It seems like we would need an ASM based post processor to analyze it before 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 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 need to get *exported* as compile dependencies and which can get exported as runtime depedencies. Projects that don't use implementation inheritance will be able to trim down their exported compile time dependencies to nil. Implementation inheritance of any class relegates that class's library to being exported as a compile 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 & > plexus-utils version - Sender is forged (SPF Fail) > > Well, I requested long ago a setting for maven to inherit all > deps as runtime by default ... :-) > > http://jira.codehaus.org/browse/MNG-2589 > > - 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]
