Comments on: Getting started with Eclipse 3.3 WTP 2.0 and JSF â€“ will this JSF editor beat JDeveloper?

By: Jan Hoeve

Jan Hoeve — Thu, 23 Aug 2007 18:11:46 +0000

you can do mvn -cpu -U eclipse:eclipse to force-check for new versions. You can also fixate the plugin version in the pom.xml.

By: mohan

mohan — Thu, 23 Aug 2007 04:19:07 +0000

yes, you can always invoke the full qualified plugin and version, 2.4 (just released) supports
wtp 1.5 (not 2.0). so here goes (I usually put it in a pom profile):
mvn org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse -Dwtpversion=1.5
cheers
Mohan

By: Jeroen van Wilgenburg

Jeroen van Wilgenburg — Wed, 22 Aug 2007 08:16:59 +0000

I didn’t knew 1.5 was supported. When I do mvn eclipse:eclipse -Dwtpversion=1.5 I get an error that I only can use R7 or 1.0. I removed the .m2\repository\org\apache\maven\plugins\maven-eclipse-plugin directory and run the command again and then it worked fine. Is there a way to automatically update the plugins you’re using?
So thanks for the tip, now my Eclipse projects are WTP 1.5

By: Jan Hoeve

Jan Hoeve — Tue, 21 Aug 2007 17:41:27 +0000

Jeroen, the maven guys (maven eclipse guys to be precisely) think that WTP 2.0 is the same as 1.5.
But there is a bugreport which addresses some issues: http://jira.codehaus.org/browse/MECLIPSE-264

By: Jeroen van Wilgenburg

Jeroen van Wilgenburg — Thu, 09 Aug 2007 07:03:49 +0000

Thanks for the tip Jan! Now I can work with existing maven projects in Eclipse. I also think it’s a bug in WTP that the webapp folder has to be a root folder. But the maven guys should also be aware that there already is a WTP 2.0 and not 1.0

By: Jan Hoeve

Jan Hoeve — Sat, 04 Aug 2007 20:53:33 +0000

I also had the same problem. I suggested a similar solution on my blog on this issue: http://janhoeve.blogspot.com/2007/07/opening-faces-configuration-files-in.html

Maybe it’s usefull for you as well.

By: Michael Schnake

Michael Schnake — Tue, 24 Jul 2007 13:41:02 +0000

Sorry, POM code format was destroyed (this is my first post here, did not know this blog takes HTML). So, here again (hopefully intact)…

maven-war-plugin

${basedir}/webapp

By: Michael Schnake

Michael Schnake — Tue, 24 Jul 2007 13:35:40 +0000

I found the problem with faces-config.xml editor not working. It fails if the “WebContent” directory is not a direct child of the project dir. So the Maven2 default “/src/main/webapp” does not work. If you want to verify, create a new Dynamic Web Project in Eclipse and try to enter some text with a “/” inside into the “Content Directory”-Field on the last wizard page

So, I got to move my /src/main/webapp to /webapp, and add the following to the POM:

maven-war-plugin

${basedir}/webapp

It is not “Maven2 Standard Directory Layout” anymore, but so far I had no problems (at least war-, eclipse- and cargo-plugin work as expected).

By: Philippe Desrosiers

Philippe Desrosiers — Sun, 22 Jul 2007 06:02:58 +0000

I’m also having the same problem opening an existing faces-config.xml file with the Faces Configuration Editor. Assertion Failed. Is anyone able to get this working in Eclipse without creating a brand new project and using the single-level directory structure they force you to use in the wizard?

By: Jeroen van Wilgenburg

Jeroen van Wilgenburg — Thu, 19 Jul 2007 08:40:57 +0000

I haven’t found out yet how to get the faces-config.xml working. The example in the article is with a brand new project.