Mark Hobson wrote: > On 26/02/07, Jörg Schaible <[EMAIL PROTECTED]> wrote: >> 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>). > > Oh the irony ;) > >> 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? > > Yeah, I'd be +1 merging maven-dependency-analyzer-plugin into > maven-dependency-plugin as previously discussed. It could be merged > into trunk since it's rather unobtrusive, but feel free to branch if > needs be.
I'm no Maven dev, so I stick with the sandbox. Point is, that we have the maven-dependency-plugin on the trunk, a maven-dependency-plugin-MDEP-50 branch and two releases in tags. So where should I branch from? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
