- Sort Score
- Result 10 results
- Languages All
Results 11 - 19 of 19 for we (0.15 sec)
-
LICENSE
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Sep 11 20:39:30 GMT 2013 - 11.1K bytes - Viewed (0) -
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
--- Getting to Plexus-configured Mojos --- John Casey --- 2005-04-29 Abstract We're moving toward integrating mojos as first-class plexus components, while at the same time avoiding introducing required plexus dependencies into the mojo development model. In order to really achieve this, we need mojo configurations (which are provided both in terms of static expressions that are just looked up, and
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jan 30 15:20:35 GMT 2023 - 4.1K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
that currently we have information about a project scattered across the project.xml and the various properties files. What needs to be done is to encapsulate all of this in the POM. Typically users parameterize the use of plugins, or have custom values like ${user.name} for use in elements like the <developerConnection/>. It would be idea if we
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 5.8K bytes - Viewed (0) -
maven-core/lifecycle-executor.txt
</plugin> . . . </plugins>
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 9.7K bytes - Viewed (0) -
maven-core/src/test/resources/org/apache/maven/extension/test-extension-repo/org/apache/apache/3/apache-3.pom
The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. We consider ourselves not simply a group of projects sharing a server, but rather a community of developers and users. </description> <licenses> <license> <name>The Apache Software License, Version 2.0</name>
Plain Text - Registered: Sun Apr 14 03:35:08 GMT 2024 - Last Modified: Sat Nov 09 12:45:14 GMT 2019 - 3.3K bytes - Viewed (0) -
Jenkinsfile
node(jenkinsEnv.nodeSelection(osLabel)) { stage("${stageLabel}") { echo "NODE_NAME = ${env.NODE_NAME}" // on Windows, need a short path or we hit 256 character limit for paths // using EXECUTOR_NUMBER guarantees that concurrent builds on same agent // will not trample each other plus workaround for JENKINS-52657
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Mar 03 21:28:30 GMT 2024 - 8.4K bytes - Viewed (0) -
maven-core/plugin-manager.txt
described the dependencies of the plugin. We are looking at using Mercury for the resolution and retrieval of the plugin dependencies so during development we would translate the POMs into dependency information that Mercury can understand, and in production we would have the pre-digested format that Mercury could utilize to resolve and retrieve dependencies. We need to be careful that we are using Mercury during development and production so that we don’t get in the situation where Maven 2.x is...
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jul 18 22:45:13 GMT 2022 - 12.9K bytes - Viewed (0) -
maven-core/src/site/apt/plugin-execution-isolation.apt
Maven2 takes advantage of Plexus' ability to execute a component using a ClassWorlds ClassRealm that is populated with the JAR containing the component in question and all of its dependencies. Using ClassWorlds notation for realms we have the following: +-----+ [plexus.core] ^ | [plexus.core.maven] ^ ^ | | [plugin0] [plugin1] +-----+
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Feb 03 09:12:28 GMT 2017 - 2.3K bytes - Viewed (0) -
apache-maven/src/main/appended-resources/licenses/Apache-2.0.txt
replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Jan 28 11:47:17 GMT 2020 - 11.1K bytes - Viewed (0)