[lambo2006]

I am using Maven and MyEclipse for web app development. Directory structure is as follows:

-project
src/main/java
src/main/webapp (with css, images etc. folders within)
src/main/resources
target/classes

In myEclipse, I set up the src/main/webapp as the source folder and target/classes as the output folder. MyEclipse builds the project properly with expected resources files and classes files going to target/classes.

However, when I deploy to jboss, only webroot/lib and webroot/classes are deployed, leaving all other directories (i.e. css, images) and files behind.

Is there a way to cleanly separate source code and generated code into separate folders like maven does? And deploy properly?

[Scott Anderson]

Lambo,

At the present time our project model is set up to handle the standard ‘exploded WAR’ based model so that deployment can be automated and kept up to date. We’re looking at adding support for Maven in the future, but presently our deployer does not know how to deploy Maven-based structures. However, if you’d like to use that structure you certainly can, but it is treated as a custom layout so that deployment must be handled by the user and cannot be done automatically.

If you’re looking for ease of use and full tool automation, have you tried setting up your project using our wizards and the default layout? Is there some overarching reason that that setup won’t work for you at all or an advantage that maven provides that our setup does not? For example, you can still keep multiple source files for all your artifacts for separation, but if you set all the output directories to WEB-INF/classes, I think you’ll find that deployment works much better for you even in this layout.

[Author]

Posts