Hello Sean,
I think we should talk about the release cycle of each artifact, first.
If artifacts have the same release cycle and version, the artifact
should belongs to the same svn module. And should organised as
multimodule build with parent-child poms, of cause. The assembly
descriptor should be a part of this svn module. Because we should be
able to reproduce a version from svn. (and creating a branch whould be
easy, too) (look at the thread 'problem getting 1.1.1 from svn')
The examples for tomahawk, sandbox.. should be a part of the projects
and not independ. (The same reason as assembly)
I added a 'publish' project which has a POM that deals exclusively
with the assembly stuff. Eventually it will also publish the nightly
builds to the website and publish the website as well.
Who invokes the nightly build?
I added javadoc for all subprojects (its in the top level POM.) We
want it for every subproject except the examples. Is there a way to
exclude this for just examples?
Also, if we remove the parent
reference in a project like tomahawk, can we still inherit from the
parent when the tomahawk POM is called from the parent POM?
I think this is not possible, the opposite yes.
Proposal: We eliminate the refs to the parent POM. I don't see a
reason to have them really.
Why you don't like it? (after 4 days)
I think users should be able to build
each of the subprojects independently.
If we have a SNAPSHOT repository this should not be a problem.
Maybe we could also get rid of
the reports from each individual project POM since site generation is
only really necessary for the entire project.
Maybe some reports are useful.
What do you think?
Sean
Maybe the site should be a own module and of cause with a parent ref.
Bernd
--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
