Jorg, Make a branch off of the trunk for now. Since these are separate goals, a merge will be easy later after the release.
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jörg Schaible Sent: Monday, February 26, 2007 2:47 PM To: [email protected] Subject: Re: Sandbox access Mark Hobson wrote: > On 26/02/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> If you're an apache committer then you're free to work no it and you >> already have permission. If you're not then mojo might be better >> where we can give you access to work on it. > > I've got mojo rights but not apache rights. Where it currently is is > probably the best place for it though since we discussed moving it's > functionality into the maven-dependency-plugin [1]. > > Mark > > [1] http://www.mail-archive.com/[email protected]/msg63738.html I can act as relay. Unfortunately I can only work on it in the evening, I cannot commit from the office (although we need the functionality there <grrrrrr>). The sandbox already contains shared/maven-dependency-analyzer and plugins/maven-dependency-analyzer-plugin. Should I create a branch for the maven-dependency-plugin (from trunk ??) and integrate the code of maven-dependency-analyzer-plugin? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
