You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carl-Erik Kopseng (JIRA)" <ji...@codehaus.org> on 2008/06/08 22:16:12 UTC
[jira] Commented: (MECLIPSE-361) eclipse plugin and WTP generating
warnings in Europa
[ http://jira.codehaus.org/browse/MECLIPSE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137814#action_137814 ]
Carl-Erik Kopseng commented on MECLIPSE-361:
--------------------------------------------
Thanks for the QuickFix tip, this has been halting development on my WebApp for three days! Someone here mentioned that the behaviour was to be expected, and was correct. I don't know how you end up with that, but what would then be the correct way to fix this?
Is there some way to specify that some/all libraries on the build path must be included in the build? I make a JSF webapp, and would like all things not included in Tomcat to be shipped with the war (in the WEB-INF/lib directory). Should I just manually put the jars in there, or is there a better/more automated way of doing this?
> eclipse plugin and WTP generating warnings in Europa
> -----------------------------------------------------
>
> Key: MECLIPSE-361
> URL: http://jira.codehaus.org/browse/MECLIPSE-361
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
> Affects Versions: 2.5
> Environment: Eclipse 3.3.1.1 and WTP 2.0.1 Using Maven 2.0.7 and the last maven-eclipse-plugin 2.5-SNAPSHOT
> Reporter: Yann Albou
> Priority: Minor
> Attachments: wtpTest.zip
>
>
> The issue is regarding warnings in Europa and WTP:
> "Classpath entry M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13.jar will not be exported or published. Runtime ClassNotFoundExceptions may result."
> 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin
> version 2.5-SNAPSHOT => I get the same behaviour in EUROPA (WARNINGS)
> 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin
> version 2.4 => I get the same behaviour in EUROPA (WARNINGS)
> 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse
> 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or
> 2.5-SNAPSHOT => Everything is perfect, no more warnings
> I create a simple test in order to reproduce the issue.
> This test is a multi module application composed of 1 Ejb module and 1 Ear module.
> So at the top level Just run "mvn install eclipse:eclipse"
> And then in an europa workspace import the projetcs and you should see the warnings on the EJB module.
> It will behave the same way if it exists other modules.
> I notice that, in the case you update parameters on the eclipse plugin you will need to remove projects from workspace and import them again.
> otherwise some old parameter will stay in the eclipse cache...
> let me know if you need other tests
> Yann.
--
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