+1 for Maven, I offered my services in the past...without
success...maybe 2010 is a lucky year ;)
Antonio Petrelli wrote:
2010/4/10 Claude Brisson <[email protected]>:
Sorry to jump in as an intruder, but if Maven was used, isolating non
stable or experimental code is very easy.
Long time ago I volunteered to make a Maven reorganization in a
sandbox directory, if it was available. This offer, obviously, is
still valid :-)
and still sounds awesome, though we don't split svn access up by
directory, so i'm not sure how to provide you access to a sandbox
directory without just making you a committer. do you know how/if
that can be done? i suppose we could just ask infra@ about it, but
they're rather busy right now with some...er..problems.
As long as it's feasible while keeping the actual ant build system
alive, I'm ok. It's pretty handy as is...
In fact no, at least not completely.
The reorganizations means also moving code around, isolating unit
tests and integration tests, modularizing everything (a module for
Struts support, a module for pure servlet, etc., a module for non
servlet related code, etc.). Recreating an Ant build is *very*
difficult.
And, trust me, once you gest accustomed to Maven you won't ever get
back. You may feel it difficult now, since it is "counter intuitive"
to your Ant habits, but it gets better every day.
Moreover, a mavenized project is available to everyone, without
messing with libraries, particular directories, configuration etc.
Download, build, run, have fun!
Sheesh! I feel like an evangelist :-P
Anyway, what I want to do is playing in a sandbox, that will contain a
branch of the trunk. I will work in this branch and won't touch the
regular code, at least until you like it :-)
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
