Re: splitting plugin dev into a separate list?

2008-08-13 Thread Dennis Lundberg
nd was having trouble since it was drowned out in plugin development discussion and votes. Considering plugin dev occurs on more on the stable basis of previous versions of Maven it seemed to make some sense to use separate lists, even if the audience is largely similar. For commits I already filt

Re: splitting plugin dev into a separate list?

2008-08-12 Thread Jamie Whitehouse
related to > >> Maven core and was having trouble since it was drowned out in plugin > >> development discussion and votes. > >> > >> Considering plugin dev occurs on more on the stable basis of previous > >> versions of Maven it seemed to make some sense to

Re: splitting plugin dev into a separate list?

2008-08-12 Thread Vincent Siveton
ing back through the archives for a couple of things related to >>> Maven core and was having trouble since it was drowned out in plugin >>> development discussion and votes. >>> >>> Considering plugin dev occurs on more on the stable basis of previous >>>

Re: splitting plugin dev into a separate list?

2008-08-12 Thread Olivier Lamy
for a couple of things related to >>>> Maven core and was having trouble since it was drowned out in plugin >>>> development discussion and votes. >>>> >>>> Considering plugin dev occurs on more on the stable basis of previous >>>>

Re: splitting plugin dev into a separate list?

2008-08-12 Thread Benjamin Bentmann
Brett Porter wrote: Any other opinions? I can easily put mails from different lists back into the same post folder if I want but splitting mails from the same list according to their topic is more tricky ;-) So I am +1 for the split. If this is made in time, we could update our parent POMs

Re: splitting plugin dev into a separate list?

2008-08-12 Thread Arnaud HERITIER
bson wrote: > > 2008/8/8 Brett Porter <[EMAIL PROTECTED]>: >> >>> I was poking back through the archives for a couple of things related to >>> Maven core and was having trouble since it was drowned out in plugin >>> development discussion and votes.

Re: splitting plugin dev into a separate list?

2008-08-12 Thread Brett Porter
votes. Considering plugin dev occurs on more on the stable basis of previous versions of Maven it seemed to make some sense to use separate lists, even if the audience is largely similar. For commits I already filter the various pieces into separate folders, but that isn't as easy with dev traf

Re: splitting plugin dev into a separate list?

2008-08-08 Thread Mark Hobson
2008/8/8 Brett Porter <[EMAIL PROTECTED]>: > I was poking back through the archives for a couple of things related to > Maven core and was having trouble since it was drowned out in plugin > development discussion and votes. > > Considering plugin dev occurs on more on the sta

Re: splitting plugin dev into a separate list?

2008-08-07 Thread Paul Benedict
ion and votes. > > Considering plugin dev occurs on more on the stable basis of previous > versions of Maven it seemed to make some sense to use separate lists, even > if the audience is largely similar. For commits I already filter the various > pieces into separate folders, but

splitting plugin dev into a separate list?

2008-08-07 Thread Brett Porter
I was poking back through the archives for a couple of things related to Maven core and was having trouble since it was drowned out in plugin development discussion and votes. Considering plugin dev occurs on more on the stable basis of previous versions of Maven it seemed to make some

Re: maven 2 plugin dev question

2006-09-05 Thread fogwolf
---------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/maven-2-plugin-dev-question-tf2202791.html#a6152725 Sent from the Maven Developers forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven 2 plugin dev question

2006-09-01 Thread Arnaud Bailly
fogwolf <[EMAIL PROTECTED]> writes: > Hi there. > > I am converting my Maven 1 environment to Maven 2 & am running into an issue > with a plugin I'm trying to update. This plugin basically filters some > template files, replacing placeholder values, & places them within > directories under the pro

maven 2 plugin dev question

2006-09-01 Thread fogwolf
to keep them in CVS? If so, what would be the best way to access CVS from my Maven plugin - to use the Ant CVS task to check the files out to a temp directory, do the variable replacement & copy them over? Thanks! -- View this message in context: http://www.nabble.com/maven-2-plugin-dev-questi

RE: plugin dev

2005-02-03 Thread HEAD-RAPSON, David
It worked perfectly. Thanks very much indeed! -Original Message- From: Florin Vancea [mailto:[EMAIL PROTECTED] Sent: 03 February 2005 11:49 To: Maven Developers List Subject: Re: plugin dev Try something like this - Original Message

Re: plugin dev

2005-02-03 Thread Florin Vancea
Try something like this - Original Message - From: "HEAD-RAPSON, David" <[EMAIL PROTECTED]> To: Sent: Thursday, February 03, 2005 1:38 PM Subject: plugin dev > Hi, > I wonder if someone can help me. It's regarding a new

plugin dev

2005-02-03 Thread HEAD-RAPSON, David
Hi, I wonder if someone can help me. It's regarding a new maven plugin I'm writing. I'm using Maven and Jelly to execute a Java command as part of our build process. Following that I wish to execute an ant command, but I need an argument from the java. Ideally I'd like to know how to return a val