Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.5
-
Fix Version/s: None
-
Component/s: WTP support
-
Labels:None
-
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
-
Number of attachments :
Description
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.
Confirmed here as well. I think this deserves a higher priority than "minor" because it requires a very tedious workaround every time you run the eclipse:eclipse goal. Essentially, WTP 2.0 support isn't practical for day to day use until this is fixed.