Re: [mojo-dev] [VOTE] Retire openjpa-maven-plugin

2011-12-23 Thread Mark Struberg
+1 that's perfectly fine with me. Actually this version of the plugin is still usable for all openjpa versions < 2.2.0. We might update a page with a hint that this is in transition and people should also test out the version of the plugin over at openjpa.apache.org. LieGrue, strub >

RE: [mojo-dev] [VOTE] Options for dealing with inactive projects (was Re: Project status)

2011-12-23 Thread Robert Scholte
Dennis, thanks for adding those plugins to this page[1]. It should help to see which plugins will survive and which once won't. Still some plugins waiting for a caretaker... -Robert [1] http://irc.codehaus.org/display/MOJO/Plugin+reassignments > Date: Fri, 23 Dec 2011 21:43:05 +01

Re: [mojo-dev] [VOTE] Options for dealing with inactive projects (was Re: Project status)

2011-12-23 Thread Dennis Lundberg
Thanks for setting up the wiki page Robert. I went in there and added the list of plugins that Stephen sent out for possible retirement. If someone want to be the caretaker of a plugin just move the plugin from the list at the bottom of the page to the table at the top of the page and add your nam

Re: [mojo-dev] Continious Integration System for the mojo maven plugins

2011-12-23 Thread David Karlsen
There used to be a job running on Sonatype's server as well as bamboo. Den 23. des. 2011 17:13 skrev "Karl Heinz Marbaise" følgende: > Hi, > > i just wanted to know if there exist a CI system (like Jenkins, Hudson or > whatever) for the plugins in the mojo area? > > I configured temporarily the a

Re: [mojo-dev] Continious Integration System for the mojo maven plugins

2011-12-23 Thread Karl Heinz Marbaise
Hi Tony, Yes we use the bamboo : [1] I don't have the time to create a plan for you, someone will soon I hope. Ok..i checked i can do it my own... Many thanks for the link... [1] http://bamboo.ci.codehaus.org/browse/MOJO Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung Schu

Re: [mojo-dev] Continious Integration System for the mojo maven plugins

2011-12-23 Thread Olivier Lamy
Karl as you are in mojo dev group maybe you have karma to create it. http://bamboo.ci.codehaus.org/browse/MOJO do you have the "Create Plan" link ? 2011/12/23 Tony Chemit : > On Fri, 23 Dec 2011 17:13:29 +0100 > Karl Heinz Marbaise wrote: > >> Hi, >> >> i just wanted to know if there exist a CI

Re: [mojo-dev] Continious Integration System for the mojo maven plugins

2011-12-23 Thread Tony Chemit
On Fri, 23 Dec 2011 17:13:29 +0100 Karl Heinz Marbaise wrote: > Hi, > > i just wanted to know if there exist a CI system (like Jenkins, > Hudson or whatever) for the plugins in the mojo area? > Yes we use the bamboo : [1] I don't have the time to create a plan for you, someone will soon I hope

[mojo-dev] Continious Integration System for the mojo maven plugins

2011-12-23 Thread Karl Heinz Marbaise
Hi, i just wanted to know if there exist a CI system (like Jenkins, Hudson or whatever) for the plugins in the mojo area? I configured temporarily the appassembler plugin to use my own CI ...so no real problem ...but i just wanted to know... Kind regards Karl Heinz Marbaise -- SoftwareEntwi

[mojo-dev] [jira] (MGWT-322) message about outputdirectory is not necessary when using copyWebapp

2011-12-23 Thread Constantino Cronemberger (JIRA)
Constantino Cronemberger created MGWT-322: - Summary: message about outputdirectory is not necessary when using copyWebapp Key: MGWT-322 URL: https://jira.codehaus.org/browse/MGWT-322 Project:

Re: [mojo-dev] [VOTE] Options for dealing with inactive projects (was Re: Project status)

2011-12-23 Thread Javier Murciego
I volunteer to look after was6-maven-plugin. I asked for commit rights few months ago but until now I haven't have much free time. Thanks On Fri, Dec 23, 2011 at 9:11 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > yeah. i think #2 is a non runner, as some are resolved already a

Re: [mojo-dev] [VOTE] Options for dealing with inactive projects (was Re: Project status)

2011-12-23 Thread Stephen Connolly
yeah. i think #2 is a non runner, as some are resolved already as remain active... #1 and #3 are sufficiently similar that we could just do both: scan jira and ask users... but i think a case by case approach would be best... - Stephen --- Sent from my Android phone, so random spelling mistakes,