river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McGrady <mmcgr...@topiatechnology.com>
Subject Re: Deciding the Future
Date Mon, 08 Dec 2008 16:19:33 GMT
I would organizing the build for Maven and then giving a choice of ANT  
with SVN or Maven.

Mike


On Dec 8, 2008, at 3:57 AM, Greg Trasuk wrote:

>
> This reminds me of that quote - "Some people, when confronted with a
> problem, think 'I know, I?ll use regular expressions.' Now they have  
> two
> problems".
>
> I'm not in favour of Maven.  I can see restructuring the build  
> somewhat
> for Ant (remember, the structure really comes from being built with a
> makefile, before there was an Ant).
>
> Cheers,
>
> Greg.
>
> On Mon, 2008-12-08 at 03:44, Jools wrote:
>> +1
>>
>> I've love to see the codebase move over to a maven build.
>>
>> Over the last 9 months we have moved all our projects over to  
>> maven, with
>> great success.
>> Our build and release procedures are greatly reduced, and getting  
>> developers
>> up and running with their ide's.
>>
>> I'd be happy to Log a JIRA and take a lead on this, what do others  
>> think ?
>>
>> --Jools
>>
>>
>>
>>
>>
>> 2008/12/8 Jeff Ramsdale <jeff.ramsdale@gmail.com>
>>
>>> Niclas,
>>> Once again I very much agree with you. Dan's got a good point  
>>> about two
>>> jars
>>> (-dl and non-dl) resulting from each service component, though.
>>>
>>> I know this will induce groans from some parties but Apache River  
>>> would
>>> really benefit from a Maven build. The dependencies between  
>>> modules are
>>> complex as is the generation of the artifacts. Maven would allow  
>>> for a
>>> restructuring that clarifies the source structure while supporting  
>>> the
>>> generation of composite artifacts. You might look into the Maven  
>>> Classdep
>>> Plugin that Chris Sterling introduced several years ago: <
>>> https://maven-classdep-plugin.dev.java.net/>. It could make sense  
>>> to bring
>>> this plugin into the Apache River fold, incidentally. Use of this  
>>> plugin
>>> could also help increase uptake among the Maven developer crowd as  
>>> it
>>> simplifies the generation of artifacts for Jini services.
>>>
>>> A huge benefit of a Maven-based build is the ability to generate  
>>> metadata
>>> for most of the popular IDEs. This has proven to be incredibly  
>>> useful on my
>>> teams and allows for a multiplicity of IDEs to be used against the  
>>> same
>>> codebase.
>>>
>>>
> -- 
> Greg Trasuk, President
> StratusCom Manufacturing Systems Inc. - We use information  
> technology to
> solve business problems on your plant floor.
> http://stratuscom.com
>

Michael McGrady
Senior Engineer
Topia Technology, Inc.
1.253.720.3365
mmcgrady@topiatechnology.com





Mime
View raw message