[
http://jira.codehaus.org/browse/MANTTASKS-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112866
]
Werner Guttmann commented on MANTTASKS-86:
------------------------------------------
I am talking about the case where the JTA JAR is *not* installed into your
local Maven repository, but where the given java.net repository should be used
for dependency resolution. Given that the JAR eventually has been made
available publically, we prefer that option. My problem is that Maven itself
does not have any problems resolving that dependency and downloades the JAR
into my local repo just fine. Whereas the Ant tasks for Maven only download the
JARs that are available in standard public Maven 2 repos.
> Resolution of java.net dependencies
> -----------------------------------
>
> Key: MANTTASKS-86
> URL: http://jira.codehaus.org/browse/MANTTASKS-86
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Affects Versions: 2.0.6
> Reporter: Werner Guttmann
> Attachments: build.bat, build.xml, pom.xml
>
>
> I am trying to use the Ant task for Maven with the root Maven POM for
> the Castor project for download the dependencies and place them into a
> lib directory.
> What I have observed is that there's a few dependencies missing when I
> run the corresponding Ant target. But if I use Maven for the build
> process, the missing JARs are downloaded as well and placed into my
> local repository.
> I have tried to define remoteRepository entries for the java.net and the
> Maven 2 java.net repositories (where e.g. java.transaction:jta:1.1.1B
> resides), but this does not make a difference.
> Any idea what I could try in addition ? Having said that, all other
> dependencies are resolved and copied without any problems. It looks like
> it's just the dependencies that are not synced globally that create a
> problem.
--
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
