- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for Night (0.27 sec)
-
CONTRIBUTING.md
code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things. Some of the ideas are documented in the [Maven Wiki][maven-wiki] which might be interesting to read and for further discussion. Getting Started ---------------
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Oct 10 09:48:27 GMT 2021 - 4.7K bytes - Viewed (0) -
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
implementation under a different roleHint, or else replace the BasicComponentConfigurator. * Other We may need to define a new lifecycle/phase to contextualize a mojo right before it's used, and reset it's state afterward. Up to now, the approach of most plexus components has been to avoid instance state like the plague. With the current parameter passing model of mojos, this will not be possible,
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
${maven.home} | +--- maven.properties +-----+ * Group configuration As far as properties go for an entire build the maven.properties could be placed at the top of the group but I'm not really sure how this might work. There could probably also be a directory for plugins.xml and maven.properties. * Project configuration At the project level all configuration is achieved by tweaking the POM. One of the differences between
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
- check to see if anything is missing
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)