It just fell off my radar. It still needs some work, so if there is
still some interest and volunteers what want to get it into shape I
can work that out with them. Anyone interested?
- Brett
On 16/09/2008, at 1:42 AM, Wendy Smoak wrote:
On Tue, May 22, 2007 at 7:05 PM, Brett Porter [EMAIL
On Tue, May 22, 2007 at 7:05 PM, Brett Porter [EMAIL PROTECTED] wrote:
Ok, there seems to be some interest. I will spend some time putting the code
into a suitable packaging / licensing structure and post it for a vote.
There was some interest in a conversion tool on #maven this morning.
Did
Ok, there seems to be some interest. I will spend some time putting
the code into a suitable packaging / licensing structure and post it
for a vote.
On 22/05/2007, at 5:46 AM, Brian E. Fox wrote:
But more importantly, it helps identify your dependency jars as
described in the proposal. In
Hi all,
DevZuz have developed some tools for build conversion as part of the
Maestro project and for internal use. If it is desired, we would now
like to donate that to the Maven project for others to enhance and re-
use. It would find a place both as an independent toolkit, and as an
Sounds helpful... though I'm kinda wondering what it would produce
for trivial and non-trivial ant and m1 projects. I'm not really sure
how such a tool could really figure out the right way to implement
the m2 build...
--jason
On May 21, 2007, at 12:15 AM, Brett Porter wrote:
Hi all,
Like Jason, I think it would be very helpful, but I would like to see the
extent that it can convert an ant script to a maven 2 project. I've written
and seen some very hairy ant scripts and I wonder how much this would
correctly pull from them.
Converting maven 1 projects to maven 2 is
On 21/05/2007, at 5:33 PM, Jason Dillon wrote:
Sounds helpful... though I'm kinda wondering what it would produce
for trivial and non-trivial ant and m1 projects. I'm not really
sure how such a tool could really figure out the right way to
implement the m2 build...
Well, it's definitely
Brett Porter a écrit :
On 21/05/2007, at 5:33 PM, Jason Dillon wrote:
Sounds helpful... though I'm kinda wondering what it would produce for
trivial and non-trivial ant and m1 projects. I'm not really sure how
such a tool could really figure out the right way to implement the m2
build...
I'm looking for others that are interested in working with or using
this - thoughts?
I would be interested using the dependency discovery from md5 feature
(currently have a need for this.)
-
To unsubscribe, e-mail: [EMAIL
But more importantly, it helps identify your dependency jars as
described in the proposal. In my experience this is a large percentage
of the conversion work for most projects.
I completely agree. This piece alone would be very handy.
10 matches
Mail list logo
