Wow.. That link is really an interesting revelation to me... The crazy thing is that nowhere in the output does it say that it's excluding those jars. In fact, it just lists them as if they ARE included just like that other jars...
But that link is only about Eclipse. What I don't understand is why wouldn't it be on the classpath for command-line compilation... Is there another line like that 'if' statement somewhere else forcing maven to exclude those jars from the classpath? There must be, right? I guess, since we are using our own archiva, I can just rename them and reimport them to archiva using a different name... "by any other name it's just a sweet?" :-) Thanks, Yaakov. On Thu, Oct 22, 2009 at 9:33 PM, Barrie Treloar <baerr...@gmail.com> wrote: > On Fri, Oct 23, 2009 at 11:53 AM, Paul Benedict <pbened...@apache.org> wrote: >> Please see: >> http://jira.codehaus.org/browse/MECLIPSE-584 >> >> Since 2.6 of the Maven Eclipse Plugin, AspectJ jars are no longer >> honored (by default) since a separate plugin controls AJDT features. >> As you will read in the ticket, if you wish to reverse this feature, >> add <ajdtVersion>none</ajdtVersion>. > > Is there a FAQ/Documentation/Example on the plugin's documentation > page for this? > > If not, someone want to contribute one so it can get included. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
