- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for problems (0.15 sec)
-
maven-core/src/site/apt/inheritance.apt
maven occur, the maven inheritance model must be pinned against a particular modelVersion. This is required so that a change from modelVersion 4.0.0 to 4.1.0 doesn't cause compatibility problems with users who have not upgraded their projects. It also allows for a certain amount of legacy support into the future. Therefore, we should rename this file from pom.xml in the maven-core
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 3.5K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
files for the current project. if yes. then I'm able to find projects that can be offered to be opened together with the current project. problems with the current solution are: 1. information is duplicate. once in POM's dependencies and once in the maven.multiproject.includes property. 2. it works without problems only for projects with relative paths, e.g., from one CVS repository.. for projects from multiple SCM repositories it's harder
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) -
apache-maven/src/main/appended-resources/licenses/unrecognized-javax.annotation-api-1.3.2.txt
that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue May 11 18:59:18 GMT 2021 - 38.5K bytes - Viewed (0) -
maven-core/src/site/apt/offline-mode.apt
file:// (which is highly likely to be the case), or the repository is not on a local filesystem, deployment will fail when offline. ** Testing mojos This can be a problem if the tests are more than simple unit tests; that is, if they require configuration of a server process, and subsequent testing in-container. Since we're only going to concern ourselves with states where localhost is
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/site/apt/getting-to-container-configured-mojos.apt
traversing an object graph and extracting Object values, not just Strings. * ComponentConfigurator Currently, the container uses BasicComponentConfigurator, to configure components. This wouldn't be a problem, except for the local instance of DefaultExpressionEvaluator used within. See the above discussion for more on why this evaluator is bad. We need to provide either an alternative
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)