You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kirill Petrov (JIRA)" <ji...@codehaus.org> on 2008/04/09 21:17:58 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=130293#action_130293 ] 

Kirill Petrov commented on MECLIPSE-361:
----------------------------------------

Was the issue fixed? on my project it generates 40-50 warnings - I don't see the real ones.
I am runing eclipse 3.2.2 (enterprise edition) and v.2.5 of the eclipse plugin. 

> 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