> From: Ted Husted [mailto:[EMAIL PROTECTED]
> 
> Does anyone have any strong negative feelings toward Maven?
> <http://maven.apache.org>
> 
> It's been spreading like Borg lately. I haven't had to use it much
> myself yet, but the handwriting is on the wall, and so I'm reconciling
> myself to the inevitable. :)
> 
> If there weren't any objections, I thought I might try setting up the
> appropriate configuration files. This would not disturb anything we
have
> now, only provide an alternative build/documentation mechanism. If we
> like it, we could then keep it and use it for 2.2.1/2.3. Otherwise,
I'll
> retract it.

Woo hoo, someone that wants to put together a real release process and
build system!  You're my hero :-)

I like the maven concept, I just haven't had the time or inclination to
climb its learning curve.  If you're up for it, I'm +1.

My only requirement is that users must be able to check out the project
and build it without any extra configuration.  Of course, Maven is
supposed to help with this.

BTW, you mentioned releasing a 2.2.1... but I don't believe there have
been any commits (to the core) since 2.2.0.  Not much point :-)

I like the versioning scheme you described, which is what Orion has been
using for aeons now.  Releases always have increasing version numbers,
but new ones are labeled "experimental" and after-the-fact some are
labeled "stable".  I'm not sure how well sourceforge's system supports
that model, can we just rename releases with -experimental or -stable?

Jeff Schnitzer
[EMAIL PROTECTED]


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
[INVALID FOOTER]

Reply via email to