[
http://jira.codehaus.org/browse/MECLIPSE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124495
]
Silvano Maffeis commented on MECLIPSE-230:
------------------------------------------
Being able to control the "exported" attribute is important for deploying Java
EE apps from Eclipse.
There are libraries which I need for the build, but which I don't want to be
included in the EAR.
The "exported" attribute allows one to control that. (Now I have to manually tag
my exported libraries again after running the eclipse plugin).
> 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: Core : Dependencies resolution and build path
> Affects Versions: 2.1
> Reporter: Vlad Skarzhevskyy
> 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
