* Frank Bille:
> IMO I think we should get this release to IPMC, not worrying
> about functional issues. I know it takes Martijn quite a while
> to do a release (Wicket *is* a big project with many subprojects
> so it will take some time to release) and this release here is
> only for IPMC.
In theory, releasing is the matter of running three commands, once
the build procedure is written: svn cp, svn switch, and release.sh
IMO what takes a lot of time is trying to tweak the assembly
plugin, discovering the numerous parameters, keeping uptodate with
the development branch of the assembly plugin and building it
yourself. If you build the release the Maven way, you have to be
satisfied with the limitations of the existing tools and cope with
them like we do currently, or otherwise start coding a new plugin
in Java with the Maven API. And there is absolutely no shame in
doing so: we need a custom build procedure because every piece of
released software differs slightly from eachother.
Therefore I proposed to start an Ant-based release build that will
allow us to have more fine-grained control over the assembly part
of the release build. It's not urgent as we won't be releasing to
the public in the next couple of days. But if at any time you
feel that the current build procedure needs to be revised, please
give a notice saying « hey, it's too much of a hassle trying to
build with the assembly plugin, let's give a try to something
else », I'll be there to help.
This is not about killing Maven, as many of you are very confident
with it, but it is about releasing Wicket in a predictable,
professional and reliable way.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
