[ http://jira.codehaus.org/browse/MECLIPSE-95?page=all ]
Kenney Westerhof updated MECLIPSE-95:
-------------------------------------
Summary: Transitive classpath entries need to be marked exported (was: Var
classpath entries need to be marked exported by default)
Not only for VAR classpath entries, but for transitive dependencies in general.
If you have 3 projects in eclipse, A, B, and C, where A depends on B, and B
depends on C,
all via project references, then A does not have access to C and it's libs.
So both project references should be exported and var classpath entries (all
library dependencies).
Note that it's not enough to _just_ mark all of those dependencies as exported
- only transitive dependencies
should be marked as such. For instance, provided and test scope dependencies
also end up in the eclipse
classpath, and they should NOT be exported.
> Transitive classpath entries need to be marked exported
> -------------------------------------------------------
>
> Key: MECLIPSE-95
> URL: http://jira.codehaus.org/browse/MECLIPSE-95
> Project: Maven 2.x Eclipse Plugin
> Type: Improvement
> Versions: 2.1
> Reporter: Sachin Patel
> Assignee: fabrizio giustina
>
>
> Generated .classpath entries of kind "var" need to be marked exported by
> default so that referenced projects have visibility to them. Or provide an
> option to specifiy that that entries should be exported.
> Example: <classpathentry kind="var"
> path="M2_REPO/mx4j/mx4j/3.0.1/mx4j-3.0.1.jar"/>
> should me made...
> <classpathentry exported="true" kind="var"
> path="M2_REPO/mx4j/mx4j/3.0.1/mx4j-3.0.1.jar"/>
--
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
