[
http://jira.codehaus.org/browse/MECLIPSE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99459
]
Hugh Willson commented on MECLIPSE-79:
--------------------------------------
I agree, I think <exclude> functionality would be a big help. I've encountered
this problem in another way, and that is working with MyEclipse and JBoss.
To be able to build my web apps successfully with Maven alone, I make reference
to the needed Java EE api's with provided scope. When I run mvn
eclipse:eclipse to work with MyEclipse however, I've added additional
<classpathContainer> settings for MyEclipse's
"com.genuitec.eclipse.j2eedt.core.J2EE14_CONTAINER". This means within
MyEclipse, my application has a reference to the needed JEE classes from
MyEclipse's container settings, and from my "provided" scope JEE dependencies.
Not a huge problem, until I use MyEclipse's integration with JBoss. JBoss
4.2.0 with blow up because the JEE dependencies are deployed with the app to
JBoss from MyEclipse (whereas MyEclipse J2EE14_CONTAINER isn't, as MyEclipse
knows not to do this).
So, to sum up - our production builds are created using a continuous
integration server with Maven, meaning the JEE dependencies have to be made
available with our app, but having this dependency added to the .classpath file
for MyEclipse use actually gets in the way of MyEclipse's custom
com.genuitec.eclipse.j2eedt.core.J2EE14_CONTAINER. All of this could be
avoided with some kind of dependency exclusion filter when generating the
.classpath file (similiar to the patch supplied). This way Maven can keep the
dependencies it needs, but Eclipse dependency use can be modified when needed.
Thanks very much!
> exclude dependencies from the Classpath Container
> -------------------------------------------------
>
> Key: MECLIPSE-79
> URL: http://jira.codehaus.org/browse/MECLIPSE-79
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Environment: Windows, Eclipse 3.1.2
> Reporter: Martin Goldhahn
> Attachments: MECLIPSE-79.patch
>
>
> There are some dependencies that need to be in the POM in order to compile
> the project (e.g. javax.servlet). When I use Sysdeo's Tomcat plugin, I get an
> error because the servlet classes from the POM are included in the classpath
> via the classpath container.
--
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
