Noel J. Bergman wrote:
I am not against using Maven, but I figured we would
wait for an official Maven 2 release.
In lieu of Ant, or as an alternative for those who want to use Maven?
Development of the maven-osgi plugin, or maven-felix plugin can just
continue. And from what I've heard is that the maven team suggests that
the M2 current release is pretty solid and can be used by other projects.
I haven't found the time yet to tranform the Wicket project to m2, but
I'm anxious to get it going.
If more people are -1 on M2 before it is final, I'd suggest using M1.0.2
(M1.1 is also still beta).
On the ant vs maven topic: the Wicket team uses maven for the internal
builds, and when someone gets the source from CVS, that is all we
support. Our distribution is maven agnostic, though: we give the source,
the dependencies in a lib folder and a working ant build.xml for people
to use in the distribution, and we also supply the maven files. This way
we cater both worlds in the best possible way we can. Our CVS isn't
'poluted' with jar files, and our users have a full distribution,
keeping the Hani's of this world happy :-)
Martijn
