[
https://jira.codehaus.org/browse/JBEHAVE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284514#comment-284514
]
Alexander Lehmann edited comment on JBEHAVE-650 at 11/29/11 7:29 AM:
---------------------------------------------------------------------
I should mention that this isn't affected by the change in the way the maven
task is loaded into ant (JBEHAVE-634)
was (Author: alexlehm):
I should mention that this isn't affected by the change in the way the
maven task is loaded into ant (JBEHAVE-650)
> Ant copy-dependencies (binary distribution) doesn't find all required
> artifacts when the local maven cache is empty
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBEHAVE-650
> URL: https://jira.codehaus.org/browse/JBEHAVE-650
> Project: JBehave
> Issue Type: Bug
> Components: Build
> Affects Versions: 3.5.4
> Environment: ubuntu, ant 1.8.2
> Reporter: Alexander Lehmann
> Priority: Minor
>
> Starting with a local .m2 repository the doesn't have the files cached, ant
> copy-dependencies doesn't find all necessary artifacts.
> (log shortened)
> BUILD FAILED
> /home/lehmann/jbehave/jbehave-3.5.4/lib/build.xml:7: Unable to resolve
> artifact: Missing:
> ----------
> 1) com.google.gdata:gdata-java-client:jar:1.40.0.atlassian-2
> 2) org.jboss.weld.se:weld-se:jar:1.1.1.Final
> it seems that the settings.xml file is not used at all (e.g. it never looks
> at the glassfish repository).
> However if you run mvn test -s settings.xml, the depencies are found and
> later the ant task completes successfully as well (once the files are cached)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
