- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for MESSAGES (0.18 sec)
-
maven-api-impl/src/test/java/org/apache/maven/internal/impl/DefaultSettingsValidatorTest.java
assertEquals(4, problems.messages.size()); assertContains(problems.messages.get(0), "'mirrors.mirror.id' must not be 'local'"); assertContains(problems.messages.get(1), "'mirrors.mirror.url' for local is missing"); assertContains(problems.messages.get(2), "'mirrors.mirror.mirrorOf' for local is missing");
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Mar 25 10:50:01 GMT 2024 - 8.6K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/model/DefaultModelNormalizer.java
* the way 2.x works. When we're in strict mode, the removal of duplicates just saves other merging steps from * aftereffects and bogus error messages. */ List<Dependency> dependencies = model.getDependencies(); Map<String, Dependency> normalized = new LinkedHashMap<>(dependencies.size() * 2); for (Dependency dependency : dependencies) {
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 5.3K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultMavenPluginManager.java
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 25 14:13:36 GMT 2024 - 42.5K bytes - Viewed (0) -
maven-core/src/site/apt/offline-mode.apt
It means warning users that since the network is missing, certain features and operations will be unavailable, rather than simply waiting for those operations to fail, then trying to help users decipher the error messages they get as a result. * Implications for Resolution ** Dependency Resolution This one is obvious...we only have access to the repositories using
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) -
api/maven-api-model/src/main/mdo/maven.mdo
For example, if you want that resource to appear in a specific package ({@code org.apache.maven.messages}), you must specify this element with this value: {@code org/apache/maven/messages}. This is not required if you simply put the resources in that directory structure at the source, however. </description>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Apr 23 13:29:46 GMT 2024 - 115.1K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar
LogFactory.getInstance(String name). Your application can contain references to multiple loggers that are used for different purposes. A typical scenario for a server application is to have each major component of the server use its own Log instance. Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (debug(), info(), warn(), error, and fatal()). For convenience, LogFactory also offers a static method getLog() that combines the typical two-step pattern:...
Archive - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 30.9K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
LogFactory.getInstance(String name). Your application can contain references to multiple loggers that are used for different purposes. A typical scenario for a server application is to have each major component of the server use its own Log instance. Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (trace(), debug(), info(), warn(), error, and fatal()). For convenience, LogFactory also offers a static method getLog() that combines the typical two-step...
Archive - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 37.1K bytes - Viewed (0)