Re: Plugin development & plexus-utils version

2008-05-02 Thread Benjamin Bentmann
Jörg Schaible wrote: Maybe a new scope +1 on that instead of some time-consuming ASM post analysis and POM rewriting. Benjamin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECT

Re: Plugin development & plexus-utils version

2008-05-01 Thread Tom Huybrechts
gt; generating the pom that gets deployed. > > > -Original Message- > From: William Ferguson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 29, 2008 7:01 PM > To: Maven Developers List; [EMAIL PROTECTED] > Subject: Re: Plugin development & plexus-utils version > >

Re: Plugin development & plexus-utils version

2008-05-01 Thread Jörg Schaible
On Mittwoch, 30. April 2008, William Ferguson wrote: > As Benjamin points out at the end of that Jira, the current behaviour is there to deal with use of libraries containing classes that extend classes in other libraries. > > Seems to me that we need a way to differentiate in our projects which

RE: Plugin development & plexus-utils version

2008-04-29 Thread Brian E. Fox
development & plexus-utils version As Benjamin points out at the end of that Jira, the current behaviour is there to deal with use of libraries containing classes that extend classes in other libraries. Seems to me that we need a way to differentiate in our projects which dependencies nee

Re: Plugin development & plexus-utils version

2008-04-29 Thread William Ferguson
e time dep, otherwise the library is exported as a runtime dep. William > -Original Message- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jörg Schaible > Sent: Wednesday, 30 April 2008 7:20 AM > To: dev@maven.apache.org > Subject: Re: Plugin development & >

Re: Plugin development & plexus-utils version

2008-04-29 Thread Jörg Schaible
Benjamin Bentmann wrote: >> Solved, the dependency was inherited transitively by >> maven-artifact-2.0.9. > > You should never rely on transitive dependencies if you directly use its > classes/methods in your code but always declare them directly. The goal > dependency:analyze > can help you a

Re: Plugin development & plexus-utils version

2008-04-29 Thread Benjamin Bentmann
Solved, the dependency was inherited transitively by maven-artifact-2.0.9. You should never rely on transitive dependencies if you directly use its classes/methods in your code but always declare them directly. The goal dependency:analyze can help you a big deal in ensuring all your dependenc

RE: Plugin development & plexus-utils version

2008-04-29 Thread Jörg Schaible
Jörg Schaible wrote: > Hi folks, > > developing a new plugin I made usage of plexus-utils 1.5.1. > Unfortunately this fails when I try to run the plugin in a > real project, because some classes seem outdated (missing method in > FileUtils): > > = %< > [FATAL ERROR] > com.el