:D Yes, you have access.
Cheers, Brett Mike Perham wrote: > Ah, I'm starting to see the hazy outline of your grand scheme. It's > just crazy enough to work. > > Do I have commit access to the sandbox as a maven plugin committer? If > so, I'll start nosing around and see if I can't move Stephane's > maven-changes mojo code into the sandbox and get a > maven-issue-provider-file project up and running. > > mike > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Monday, January 23, 2006 9:03 PM > To: dev@mojo.codehaus.org > Subject: Re: [mojo-dev] Remove JIRA report from changes-maven-plugin > > Hi Mike, > > I agree with splitting this up now, but would like to treat changes.xml > as an "issue tracker". > > ie: > maven-issue-provider-api > maven-issue-provider-jira > maven-issue-provider-file (changes.xml) > maven-issue-provider-bugzilla|trac|clearquest|scarab|sourceforge > > Then: > maven-issue-provider-plugin > with: > issue-provider:changes-report > issue-provider:roadmap-report > > and > maven-announcement-plugin > with: > announcement:generate > announcement:mail > using the issue-provider library to source content either from JIRA, > changes.xml, etc > > I think the best place to work on it is the sandbox at Maven where the > issue tools are now. > > WDYT? > > - Brett > > Mike Perham wrote: >> I'd like to propose removing the JIRA report from the >> changes-maven-plugin. I think this report would be much better suited > >> packaged into another issue management reporting plugin whereas the >> changes plugin is devoted to reporting on a simple developer-authored >> changelog. >> >> I'll take 48 hrs of silence as consent. If you are using this >> functionality or have a problem with this move for other reasons, >> please speak up. >> >> mike >> > >
