- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for dong (0.34 sec)
-
apache-maven/src/assembly/shared/init
( basedir=`find_file_argument_basedir "$@"` wdir="$basedir" while [ "$wdir" != '/' ] ; do if [ -d "$wdir"/.mvn ] ; then basedir=$wdir break fi wdir=`cd "$wdir/.."; pwd` done echo "$basedir" ) } find_file_argument_basedir() { ( basedir=`pwd` found_file_switch=0 for arg in "$@"; do if [ ${found_file_switch} -eq 1 ]; then if [ -d "${arg}" ]; then
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sat Mar 05 22:52:54 GMT 2022 - 2.3K bytes - Viewed (0) -
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
If these mojos are to be first-class components, the configuration from these various sources must be consolidated and injected using the container. Currently, mojo configuration is done externally to the container, in the DefaultPluginManager in the maven-core API. In order to get from here to there, we need to do several things to add capability to the default
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
</goals> </execution> </executions> </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/site/apt/index.apt
* {{{./extension.html}extension descriptor}} and {{{./core-extensions.html}core extensions}}, * {{{/guides/mini/guide-maven-classloading.html}classloader hierarchy}} done by <<<ClassRealmManager>>> component ({{{./apidocs/org/apache/maven/classrealm/ClassRealmManager.html}javadoc}}), with its <<<DefaultClassRealmManager>>> implementation
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Jun 14 05:48:39 GMT 2023 - 5.3K bytes - Viewed (0) -
maven-core/plugin-manager.txt
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 resolving differently than Mercury is. We can still leverage POMs during development but we need to make sure Mercury is doing the work. With respect to development inside an IDE the workspace from which we would like to resolve and retrieve dependencies is a read-only local repository...
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) -
apache-maven/src/assembly/shared/mvnvalidate
while [ -h "$PRG" ] ; do ls=`ls -ld "$PRG"` link=`expr "$ls" : '.*-> \(.*\)$'` if expr "$link" : '/.*' > /dev/null; then PRG="$link" else PRG="`dirname "$PRG"`/$link" fi done saveddir=`pwd` MAVEN_HOME=`dirname "$PRG"`/.. # make it fully qualified MAVEN_HOME=`cd "$MAVEN_HOME" && pwd`
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sat May 23 07:59:32 GMT 2020 - 418 bytes - Viewed (0)