Let me introduce what I'm doing in my company. We have some
maven-java-simple projects used in other projects. These projects are
considered common code. Then, our projects are all maven-j2ee-simple
projects. These projects have a root pom. Then, we have inside a folder
called servlets, with at least a webapp inside. Then, a projects folder,
with some jar modules inside. Finally, we have the ear folder, with only a
project that generates an ear. We have another folder, called ejbs, to
create ejbs inside, but, as we are using Spring framework, we don't have any
ejb yet. This is the structure of a project:
/-root-project/
-/ear/
-/projects/
-/servlets/
-/ejbs/
2010/1/24 Josh Stone <pacesysj...@gmail.com>
> I'm in the process of moving our company over to Maven, and am not sure of
> the best way to organize our existing projects. Currently our application
> stack consists of two dozen projects with various dependencies on each
> other. For projects that a developer is actively working on, these should
> be
> built locally from source whereas dependencies on all other projects should
> be resolved from jars in the maven repository. I've setup 1 pom for each
> project, but there are a few things I'm not sure about:
>
> Since any given project could be built locally from source or from jars, do
> I need two poms for each project, one to serve as a "build" pom and one to
> reference jars?
> Should I store the pom(s) in SCM along with having them in the maven
> repository?
>
> Any tips are appreciated,
> Josh
>
--
"Everything should be made as simple as possible, but not simpler" Albert
Einstein
