Bill Bartels wrote:
I used command line to check out the Jetspeed-2 and built with maven2 by using "mvn
-P tomcat".
It deployed to tomcat server well. Then I ran "mvn eclipse:eclipse" under
Jetspeed-2 root directory and it produced
the .classpath and .project files. In Eclipse I imported Jetspeed-2 and
manually added the missing libs for the build.
I enabled maven2 and did the validation, Eclipse threw out 100+ errors and
1000+ warnings.
Then can somebody please tell me what would be next in this situation, I mean
what I can do on Jetspeed-2 in Eclipse.
How exactly should I build/deploy/debug Jetspeed-2 in Eclipse?
We provide you with .classpath files with the project
Unfortunately those .classpath references are based off a maven-1 local
repo based variable.
I installed the Maven-2 Eclipse plugin. I can't seem to get past this
weird pom.version 2.4.1 error. We use the ${pom.version} in a lot of dep
references and the eclipse plugin fails to support that currently:
http://jira.codehaus.org/browse/MNGECLIPSE-30
http://jira.codehaus.org/browse/MNG-2653?rc=1
Seems to be fixed in 0.0.10 which is not available yet afaik, (im at
0.0.9), so I think you have to build the plugin from source to get this
fix, or maybe there is a nightly build available somewhere on codehaus
As for build/deploy/debug, if I am working on the core jetspeed-2
project, I build from the command line, and then remotely debug to
Tomcat. For custom builds, recommend the genapp approach even in maven-1
or better yet, maven-2 since we will deprecate maven-1 after the next
release
maven-1:
http://portals.apache.org/jetspeed-2/j2-maven-plugin.html
maven-2:
http://wiki.apache.org/portals/Jetspeed2/Maven2BuildSupport
I am working on a tutorial for custom projects
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
