Java 6 Development Environment, Maven 2.x, Eclipse 3.4.x, JBoss 5, and JBoss Seam
I need to organize a development environment where I can run Maven projects using JBoss Seam, the eclipse 3.4.x IDE, and deployments to JBoss 5. The projects that will run in this environment are Java 6, EJB3, and JSF1.2 based. The environment must support hot deployment.
I worked in a development environment using the Sysdeo Plugin to get Tomcat to run all my applications - I rarely used EJB (only for MDB). So I would prefer an environment like this.
I would like to know what you guys are using for architecture (which eclipse plugins - if they work fine, something like this)
What I didn't really understand is why my Maven2 project with SEAM as a dependency packaged as EAR does not appear on my server (in Eclipse Ganymede - in tabs) for deployment (right click - Add and Remove option projects ...). Do I have to include a specific project to make my Maven2 EAR project visible to my JBoss AS included in my Eclipse Ganymede?
The seam doesn't seem good for Maven2. I am running into some problems to get them to work together - some dependencies seem to be missing and I have to add some additional files in some special places like seam.properties and components.xml with some special content. I feel compelled to use suture gene and Ant. Too bad!
a source to share
I am currently working on the same environment you asked for, the only difference being that I am running the application on tomcat 6.0.18. I prefer to use tomcat because it is faster and I am not using EJB yet.
Eclipse plugins:
- maven: m2eclipse.codehaus.org
- Jboss tools: www.jboss.org/tools
- rapid deployment web tools platform: www.eclipse.org/webtools/
I took Eclipse Java EE version, I don't use seam-gen to create basic architecture.
I don't have many problems with this environment, sometimes hot-deploy doesn't work and I have to manually clean up the files. The only problem I had was splitting my application in two modules: eclipse doesn't do the job well (other than the last package of one module when building another), and I found the "disable workspace resolution" option that works fine now.
Works great. Hope this works for you.
a source to share
Not sure if this is helpful for you, but we run the following
- eclipse as IDE
- mercury for source control.
- merclipse mercury eclipse plugin http://goldenhammers.com/merclipse/
- maven for build (and m2eclipse)
- mylyn with bugzilla for issue tracking
- tomcat as application server
- hudson for continuous integration http://hudson-ci.org/
- review for code reviews http://www.review-board.org/
- to assess code quality http://sonar.codehaus.org/
- Proxmox VE for Virtualization http://pve.proxmox.com/wiki/Main_Page
Most things run on separate virtual machines to ensure minimal interference. Proxmox VE is a breeze to set up (15 minutes and you're up and running).
Hudson monitors the repository and automatically builds and tests every push. If the war build is successful, it is automatically (re) deployed (using the hudson plugin) to Tomcat and restarted.
I cannot recommend these tools enough.
NTN
a source to share