- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 21 for Cook (0.15 sec)
-
maven-core/plugin-manager.txt
* * - nexus - the plugin class - UI to contribute - what JS to hook into the UI - what resources to * load into the UI - having packed or unpacked plugins, and positioning resources if necessary - * maven can work out of the classloader, nexus plugins probably couldn't give the js and image * resources * * We need to look at Maven, and Nexus as use cases and figure out what each of them needs to be * able to do *
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 22:45:13 GMT 2022 - 12.9K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/api/services/model/RootLocator.java
* property which happens very early. The implementation used in this case * will be discovered using the JDK service mechanism. * * The default implementation will look for a {@code .mvn} child directory * or a {@code pom.xml} containing the {@code root="true"} attribute. */ public interface RootLocator {
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 2.4K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
named org.apache.commons.logging.LogFactory. Use the JDK 1.3 JAR Services Discovery mechanism (see http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html for more information) to look for a resource named META-INF/services/org.apache.commons.logging.LogFactory whose first line is assumed to contain the desired class name. Look for a properties file named commons-logging.properties visible in the application class path, with a property named org.apache.commons.logging.LogFactory defining the desired implementation...
Archive - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 37.1K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/plugin/MavenPluginManager.java
* the mojo execution. The mojo/plugin descriptor associated with the mojo execution provides the class realm to * look up the mojo from. <strong>Warning:</strong> The returned mojo instance must be released via * {@link #releaseMojo(Object, MojoExecution)} when the mojo is no longer needed to free any resources allocated for * it. *
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Sep 06 08:39:32 GMT 2023 - 6.6K bytes - Viewed (0) -
apache-maven/src/assembly/maven/conf/settings.xml
<!-- | Here is another profile, activated by the property 'target-env' with a value of 'dev', which | provides a specific path to the Tomcat instance. To use this, your plugin configuration might | hypothetically look like: | | ... | <plugin> | <groupId>org.myco.myplugins</groupId> | <artifactId>myplugin</artifactId> | | <configuration>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jun 19 15:06:01 GMT 2023 - 11K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar
named org.apache.commons.logging.LogFactory. Use the JDK 1.3 JAR Services Discovery mechanism (see http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html for more information) to look for a resource named META-INF/services/org.apache.commons.logging.LogFactory whose first line is assumed to contain the desired class name. Look for a properties file named commons-logging.properties visible in the application class path, with a property named org.apache.commons.logging.LogFactory defining the desired implementation...
Archive - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 30.9K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/api/services/model/ModelNormalizer.java
import org.apache.maven.api.services.ModelProblemCollector; /** * Handles normalization of a model. In this context, normalization is the process of producing a canonical * representation for models that physically look different but are semantically equivalent. * */ public interface ModelNormalizer { /** * Merges duplicate elements like multiple declarations of the same build plugin in the specified model. *
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 2.3K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/plugin/PluginContainerException.java
* artifactId, and version for the plugin; at times, the goal name for which * execution failed; a message detailing the problem; the ClassRealm used to * look up the plugin; and the Plexus exception that caused this error. * * */ public class PluginContainerException extends PluginManagerException { private ClassRealm pluginRealm;
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Jan 10 12:55:54 GMT 2024 - 3.2K bytes - Viewed (0) -
apache-maven/src/assembly/shared/init.cmd
@REM Find the project basedir, i.e., the directory that contains the directory ".mvn". @REM Fallback to current working directory if not found. set "EXEC_DIR=%CD%" set "WDIR=%EXEC_DIR%" @REM Look for the --file switch and start the search for the .mvn directory from the specified @REM POM location, if supplied. set FILE_ARG= :arg_loop if "%~1" == "-f" ( set "FILE_ARG=%~2" shift goto process_file_arg
Batch File - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Dec 16 21:35:28 GMT 2022 - 2.1K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/DefaultLifecycleExecutor.java
} public void execute(MavenSession session) { lifecycleStarter.execute(session); } // These methods deal with construction intact Plugin object that look like they come from a standard // <plugin/> block in a Maven POM. We have to do some wiggling to pull the sources of information // together and this really shows the problem of constructing a sensible default configuration but
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Feb 28 23:31:09 GMT 2024 - 7K bytes - Viewed (0)