- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 13 for location (0.15 sec)
-
maven-core/src/site/apt/offline-mode.apt
* Implications for Subsystems ** Maven-Wagon Parts of Wagon will continue to function normally. These include: * The file wagon, provided the referenced location is on a local filesystem. It is not possible to determine whether a file-based location will be available except on a case-by-case basis (or a root-url by root-url basis). We may want to move the offline sensitivity entirely to
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 10.6K bytes - Viewed (0) -
README.md
Quick Build ------- If you want to bootstrap Maven, you'll need: - Java 17+ - Maven 3.6.3 or later - Run Maven, specifying a location into which the completed Maven distro should be installed: ``` mvn -DdistributionTargetDir="$HOME/app/maven/apache-maven-4.0.x-SNAPSHOT" clean package ``` [home]: https://maven.apache.org/
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) -
maven-core/src/test/resources/org/apache/maven/extension/test-extension-repo/org/apache/maven/wagon/wagon/1.0-beta-2/wagon-1.0-beta-2.pom
<artifactId>plexus-utils</artifactId> <version>1.0.4</version> </dependency> </dependencies> </dependencyManagement> <!-- TODO: point to ref location <distributionManagement> <site> <id>apache.website</id> <url>scp://people.apache.org/www/maven.apache.org/wagon/</url> </site> </distributionManagement> -->
Plain Text - Registered: Sun Mar 31 03:35:09 GMT 2024 - Last Modified: Tue Oct 27 10:08:56 GMT 2020 - 5.7K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/org/apache/maven/wagon/wagon/1.0-beta-2/wagon-1.0-beta-2.pom
<artifactId>plexus-utils</artifactId> <version>1.0.4</version> </dependency> </dependencies> </dependencyManagement> <!-- TODO: point to ref location <distributionManagement> <site> <id>apache.website</id> <url>scp://people.apache.org/www/maven.apache.org/wagon/</url> </site> </distributionManagement> -->
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 5.7K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/org/apache/maven/maven-parent/5/maven-parent-5.pom
<goal>sign</goal> </goals> </execution> </executions> </plugin> <!-- We want to deploy the artifact to a staging location for perusal --> <plugin> <inherited>true</inherited> <artifactId>maven-deploy-plugin</artifactId> <version>2.3</version> <configuration>
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 14.8K bytes - Viewed (0) -
apache-maven/README.txt
export PATH=/usr/local/apache-maven-4.x.y/bin:$PATH Windows set PATH="c:\program files\apache-maven-4.x.y\bin";%PATH% 4) Make sure JAVA_HOME is set to the location of your JDK 5) Run "mvn --version" to verify that it is correctly installed. For complete documentation, see https://maven.apache.org/download.html#Installation Licensing ---------
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sat Mar 13 20:21:20 GMT 2021 - 2.5K bytes - Viewed (0) -
maven-core/src/test/resources/org/apache/maven/extension/test-extension-repo/org/apache/maven/maven-parent/5/maven-parent-5.pom
<goal>sign</goal> </goals> </execution> </executions> </plugin> <!-- We want to deploy the artifact to a staging location for perusal --> <plugin> <inherited>true</inherited> <artifactId>maven-deploy-plugin</artifactId> <version>2.3</version> <configuration>
Plain Text - Registered: Sun Mar 31 03:35:09 GMT 2024 - Last Modified: Thu Dec 24 18:09:10 GMT 2020 - 14.8K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
</parameters> </plugin> </plugins> +-----+ Unified source directory Unified source directory structure that is analogous to the repository itself. This way locations of intermediary artifacts of a build would be in a known location. This would also help with developer setup i.e. getting new developers up and running. They could run a maven command and have all their source trees set up in the same way as their colleagues.
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/src/main/resources/META-INF/maven/org.apache.maven.api.di.Inject
org.apache.maven.internal.impl.resolver.DefaultArtifactDescriptorReader org.apache.maven.internal.impl.resolver.MavenVersionScheme org.apache.maven.internal.impl.resolver.relocation.DistributionManagementArtifactRelocationSource org.apache.maven.internal.impl.resolver.relocation.UserPropertiesArtifactRelocationSource
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Thu Apr 25 14:13:36 GMT 2024 - 4.2K bytes - Viewed (0) -
apache-maven/src/main/appended-resources/META-INF/LICENSE.vm
#* *### MIT license contains date and copyright that makes the file specific to each artifact #* *##set ( $downloaded = $locator.getResourceAsFile( "licenses/${spdx}-${project.artifact.artifactId}-${project.artifact.version}.txt", "licenses/${licFile}" ) ) #* *##else #* *##set ( $downloaded = $locator.getResourceAsFile( "licenses/${spdx}.txt", "licenses/${licFile}" ) ) #* *##end #* *### add dependency info to output
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Sep 13 20:57:31 GMT 2021 - 3.7K bytes - Viewed (0)