If your already changing the build system, migrating to SVN would also
be a very nice improvement I think, as Michiel already suggested.
--
Martin Sturm
Finalist IT Group - never stop developing!
http://www.finalist.com
E: martin.st...@finalist.com
T: +31882170882
M: +31615529147
Op 8 mrt 2009, om 19:32 heeft Nico Klasens het volgende geschreven:
Michiel Meeuwissen wrote:
On Wed, Mar 4, 2009 at 13:09, Nico Klasens <mmb...@klasens.net>
wrote:
Hello Michiel,
I have been playing around for some hours the last weeks with my
preferred
maven2 build structure. I commited the head to a subversion and
started
moving the files in the way I wanted it. See
http://nico.klasens.net/svn/trunk/mmbase/.
Big advatnages. Simple poms which use the provided mojo's instead
of our
own. Any level of rhe build can trigger a multimodule build.
I creatwd two mojo's. 1 for the INDEX files (copy of yours) and 2 an
RemoteGenerator for the rmmci build.
A lot is also usable in the current structure, but I would prefer
somthing
like mine.
I think your proposal is preferable above what is now in CVS. Though
on one hand I find some merit in our current, less complicated
directory structure (src, blocks, template, config, vs. src/main/
java,
src/main/webapp, src/main/config), on the other hand this default
maven directory structure is used more universally so probably more
readily understandable. That using that structure also simplifies the
pom's and largely obsoletes the Mojo I deviced is an argument too,
though I must say that I found the amount of code to arrange
everything quite modest.
The big disadvantages of changing the directory structure is that you
can't simply move things in CVS, so it would be best to migrate to
svn
first, and that it would be silly to try to keep the existing build
scripts working, so I'd propose to simply drop those. These are
hardly
technical probems though.
greetings,
Michiel
Just committed some maven stuff which was in my structure and could
be applied to the current one. It is now possible to run a full
multimodule build when you run mvn inside the <mmbase all checkout>/
maven directory. I don't mind the directory strucuture how it is in /
applications The ugliest part of the build is that the mmbase.jar is
build in the root. This prevents that the modules sectioncan be
added to the /pom.xml. I put it now in the /maven/pom.xml. The /
maven-base/pom.xml is still the master pom with overall project
information.
When the snapshots are installed in the mmbase.org repository then
it is even possible to only checkout a small project and build only
that one.
I think from now on I will only use the maven 2 build for the head.
Still 2 things are missing: 1 our integration tests and 2
documentation generation.
Nico
_______________________________________________
Developers mailing list
Developers@lists.mmbase.org
http://lists.mmbase.org/mailman/listinfo/developers
_______________________________________________
Developers mailing list
Developers@lists.mmbase.org
http://lists.mmbase.org/mailman/listinfo/developers
