I am considering"Mavenizing" a pre-existing project.
This project consists of a Web Application (WAR file) and a server side
JAR module, built from several Eclipse projects, some of which are
dependencies of both modules, as well as many third party jars, both
open source (many of which themselves use Maven, of course) and proprietary.
Current build process is very rudimentary. The Eclipse projects do not
currently use Maven naming standards for directories. To do builds, the
simple Eclipse Export menu options are currently used. Deployment is
manual and there are some annoying manual post-export tasks that must be
run. Version control uses subversion, including a big ugly "project"
containing static copies of binary jars. These are my main reasons for
considering conversion to Maven.
Questions:
1. Are there articles around detailing "war stories" about making the
kind of move I am contemplating? I would like to read such before I get
started. I have just purchased Maven: The Definitive Guide, and while
the information there is very good, it tends to assume a start from
scratch. I would like to keep the history in the Subversion respository
if possible.
2. Would I be better served by renaming directories at the start to
Maven "Convention over Configuration" standards or by overrriding the
defaults all the way down the line?
3. Would I be better off building a local network repository containing
both the open source and proprietary code needed or would it be better
to create a local repository only for the proprietary stuff and get the
open source stuff from a remote repository.
Thanks.
Steve Cohen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
