- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for show (0.15 sec)
-
maven-core/src/test/resources/apiv4-repo/junit/junit/4.13.1/junit-4.13.1.pom
<version>2.10.3</version> <configuration> <stylesheetfile>${basedir}/src/main/javadoc/stylesheet.css</stylesheetfile> <show>protected</show> <author>false</author> <version>false</version> <detectLinks>false</detectLinks> <linksource>true</linksource>
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 24.5K bytes - Viewed (0) -
maven-core/src/site/apt/artifact-handlers.apt
define for each {{{../maven-model/maven.html#class_dependency}dependency type}} information on the artifact (classifier, extension, language) and how to manage it as dependency (add to classpath, include dependencies). They are replaced in Maven 4 with Maven 4 API Core's {{{../api/maven-api-core/apidocs/org/apache/maven/api/Type.html}Dependency Types}},
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Apr 23 06:12:44 GMT 2024 - 4.6K 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)