- Sort Score
- Result 10 results
- Languages All
Results 11 - 19 of 19 for MESSAGES (0.19 sec)
-
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-compat/src/main/java/org/apache/maven/artifact/resolver/DebugResolutionListener.java
logger.debug(indent + artifact + " (not setting artifactScope to: " + ignoredScope + "; local artifactScope " + artifact.getScope() + " wins)"); // TODO better way than static? this might hide messages in a reactor if (!ignoredArtifacts.contains(artifact)) { logger.warn("\n\tArtifact " + artifact + " retains local artifactScope '" + artifact.getScope()
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Sep 06 11:28:54 GMT 2023 - 5.6K bytes - Viewed (0) -
maven-compat/src/main/java/org/apache/maven/project/validation/ModelValidationResult.java
/** */ private List<String> messages; public ModelValidationResult() { messages = new ArrayList<>(); } public int getMessageCount() { return messages.size(); } public String getMessage(int i) { return messages.get(i); } public List<String> getMessages() { return Collections.unmodifiableList(messages); }
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Sep 06 11:28:54 GMT 2023 - 2.4K bytes - Viewed (0) -
maven-core/src/test/resources/projects/project.xml
<include>driver.properties</include> </includes> </resource> <resource> <directory>/src/messages</directory> <targetPath>org/apache/maven/messages</targetPath> <includes> <include>messages*.properties</include> </includes> </resource> </resources> </build> <reports> <report>maven-jdepend-plugin</report>
XML - Registered: Sun Mar 31 03:35:09 GMT 2024 - Last Modified: Wed Feb 28 22:49:30 GMT 2007 - 4.6K 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/site/apt/index.apt
with its <<<DefaultExceptionHandler>>> implementation ({{{./xref/org/apache/maven/exception/DefaultExceptionHandler.html}source}}), use to transform exception into useful end-user messages. * Toolchains * {{{./toolchains.html}Toolchains descriptor reference}},
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/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)