Michiel Meeuwissen wrote:
I was about to explore how we should finally start using maven, only to
find out that all existing project.xml's don't work with my version of maven
(2.0.4), which expects pom.xml files.
The good thing was that it at least started working immediately when I
figured out how to generate a pom.xml file.
So, I think we decided long ago that we should actually sooner or later
migrate to maven. The question arises though, are we going to migrate to
maven 1 or maven 2? Investing any time in learning how to use maven 1 seems
a bit folly.
Michiel
The maven1 build works for almost a year now. There are only some loose
ends like the rmmci applications and the testcases. The maven1 build
creates mmbase-module artifacts which contains the jar and all others
sources to install it in a war. This is all done by a maven-plugin. The
plugin can also extract the mmbase-module into a war. See the
example-webapp.
Maven2 will work to create the jars, but not what the mmbase-module
plugin can do. Maybe it is an idea to create a Maven2 plugin (Mojo) in
the component project which creates an artifact based on the new
componenet structure. Another option is to wait for a while, because it
is also on the cmscontainer roadmap 2007.
Nico
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
