- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for ideas (0.12 sec)
-
README.md
Contributing ------------ If you are interested in the development of Maven, please consult the documentation first and afterward you are welcome to join the developers mailing list to ask questions or discuss new ideas/features/bugs etc. Take a look into the [contribution guidelines](CONTRIBUTING.md). License ------- This code is under the [Apache License, Version 2.0, January 2004][license].
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Mar 03 21:28:30 GMT 2024 - 4.3K bytes - Viewed (0) -
.gitignore
**/target/** .project .classpath .settings/ .svn/ # Intellij *.ipr *.iml .idea .DS_Store /bootstrap /dependencies.xml .java-version .checkstyle .factorypath .vscode/ repo/
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Mar 24 18:29:19 GMT 2024 - 178 bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/MavenExecutionPlan.java
// TODO unfortunately the plugins need to be downloaded in order to get the plugin.xml file. need to externalize this // from the plugin archive. // TODO this will be the class that people get in IDEs to modify /** * MavenExecutionPlan */ public class MavenExecutionPlan implements Iterable<ExecutionPlanItem> { /*
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Jan 10 12:55:54 GMT 2024 - 6.2K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
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 could encapsulate everything we need about the project in the POM including plugin parameters and anything else. We once had a document that Vincent and I agreed upon and I was about to
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)