Hi Mark, The new plugin works great.
The old plugin was definitely declared in my project's pom, so I'm not sure why it resolved the new one. In case it helps, it was actually declared in a parent pom and inherited. Thanks, -Evan On Thu, Jun 19, 2008 at 2:12 AM, Mark Hobson <[EMAIL PROTECTED]> wrote: > 2008/6/18 Evan Worley <[EMAIL PROTECTED]>: > > Thanks for all the info Mark, I greatly appreciate it. > > > > We will move onto the codehaus plugin immediately. > > Cool, let me know if you have any problems with the new version by > raising an issue. > > > I'm still curious how "apt" can suddenly resolve to a new plugin without > any > > POM changes. It seems like we wouldn't want that to happen? Or perhaps > in > > Maven 2.1 a "conflict resolver" would've solved this problem? I am > assuming > > that I picked up the codehaus plugin transitively, since I don't have any > > direct dependencies on it (yet). > > You shouldn't have had a problem if the plugin was declared in your > project's pom. I'm guessing it wasn't declared and so Maven picked up > the Mojo version via the plugin resolution order Brian described > earlier. Plugins won't be picked up transitively. > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
