dev@glassfish.java.net

Re: GlassFish jars to maven repository

From: Ed Burns <ed.burns_at_sun.com>
Date: Wed, 3 May 2006 07:25:00 -0700

>>>>> On Wed, 03 May 2006 06:49:13 -0700, Jerome Dochez <Jerome.Dochez_at_Sun.COM> said:

JD> Dinesh Patil wrote:
>> Carla Mott wrote:
>>
>>> Not sure what this means
>>>
>>> Once above AIs are experimented successfully, send proposal to
>>> dev_at_glassfish to use ANT for GlassFish Workspace.
>>
>> Since we have experimented Ant for GlassFish Workspace (if that
>> doesn't work, there is no question we need to keep things as it is),
>> we now know that most of the commands work with Ant also, then we can
>> ask for feedback and inputs that should we go back to Ant or keep
>> maven for the benefits its bringing to current workspace?
JD> Hi Dinesh

JD> Can you list the benefits of keeping maven over the complete ANT based
JD> solution you experimented ?

Here's my unsolicited opinion on this. I've been using maven 2 on the
jsf-extensions project and I've come to like it a lot. As Kohsuke
pointed out, the glassfish build system is hard to learn. The main
value-proposition of maven is its *standardized* directory layout and
build structure. When I move from one maven project to another, I
*know* how it works.

The more of the world we can move to maven2 the easier it will be for
people to get productive when coming to a new project. That's what we
want for glassfish.

Ed

-- 
| ed.burns_at_sun.com  | {home: 407 869 9587, office: 408 884 9519 OR x31640}
| homepage:         | http://purl.oclc.org/NET/edburns/
| aim: edburns0sunw | iim: ed.burns_at_sun.com
| 08 Business Days until JavaOne SF 2006