- Sort Score
- Result 10 results
- Languages All
Results 151 - 153 of 153 for Implementation (0.25 sec)
-
src/mdo/merger.vm
* @param sourceDominant A flag indicating whether either the target object or the source object provides the * dominant data. * @param hints A set of key-value pairs that customized merger implementations can use to carry domain-specific * information along, may be <code>null</code>. */ public ${root.name} merge(${root.name} target, ${root.name} source, boolean sourceDominant, Map<?, ?> hints) {
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Tue Sep 05 16:06:44 UTC 2023 - 12.2K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/org/apache/maven/wagon/wagon-provider-api/1.0-beta-2/wagon-provider-api-1.0-beta-2.jar
static String getUserName(); } META-INF/maven/org.apache.maven.wagon/wagon-provider-api/pom.xml wagon org.apache.maven.wagon 1.0-beta-2 4.0.0 wagon-provider-api Maven Wagon API Maven Wagon API that defines the contract between different Wagon implementations org.codehaus.plexus plexus-utils META-INF/maven/org.apache.maven.wagon/wagon-provider-api/pom.properties #Generated by Maven #Tue Dec 12 17:05:59 EST 2006 version=1.0-beta-2 groupId=org.apache.maven.wagon artifactId=wagon-provider-api...
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Sun Oct 02 08:41:25 UTC 2022 - 45.2K bytes - Viewed (1) -
maven-core/plugin-manager.txt
- we also seem to have information like the plugin lifecycle model that's buried inside the maven execution model - we also seem to have artifact information tangled inside the plugin model - we have to deal with scripting implementations (groovy, beanshell, ruby) - we need to deal with a shared context for plugins, like the guarded mojos - we need to deal with plugins as core application logic which can also interact with plugins
Registered: Wed Jun 12 09:55:16 UTC 2024 - Last Modified: Mon Jul 18 22:45:13 UTC 2022 - 12.9K bytes - Viewed (0)