I migrate the JSF 1.1 application to the Java EE 6 web profile and do it step by step. I am in the process of switching from JSP from JSF 1.1 to Facelets in JSF 1.2 using jsf-facelets.jar for JSF 1.2 and got an "interesting" stack trace when trying to find the key on the map using "{Bean.foo.map.key}" where stacktrace complained about a "key" that is not a real integer. (After introspecting the code, I trick it into using a number as a key). This error is not what this question is about.
In such a situation, it is important to be able to navigate the source of each line in the stack trace. In Eclipse, I usually attach a source jar to each jar in the build path, but in this particular case, the Glassfish server adapter creates a library that automatically contains jars. Also, as far as I know, there is no Glassfish debug build where sources are included.
Glassfish is a non-trivial Maven project, and a bit picky. I am not very familiar with maven, but I managed to check the code from Subversion and build it for the 3.0 tag according to http://wiki.glassfish.java.net/Wiki.jsp?page=V3FullBuildInstructions#section-V3FullBuildInstructions-CheckoutTheWorkspace - this is apparently the code corresponding to the official version 3.0.
After completing the "mvn -U install" part, I tried to create Eclipse projects, first using "mvn -DdownloadSources = true eclipse: eclipse" and then import them into Eclipse Java EE 3.5.2 and specifying M2_REPO but many of the projects still have compilation errors, and I can not find any instructions from Oracle on how to do this.
I would appreciate help in the simple, functional IDE workspace reflecting the 3.0 version of Glassfish. I have Eclipse 3.5.2, Netbeans 6.8 and 6.9 beta, and IntelliJ IDEA 9 and Linux / Windows / OS X do this.
source
share