[
http://jira.codehaus.org/browse/MECLIPSE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103201
]
Max Bowsher commented on MECLIPSE-230:
--------------------------------------
I do not know about J2ME, but for J2SE development, exporting seems to be
unnecessary, and potentially even harmful:
If you have a group of interdependent projects, configured with the
maven-eclipse-plugin, Maven will already have resolved the complete set of
required dependencies and added them to each project's classpath - no exports
needed. The potential for harm is: Maven may have resolved different versions
of various dependencies in each project. Exports will thus result in multiple
versions of the same jar being present on the classpath.
> Classpath entries to be marked exported
> ---------------------------------------
>
> Key: MECLIPSE-230
> URL: http://jira.codehaus.org/browse/MECLIPSE-230
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: dependency resolution
> Affects Versions: 2.1
> Reporter: Vlad Skarzhevskyy
> Assignee: fabrizio giustina
> Fix For: 2.5
>
>
> 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
