You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Michal Stochmialek (JIRA)" <ji...@codehaus.org> on 2006/01/16 11:31:01 UTC
[jira] Commented: (MNGECLIPSE-21) subprojects' jars inside the
project are added to eclipse .classpath
[ http://jira.codehaus.org/browse/MNGECLIPSE-21?page=comments#action_55984 ]
Michal Stochmialek commented on MNGECLIPSE-21:
----------------------------------------------
The problem with war dependency is one thing. The another problem is when you include subproject jars into classpath, then you have duplicates in classpath. Classes from subprojects are added to target directory from source folders, and also they are in jars (which plugin adds to eclipse classpath). Duplicates in classpath are often a cause of difficult to find class loading problems...
> subprojects' jars inside the project are added to eclipse .classpath
> --------------------------------------------------------------------
>
> Key: MNGECLIPSE-21
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-21
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Versions: 0.0.3
> Environment: windows xp, eclipse 3.1, maven 2.0.1, plugin 0.0.3
> Reporter: Michal Stochmialek
> Assignee: Eugene Kuleshov
> Fix For: 0.0.4
> Attachments: mvn-multiproject-2.zip
>
>
> My project is a multiproject which produces an ear with ejb and war. It has several subprojects / modules. The project has normal hierachial maven structure.
> Whole project (all subprojects) are contained in a single eclipse project. It's a quite convinient to work if it like that.
> I tried to use eclipse plugin with this project, but I following problem appeared. While building .classpath (Maven2 Dependencies container) plugin is also adding subproject jars.
> In this case this behaviour is incorrect, since:
> 1) the same classes are also compiled by eclipse (from source folders). In result we have classes compiled by eclipse in output folder and classes compiled by maven in jars in maven repository.
> 2) one of subprojects is packaged as a war. In result eclipse is refusing to use this kind of dependency and I'm getting following message: "Illegal type of archive for required library: '<CUT>\.m2\repository\foo2\foo-web\0.0.1-SNAPSHOT\foo-web-0.0.1-SNAPSHOT.war' in project foo2"
> See included example projected.
> I'm not aware of any case when adding subproject jars to eclipse .classpath would be appropiate. Maybe you can turn off this 'feature' by default?
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org