[
http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11182
]
Wouter de Vaal commented on PAXCONSTRUCT-74:
--------------------------------------------
p.s: all other test-scoped dependencies are allways added to the .classpath
file, so this issue only appears to happen on projects that are build as
modules within the main pom
> test dependencies with scope test are not added to .classpath when building
> overall project
> -------------------------------------------------------------------------------------------
>
> Key: PAXCONSTRUCT-74
> URL: http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-74
> Project: Pax Construct
> Issue Type: Bug
> Components: maven-pax-plugin
> Affects Versions: 1.0
> Reporter: Wouter de Vaal
> Assignee: Stuart McCulloch
>
> I have created a bundle that is an implementation bundle of a bundle that
> specificies some interfaces. The normal bundle code only depends on the
> latter, but some test code within certain bundles uses the implementation
> bundle, so I wanted to add it as a maven dependency with scope test. However
> when building the overall project, the build is successful, but the entry IS
> NOT added to the .classpath file so eclipse will barf on that project.
> When I run a maven build from within the particular project, the entry IS
> added to the classpath and eclipse is happy again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
