- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for Down (0.12 sec)
-
maven-core/src/site/apt/offline-mode.apt
repositories are "really" offline, since offline mode is more of a behavior, and this will lead to counter-intuitive results. A different feature may exist unimplemented, which is to detect when the network is down and provide better feedback for that case. However, when offline mode is declared, nothing earmarked as remote should be accessed, regardless of whether it is actually a physically local resource.
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) -
maven-core/src/test/resources/apiv4-repo/org/codehaus/plexus/plexus-components/1.1.6/plexus-components-1.1.6.pom
<artifactId>plexus-components</artifactId> <packaging>pom</packaging> <version>1.1.6</version> <name>Plexus Components Parent Project</name> <!-- TODO: should this be pushed down to all the dependencies? - a more stable API JAR may be useful, for the interfaces and classes such as AbstractLogEnabled --> <dependencies> <dependency> <groupId>org.codehaus.plexus</groupId>
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 1.8K bytes - Viewed (0) -
apache-maven/src/assembly/maven/lib/jansi-native/README.txt
This directory contains Jansi native libraries extracted from Jansi JAR. You can add your own build for platforms not natively supported by Jansi. See here [1] on how to compile for your platform and here [2] how libraries follow Jansi's directory and filename conventions. [1] https://github.com/fusesource/jansi/tree/master/src/main/native
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 486 bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/org/apache/apache/3/apache-3.pom
<releases> <enabled>false</enabled> </releases> </repository> </repositories> <distributionManagement> <!-- Site omitted - each project must provide their own --> <repository> <id>apache.releases</id> <name>Apache Release Distribution Repository</name> <url>scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository</url> </repository>
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 3.3K bytes - Viewed (0) -
maven-api-impl/src/test/remote-repo/org/apache/apache/1/apache-1.pom
<releases> <enabled>false</enabled> </releases> </repository> </repositories> <distributionManagement> <!-- Site omitted - each project must provide their own --> <repository> <id>apache.releases</id> <name>Apache Release Distribution Repository</name> <url>scp://minotaur.apache.org/www/www.apache.org/dist/maven-repository</url> </repository>
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu May 02 15:10:38 GMT 2024 - 3.3K bytes - Viewed (0) -
maven-core/plugin-manager.txt
h3. Plugins need a specific metadata model Each application will have its own model for plugins. Much of this model will be common across applications but there will always be issues specific to a particular applications’s plugins. Some of the issues that need to be taken into consideration: * Plugin dependencies
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)