Mavenizing the Etch build tree

[Richard Bolkey <rb...@gmail.com>]

So, at what point should I start working on this :-D.

Re: Mavenizing the Etch build tree

["scott comer (sccomer)" <sc...@cisco.com>]

thanks, niclas!

scott out

Niclas Hedhman wrote:
> On Tue, Mar 3, 2009 at 9:36 PM, scott comer (sccomer) <sc...@cisco.com> wrote:
>   
>> agreed. i think the tree is well designed for mavenization.
>>
>> the only problem, perhaps not insurmountable, is that maven easily supports
>> only java. perhaps it is reasonable that on the the java build be supported.
>> the csharp build still requires ant...
>>     
>
> I think this page may assist in making the right choices;
> http://activemq.apache.org/building-csharp-code.html
>
>
> Cheers
> Niclas
>   

Re: Mavenizing the Etch build tree

[Niclas Hedhman <ni...@hedhman.org>]

On Tue, Mar 3, 2009 at 9:36 PM, scott comer (sccomer) <sc...@cisco.com> wrote:
> agreed. i think the tree is well designed for mavenization.
>
> the only problem, perhaps not insurmountable, is that maven easily supports
> only java. perhaps it is reasonable that on the the java build be supported.
> the csharp build still requires ant...

I think this page may assist in making the right choices;
http://activemq.apache.org/building-csharp-code.html


Cheers
Niclas
-- 
http://www.qi4j.org - New Energy for Java

Re: Mavenizing the Etch build tree

["scott comer (sccomer)" <sc...@cisco.com>]

agreed. i think the tree is well designed for mavenization.

the only problem, perhaps not insurmountable, is that maven easily 
supports only java. perhaps it is reasonable that on the the java build 
be supported. the csharp build still requires ant...

scott out

Niclas Hedhman wrote:
> On Fri, Feb 27, 2009 at 4:20 AM, scott comer <sc...@cisco.com> wrote:
>   
>> make a branch of 1.1, call it maven, and knock yourself out. it can't go
>> into 1.1 stream, we could merge it into something post 1.1.
>>
>> i'd rather have logging...
>>     
>
> Well, I would recommend to do it on trunk, but that the effort is not
> allowed to move anything around. That way, only a pom.xml will show up
> and can be ignored by everyone else who are not interested.
>
>
> Cheers
> Niclas
>   

Re: Mavenizing the Etch build tree

[Niclas Hedhman <ni...@hedhman.org>]

On Fri, Feb 27, 2009 at 4:20 AM, scott comer <sc...@cisco.com> wrote:
> make a branch of 1.1, call it maven, and knock yourself out. it can't go
> into 1.1 stream, we could merge it into something post 1.1.
>
> i'd rather have logging...

Well, I would recommend to do it on trunk, but that the effort is not
allowed to move anything around. That way, only a pom.xml will show up
and can be ignored by everyone else who are not interested.


Cheers
Niclas
-- 
http://www.qi4j.org - New Energy for Java

Re: Mavenizing the Etch build tree

[scott comer <sc...@cisco.com>]

make a branch of 1.1, call it maven, and knock yourself out. it can't go 
into 1.1 stream, we could merge it into something post 1.1.

i'd rather have logging...

thanks!

scott out

Richard Bolkey wrote:
> So, at what point should I start working on this :-D.
>
>