[jira] Created: (MNG-3513) Add filtering to determine if a artifact should be downloaded from a repository.
Add filtering to determine if a artifact should be downloaded from a repository. Key: MNG-3513 URL: http://jira.codehaus.org/browse/MNG-3513 Project: Maven 2 Issue Type: Improvement Components: Artifacts and Repositories Reporter: Marco Beelen Then the settings.xml starts to contain various repositories maven will try to download artifacts from all defined repository until it is found. Since the central repo is the last repo being queried all other repositories will be queried for all artifacts as well. This causes the build to take extra unneccesary time and additional load on some repository servers. In order to prevent this I would like to be able to specify some filters on the repostories, so maven can check whether or not to ask a repository for a certain component. Suggestion for adjustments in settings.xml: repository idatlassian/id nameAtlassian Repository/name urlhttp://repository.atlassian.com/url layoutlegacy/layout includes includecom.atlassion/include /includes /repository repository idcodehaus/id nameCodehaus Repository/name urlhttp://repository.codehaus.org///url includes includeorg.codehaus/include /includes /repository repository idcentral/id nameThe default maven2 repository/name urlhttp://repo1.maven.org/maven2//url excludes excludecom.atlassion/exclude excludeorg.codehaus/exclude /excludes /repository Maven should only attempt to download a certain artifact from a defined repository if the groupId of the artifact could be found on that server. If a repository contains an includes-filter, then only those groupId's configured should be downloaded there. If a repository contains an excludes-filter, then everything except those should be downloaded there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-431) Running mvn install -Dtest fails
Running mvn install -Dtest fails Key: SUREFIRE-431 URL: http://jira.codehaus.org/browse/SUREFIRE-431 Project: Maven Surefire Issue Type: Improvement Affects Versions: 2.4 Environment: Maven 2.0.8 on Windows XP with Surefire plugin 2.4 Reporter: Marco Beelen Priority: Minor When I run mvn install -Dtest I explicitly tell maven not run any test. Since my machine got the 2.4 version of the surefire plugin, thist results in: --- T E S T S --- There are no tests to run. Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] No tests were executed! (Set -DfailIfNoTests=false to ignore this error.) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 17 seconds [INFO] Finished at: Wed Jan 16 14:17:09 CET 2008 [INFO] Final Memory: 13M/26M [INFO] Of course I can add the -DfailIfNoTests=false, but it would be much more easy if the -Dmaven.test.skip=true would set the -DfailIfNoTests=false option as well. If I'm smart or stupid enough to force to skip the execution of the test, I don't really want to be warned about that in the way of a failed build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira