[
http://jira.codehaus.org/browse/MANTTASKS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159985#action_159985
]
Trevor Leach commented on MANTTASKS-124:
Thank you for your suggestion. This will approach will work for me in the
short term. For others implementing this work around, I'll list some things to
think about.
1) The POM published with your artifacts isn't being truthful with its
dependencies. Any dependent projects may not end up with everything they need
in their classpaths.
2) The build scripts will need to exclude the runtime scoped dependencies when
generating the WEB-INF/lib dir, which would normally be included.
3) This solution will not work if the project has real runtime dependencies.
> Setting dependencies with the provided scope does not work
> --
>
> Key: MANTTASKS-124
> URL: http://jira.codehaus.org/browse/MANTTASKS-124
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
>Affects Versions: 2.0.9
> Environment: OS X 10.4.11, Java 5, Ant 1.7.0, Ant 1.6.5
>Reporter: John Gibson
>
> If you use the provided scope to pull in dependences like this:
> filesetId="osgi.provided.fileset" verbose="true" useScope="provided">
>
>
>
> Then the result classpath and fileset are empty despite the POM containing
> definitions like this:
> ...
>
>
> org.osgi
> osgi-compendium
> 4.1.0
> provided
>
>
> org.osgi
> osgi-core
> 4.1.0
> provided
>
> ...
>
> I would expect to have the path/fileset contain at least those two jars (I'm
> not sure about transitive dependencies, however).
> Other users have encountered this issue, see here:
> http://www.nabble.com/maven-ant-tasks-and-the-provided-scope-td19662878.html
--
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
