Karol Dowbecki created MOJO-1795:
Summary: jasperreports-maven-plugin upgrade
Key: MOJO-1795
URL: https://jira.codehaus.org/browse/MOJO-1795
Project: Mojo
Issue Type: Improvement
Co
Karl Heinz Marbaise created MAPPASM-134:
---
Summary: Create integration test based on the maven-invoker-plugin
Key: MAPPASM-134
URL: https://jira.codehaus.org/browse/MAPPASM-134
Project: Mojo AppAs
[
https://jira.codehaus.org/browse/MWEBTEST-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286546#comment-286546
]
Kennard Consulting commented on MWEBTEST-3:
---
Siegfried,
Thanks for your reply.
I'm not
James Nord created MJAXB-58:
---
Summary: Add native support for episodes
Key: MJAXB-58
URL: https://jira.codehaus.org/browse/MJAXB-58
Project: Maven 2.x JAXB 2.1 Plugin
Issue Type: New Feature
Af
I think we are fine.
Karl can you ask membership to the project tru xircle ?
2011/12/20 Dennis Lundberg :
> +1
>
> On 2011-12-19 17:48, Olivier Lamy wrote:
>> Hello,
>>
>> Karl want to help on appassembler plugin.
>>
>> So here my +1 for him as a committer.
>>
>> Vote open for 72H (and +1 is the o
We might need to reassign all projects. Jason told me a lot of the plugins were
automaticly assigned to him. So right now only a small group has a valid
assignee.A suggestion: remove the project leads and start all over again.Active
developers can (re)claim there favorite plugins.That would giv
+1
2011/12/21 Robert Scholte :
> Assuming Mark has completed the move to the openjpa project, here's my +1
>
> -Robert
>> Date: Wed, 21 Dec 2011 10:08:44 -0800
>> From: k...@kohsuke.org
>> To: dev@mojo.codehaus.org
>> CC: pg...@redhat.com
>> Subject: Re: [mojo-dev] [VOTE] Retire openjpa-maven-plug
Assuming Mark has completed the move to the openjpa project, here's my +1
-Robert > Date: Wed, 21 Dec 2011 10:08:44 -0800
> From: k...@kohsuke.org
> To: dev@mojo.codehaus.org
> CC: pg...@redhat.com
> Subject: Re: [mojo-dev] [VOTE] Retire openjpa-maven-plugin
>
>
> +1
>
> On 12/21/2011 06:59 AM
+1
On 12/21/2011 06:59 AM, Paul Gier wrote:
Hi,
Given that this plugin is now officially part of the openjpa project
[1][2], I think it makes sense to retire it here.
The vote is open for 72 hours and will succeed by lazy consensus.
Here's my +1
Thanks!
[1]http://markmail.org/message/rbmcj
+1
On Wed, Dec 21, 2011 at 9:59 AM, Paul Gier wrote:
> Given that this plugin is now officially part of the openjpa project
> [1][2], I think it makes sense to retire it here.
> The vote is open for 72 hours and will succeed by lazy consensus.
> Here's my +1
>
> [1]http://markmail.org/message/
+1
On 21 December 2011 14:59, Paul Gier wrote:
> Hi,
>
> Given that this plugin is now officially part of the openjpa project
> [1][2], I think it makes sense to retire it here.
>
> The vote is open for 72 hours and will succeed by lazy consensus.
>
> Here's my +1
>
> Thanks!
>
> [1]http://markma
+1
/Anders (mobile)
Den 21 dec 2011 16.11 skrev "Paul Gier" :
> Hi,
>
> Given that this plugin is now officially part of the openjpa project
> [1][2], I think it makes sense to retire it here.
>
> The vote is open for 72 hours and will succeed by lazy consensus.
>
> Here's my +1
>
> Thanks!
>
> [
+1
On Wed, Dec 21, 2011 at 3:59 PM, Paul Gier wrote:
> Hi,
>
> Given that this plugin is now officially part of the openjpa project
> [1][2], I think it makes sense to retire it here.
>
> The vote is open for 72 hours and will succeed by lazy consensus.
>
> Here's my +1
>
> Thanks!
>
> [1]http:/
Hi,
Given that this plugin is now officially part of the openjpa project
[1][2], I think it makes sense to retire it here.
The vote is open for 72 hours and will succeed by lazy consensus.
Here's my +1
Thanks!
[1]http://markmail.org/message/rbmcjwt767mbcfy2
[2]http://openjpa.apache.org/enhance
Jesse,
All that will be required in the new year is one of
Option 1: review the jira to see if there is somebody you can pass the
project off to (and call a vote to add them as a committer if
necessary) if you cannot find somebody to pass the project off to,
then you follow option 2
Option 2. Ju
[
https://jira.codehaus.org/browse/MWEBTEST-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286500#comment-286500
]
Michael Wenig commented on MWEBTEST-4:
--
Hi Siegfried,
sorry for the delay :-)
Currently I do
I'm thinking option 3 or possibly option 2. In my world, a retired
project/mojo means that there is no active development going on (which
there isn't in this case). It does not necessarily mean that it's not
mature, but simply that it is (very) unlikely that any ticket/issue
will be handled. With t
[
https://jira.codehaus.org/browse/MWEBTEST-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286490#comment-286490
]
Siegfried Goeschl commented on MWEBTEST-4:
--
Hi Michael,
any feedback from your side?
[
https://jira.codehaus.org/browse/MWEBTEST-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286489#comment-286489
]
Siegfried Goeschl commented on MWEBTEST-3:
--
Hi Kennard,
upgrading to a new WebTest versio
Hi Stephen,
Stephen Connolly-2 wrote:
>
>>Project: http://svn.codehaus.org/mojo/trunk/mojo/appassembler
>> Last revision: 2011-11-09
>> Active devs: brett, carlos, oching, olamy
>
>> The following projects have had no activity in the last year
>> ==
>
Harald Raffelt created MFINDBUGS-156:
Summary: xmlOutput Filename changed
Key: MFINDBUGS-156
URL: https://jira.codehaus.org/browse/MFINDBUGS-156
Project: Maven 2.x FindBugs Plugin
Issue T
Hi all,
Option 1 or 3 for me.
There is several reason for not having activity on a mojo project :
maturity of a plugin (and it could been kept alive), replacement by another
plugin or just inactivity of the team.
I am still available to help for managing my
plugin (fitnesse-maven-plugin ).
Philip
I see a few options:
Option 1:
We divide up the projects among the active developers, each active
developer has a look in JIRA to see if there are any recent JIRAs with
patches of semi-reasonable quality, and we try and get the people
submitting such patches to become active committers for those
p
The following are the projects which have at least one active
developer (after my emeritus drive)
==
Project: http://svn.codehaus.org/mojo/trunk/mojo/animal-sniffer
Last revision: 2011-08-28
Active devs: kohsuke, olamy, stephe
24 matches
Mail list logo
