[ https://jira.jboss.org/jira/browse/JBBUILD-545?page=com.atlassian.jira.pl... ] Paul Gier updated JBBUILD-545: ------------------------------ Description: In the AS build, the modules install their jars to the local repository. Then when the dist build runs with the maven ant tasks, the ant tasks check the snapshot repository for updates. The ant tasks should not be checking the snapshot repository when there was a recent copy just installed. I'm not sure if this is a general problem in maven, or just a problem in the ant tasks. This is potentially a serious issue because it could mean that the jar generated by a module is not the same as the jar resolved by the Ant tasks. was: In the AS build, the modules install their jars to the local repository. Then when the dist build runs with the maven ant tasks, the ant tasks check the snapshot repository for updates. The ant tasks should not be checking the snapshot repository when there was a recent copy just installed. I'm not sure if this is a general problem in maven, or just a problem in the ant tasks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBBUILD-545?page=com.atlassian.jira.pl... ] Paul Gier commented on JBBUILD-545: ----------------------------------- This appears to be a bug in Maven dependency resolution (http://jira.codehaus.org/browse/MNG-4326). It is not a critical issue, because Maven still uses the local artifacts even though the remote repository is checked. But this should still be fixed in Maven's dependency management. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira