maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Perham" <Mike.Per...@webifysolutions.com>
Subject RE: [important] plugin statuses
Date Wed, 25 Jan 2006 14:53:20 GMT
About that... I'm still waiting on feedback on MCLOVER-19.  See my last
three comments there.

-----Original Message-----
From: Vincent Massol [mailto:vmassol@pivolis.com] 
Sent: Wednesday, January 25, 2006 2:35 AM
To: 'Maven Developers List'
Subject: RE: [important] plugin statuses

I'm maintaining the Clover plugin (as time permits). It's already in a
good shape and I believe most issues are feature requests. It's still
missing lots of features when compared with the m1 version.

I'm happy for any help though (Note that Mike Perham is already
helping).

Thanks
-Vincent

> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: mercredi 25 janvier 2006 03:03
> To: Maven Developers List
> Subject: Re: [important] plugin statuses
> 
> Anyone want to update:
> clean, ear, ejb, jar, plugin, rar, war, compiler, resources, source, 
> ant, antlr, release, repository, idea, eclipse, verifier, checkstyle, 
> clover, javadoc, projectinforeports below?
> 
> I'll pass back over this and fill in the gaps at the end of the month,

> then this will become a monthly activity (as segregated below).
> 
> Let me know if you have any thoughts on the effectiveness of this.
> 
> - Brett
> 
> Brett Porter wrote:
> > Hi,
> >
> > Some time back there was a proposal about plugin maintainers, and I 
> > adapted that proposal for m2 a little. I don't think that our 
> > community fits assigning a person to do something, so I'd like to
try this.
> >
> > Next Wednesday we have a board report due. I'd like to get the 
> > status of
> > *all* the plugins summarised by people currently interested/working 
> > on them. Then we'll get some others to take a look and if something 
> > looks close to a release or particularly neglected we can deal with
it.
> >
> > While we do all now, I think we can do a small group each month, 
> > completing them all by the end of the next board report. So here I 
> > assign some for end Jan, some for end Feb, some for end Mar. 
> > Remember, this time we need to do them all.
> >
> > We can try this inline, but maybe next time we need to find a better
> way.
> >
> > Anyone have additional thoughts on this?
> >
> > To be completed by Jan, April, July, Oct clean assembly
> >   * Cleaned up several issues. Prep release next month. New 
> > functionality and significant bugfixes. X outstanding issues ear ejb

> > jar plugin rar war compiler deploy
> >  * Just released. 1 outstanding minor issue install
> >  * Just released. No outstanding issues surefire
> >  * Just release. X outstanding issues resources source
> >
> > To be completed by Feb, May, Aug, Nov ant antrun
> >  * Recently released. X outstanding issues.
> > antlr
> > release
> > repository
> > help
> >  * Preparing release. 2 new feature requests in JIRA for next
release.
> > idea
> > eclipse
> > verifier
> >
> > To be completed by Mar, Jun, Sep, Dec checkstyle clover javadoc pmd
> >  * Release in progress. No outstanding issues.
> > project-info-reports
> > site
> >  * Significant new work. Nearing 2.0 release. X outstanding issues
> >
> >
> > Thanks!
> > - Brett
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For 
> > additional commands, e-mail: dev-help@maven.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For 
> additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message