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: > 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 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 the changes plugin needs to be removed and > > I assume it should depend on this maven-changens component instread. I > > have no idea where to place the component though. > > > > Also, Jason had nice ideas regarding changes management (changes.xml, > > issue tracker system, etc). Jason, maybe you could wrap up the > > discussion we had on IRC? > > > > Thanks, > > Stéphane > > > > > > On 1/9/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: > >> 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 > >> > >> +1 > >> > >> -- > >> > >> jvz. > >> > >> Jason van Zyl > >> jason at maven.org > >> http://maven.apache.org > >> > >> Simplex sigillum veri. (Simplicity is the seal of truth.) > >> > > > > > > -- > > .::You're welcome ::. > > > -- .::You're welcome ::.
