On 2/18/07, Shash Chaterjee <[EMAIL PROTECTED]> wrote:
Matt,
I am sure AppFuse works, that's why I am spending time on it. For sure,
most of the validation errors are because the WEB-INF/lib isn't setup
correctly in my config, working on that. But, there are some true errors
as
well, I found. Once I get this all working, I'll checkout from the repo,
and send in patches for stuff I can fix.
I followed the other two links, but not that applicable to what I am
trying
to get, so I'll just trudge through this.
Here's what I have seen so far:
- Eclipse doesn't really like the parent POM to be at the root
dir. Instead
I broke it up to have the parent POM in a project of it's own, and that
works much better:
myproject
pom
core
web
- Need to use one of the following, but not a combo:
- mvn eclipse:eclipse (i.e. the Maven-2 Eclipse Plugin)
- Eclipse M2 plugin (this one has problems with the AppFuse Warpath
Maven plugin when run from Maven used under Eclipse)
- Eclipse Maven IDE plugin
- I like the Maven-2 Eclipse plugin the best, so I am concentrating on
that.
it creates the .settings folder in the web project, which the WTP toolkit
now uses. .wtpmodules file is now gone,
.settings/org.eclipse.wat.common.component used instead.
- The main problem seems to be that the Maven Eclipse Plugin doesn't add
the
"target/myproject-webapp-1.0-SNAPSHOT" directory as the place where WTP
should find WEB-INF and WEB-INF/lib, so the .settings/....component file
needs to be modified by hand.
- Most of the validation errors go away after that, but not all. Almost
there with being able to use code-completion for JSPs, which is my biggest
interest in using an IDE and not just vanilla mvn build.
- When running AppFuse straight from a WTP deploy to Tomcat, got lots of
errors with missing listenors, etc. Seems like it is because WTP (of
course) have an understanding of the AppFuse warpath JARs. I see those
JARs
in target, how/where should those be expanded?
AppFuse 2.0 uses the overlay[1] feature of the Maven WAR plugin, which is
probably going to be tricky to replicate in an IDE build. Basically it
merges the contents of dependent war files with the project to build the
final, deployable war. The warpath jar files are created purely to make the
contents of the WEB-INF/classes directory of all dependent war files
available on the compile classpath for the other steps in the build. They
should not form part of the final build, rather the IDE build tools should
emulate the war overlay capabilities of the Maven war plugin - the easiest
way to do this might be to delegate to Maven to do the build rather than
rely on the IDE tools.
Mike
[1]http://maven.apache.org/plugins/maven-war-plugin/examples/war-
overlay.html
Since AppFuse works fine (and validates!), most of these
errors/warnings are invalid. It's probably best to configure Eclipse
so it doesn't warn you about JSP issues. If it makes you feel any
better - IDEA doesn't warn about these issues. ;-)
Matt
--
View this message in context:
http://www.nabble.com/Appfuse-M3-and-Eclipse-help-tf3245072s2369.html#a9031413
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
