[mojo-dev] [jira] Commented: (MOJO-224) maven-findbugs-plugin for maven 2

[ http://jira.codehaus.org/browse/MOJO-224?page=comments#action_55375 ] Cyrill Ruettimann commented on MOJO-224: The Plug-In does not work on any computer other than the developers workstation because of a file system reference of the coreplugin.jar.

[mojo-dev] [jira] Commented: (MOJO-228) Maven MiniJar Plugin to mimimize dependency jars

[ http://jira.codehaus.org/browse/MOJO-228?page=comments#action_55361 ] Brian Fox commented on MOJO-228: Code, license and site seem to be in order. I committed the code to the sandbox. There seems to be a pathing error when I try to run it: (tried 2.0 and

[mojo-dev] [jira] Created: (MOJO-228) Maven MiniJar Plugin to mimimize dependency jars

Maven MiniJar Plugin to mimimize dependency jars Key: MOJO-228 URL: http://jira.codehaus.org/browse/MOJO-228 Project: Mojo Type: New Feature Versions: 2.0.1 Reporter: Torsten Curdt Attachments: maven-mini

[mojo-dev] [jira] Commented: (MOJO-222) xmlbeans-jsr173-api not available in any repository

[ http://jira.codehaus.org/browse/MOJO-222?page=comments#action_55335 ] Carlos Sanchez commented on MOJO-222: - AFAIK That jar can't be on the repo, however the standard name should be used (javax.*) > xmlbeans-jsr173-api not available in any repository

[mojo-dev] [jira] Assigned: (MOJO-222) xmlbeans-jsr173-api not available in any repository

[ http://jira.codehaus.org/browse/MOJO-222?page=all ] Corridor Software Developer reassigned MOJO-222: Assign To: Corridor Software Developer > xmlbeans-jsr173-api not available in any repository >

Re: [mojo-dev] [vote] commit privs for Mike Perham

Of course. Actually, I should have put that there in a first place. I think I misunderstood what Jason told me (I actually thought he asked me to put the component in the mojo-sandbox). Anyway ... We can put that in the [EMAIL PROTECTED] Stéphane On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote

Re: [mojo-dev] Commit access request (was: [vote] commit access for stephane nicoll)

Yep - we'll try and get this moving for all three of you at once. - Brett Fabrizio Giustina wrote: > On 1/9/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: >> +1, but I though that we said that any Maven 2 core or plug-in developer >> could simply request access for the Mojo project as we threat t

Re: [mojo-dev] [vote] commit privs for Mike Perham

Stephane, Can we put that in the sandbox at Apache along with the issue stuff so it all stays together? You should do that since it is your work and you are a committer there. Mike can also work on it there. - Brett Stephane Nicoll wrote: > If mike wants to work on the changes plugin, I think he

Re: [mojo-dev] junitdoclet plugin

Hi Kris, thanks for your feedback. I have finished the docs and created a JIRA ticket (with an attached ZIP file) under http://jira.codehaus.org/browse/MOJO-227. Hope I am not pushing too hard! Thanks for your great work. Ralf Kris Bravo wrote: Thanks for the offer. We could add th

[mojo-dev] [jira] Created: (MOJO-227) Maven-2 Junitdoclet Plugin

Maven-2 Junitdoclet Plugin -- Key: MOJO-227 URL: http://jira.codehaus.org/browse/MOJO-227 Project: Mojo Type: New Feature Reporter: Ralf Quebbemann Attachments: junitdoclet-maven-plugin.zip There was recently a request for a junitdoclet

Re: [mojo-dev] [vote] commit privs for Mike Perham

If mike wants to work on the changes plugin, I think he should have a look to the maven-changes component I have committed recently in the mojo-sandbox. This component is used to externalize the changes.xml file management (to be used by the Wiki providers for instance). Code which is currently in

Re: [mojo-dev] [jira] Created: (MOJO-226) Cobertura plugin forces ASM 2.1 on projects

This might be a duplicate of this one: http://jira.codehaus.org/browse/MOJO-194?! Ralf mike perham (JIRA) wrote: Cobertura plugin forces ASM 2.1 on projects --- Key: MOJO-226 URL: http://jira.codehaus.org/browse/MOJO-226 P

[mojo-dev] mojo svn links

I just noticed today that pretty much all the links in the parent pom are messed up for svn. On the plugin report we have: http://svn.mojo.codehaus.org/trunk/mojo/dependency-maven-plugin https://svn.codehaus.org/mojo/scm/trunk/mojo/dependency-maven-plugin https://svn.codehaus.org/mojo/trunk/mojo/de

[mojo-dev] [jira] Created: (MOJO-226) Cobertura plugin forces ASM 2.1 on projects

Cobertura plugin forces ASM 2.1 on projects --- Key: MOJO-226 URL: http://jira.codehaus.org/browse/MOJO-226 Project: Mojo Type: Bug Reporter: mike perham The Cobertura plugin puts asm 2.1 in the classpath. My project us

Re: [mojo-dev] junitdoclet plugin

Thanks for the offer. We could add the plugin to the mojo sandbox. While you're working on the documentation, please look at http://mojo.codehaus.org/development/guidelines.html for plugin guidelines and make sure everything is accounted for. Once you've finished, you can add a JIRA ticket and att

Re: [mojo-dev] [vote] commit privs for Mike Perham

Arnaud HERITIER a écrit : +1 Arnaud On 1/9/06, *Emmanuel Venisse* <[EMAIL PROTECTED] > wrote: +1 Emmanuel Jason van Zyl a écrit : > Hi, > > Mike would like to contribute to the changes plugin so I propose we give > him access. Mike

[mojo-dev] Commit access request (was: [vote] commit access for stephane nicoll)

On 1/9/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > +1, but I though that we said that any Maven 2 core or plug-in developer > could simply request access for the Mojo project as we threat the Mojo > project as a simple extension of the plugin project at Apache? Could I request access to the m

Re: [mojo-dev] [vote] commit privs for Mike Perham

+1 ArnaudOn 1/9/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: +1EmmanuelJason van Zyl a écrit :> Hi,>> Mike would like to contribute to the changes plugin so I propose we give> him access. Mike is a committer on Maven SCM and wants to use his Maven > SCM know-how to improve the changes plugin>>

Re: [mojo-dev] [vote] commit access for stephane nicoll

+1 ArnaudOn 1/9/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: Jason van Zyl wrote:> Hi,>> Stephane is a committer on m2 and would like to do some work on some> mojos. I think we can certainly allow him access!>> +1+1, but I though that we said that any Maven 2 core or plug-in developer could simp

[mojo-dev] [jira] Closed: (MOJO-211) xmlPath not the same for announcement and changes reports

[ http://jira.codehaus.org/browse/MOJO-211?page=all ] Allan Ramirez closed MOJO-211: -- Assign To: Allan Ramirez Resolution: Won't Fix I believe that this is already fixed in the svn. > xmlPath not the same for announcement and changes reports > -