Hi,
I am using Eclipse, and have generated a modular Struts project. My project
root folder currently contains all source internally within "core" and "web"
folders.
These are the steps I followed when creating the project...
* From the command line, cd into the new project's "core" directory and
run mvn install eclipse:eclipse to generate project files for Eclipse and
install the core jar ready for the "web" part of the project.
* cd into the new project's "web" directory and run mvn eclipse:eclipse
to generate project files for Eclipse
* run mvn clean in the project "root" directory and both "core" and
"web" directories will be cleaned
* run mvn appfuse:full-source in the project "root" directory
(I have also placed the all source folders on the build path so that they
are more accessible via core/src/main/java etc)
I have noticed that "projectname-core" and "projectname-webapp" projects
have also been created and they are empty.
1. What should I have done so that the source was dispersed between the
appropriate separate projects?
2. Once the projects are separated, how will I maintain the entire thing, in
terms of the parent pom in the root project "knowing" about it's child poms
etc?
3. What are the pros and cons of the two approaches when compared?
-----
Regards,
Matthew
--
View this message in context:
http://www.nabble.com/Modular-structure-with-Eclipse-tp18234345s2369p18234345.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
