You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Yaakov Chaikin <ya...@gmail.com> on 2009/10/22 21:07:39 UTC
Aspectj jars refuse to get imported
Hi,
Perhaps, someone can point out to me what I am doing wrong...
I have the following simple pom.xml file:
**************
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>pull</groupId>
<artifactId>spring-aop-example</artifactId>
<packaging>jar</packaging>
<version>1.0-SNAPSHOT</version>
<name>Maven pull of dependencies project</name>
<dependencies>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjrt</artifactId>
<version>1.6.0</version>
</dependency>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjweaver</artifactId>
<version>1.6.0</version>
</dependency>
</dependencies>
</project>
**************
When I run 'mvn clean install', the proper JARs get pulled into my
local repository. However, when I need these on my classpath, they are
not there!
On top of that, running regular 'mvn eclipse:eclipse' DOES NOT import
them into eclipse like any other regular dependency! It's as if they
are not mentioned in the pom at all!
What am I doing wrong here? I've been using maven for years now and
have never seen this before.
Thanks,
Yaakov.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Yaakov Chaikin <ya...@gmail.com>.
Right... Forgot about that one. Thanks.
On Thu, Oct 29, 2009 at 8:36 AM, Paul Benedict <pb...@apache.org> wrote:
> Yup, it was already posted in the beginning of this thread. Yaakov, do
> not rename your jars but simply configure the plugin like you were
> told to before:
>
> <configuration>
> <ajdtVersion>none</ajdtVersion>
> </configuration>
>
> http://jira.codehaus.org/browse/MECLIPSE-594
>
> Paul
>
> On Thu, Oct 29, 2009 at 6:56 AM, Brian Fox <br...@infinity.nu> wrote:
>> Renaming it and installing it into your repo won't change anything if
>> it's getting added to the classpath on the commandline, so NO don't do
>> that. I believe someone already posted how to configure
>> eclipse:eclipse to add the aspect support. Or you can install
>> m2eclipse and use that instead.
>>
>> On Sun, Oct 25, 2009 at 8:42 AM, Yaakov Chaikin
>> <ya...@gmail.com> wrote:
>>> I spoke too soon. It does work on the command line... Given that it
>>> now work on the command line, are you still suggesting that I NOT
>>> renaming it and deploy it in our archiva under a different name? I
>>> guess, I am not sure how I would force it into Eclipse's .classpath
>>> any other way.
>>>
>>> Thanks,
>>> Yaakov.
>>>
>>> On Fri, Oct 23, 2009 at 7:39 PM, Brian Fox <br...@infinity.nu> wrote:
>>>> Can you send us some build logs with -X enabled? There is nothing in
>>>> core that should be excluding aspectj, so something else is at play
>>>> here. And loading them with a different coordinate into your repo
>>>> manager is going to cause problems later, that is just patching the
>>>> symptoms
>>>>
>>>> On Fri, Oct 23, 2009 at 4:09 PM, Yaakov Chaikin
>>>> <ya...@gmail.com> wrote:
>>>>> Oh, I see... However, classpath I was referring to was just regular
>>>>> classpath, not .classpath of eclipse... It's excluded from the regular
>>>>> Java classpath as well for some reason.
>>>>>
>>>>> Yaakov.
>>>>>
>>>>> On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk <ni...@gmail.com> wrote:
>>>>>> The plugins have their own versioning. He means the 2.8 release of the
>>>>>> eclipse plugin.
>>>>>>
>>>>>> Hth,
>>>>>>
>>>>>> Nick Stolwijk
>>>>>> ~Java Developer~
>>>>>>
>>>>>> IPROFS BV.
>>>>>> Claus Sluterweg 125
>>>>>> 2012 WS Haarlem
>>>>>> http://www.iprofs.nl
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>>>>>>
>>>>>>> > This won't happen anymore in (unreleased) 2.8. I agree with Barrie
>>>>>>> > that this should be documented for users of 2.6 and 2.7. Anyone want
>>>>>>> > to submit a patch for one of the help pages?
>>>>>>>
>>>>>>> Version 2.8 of maven? I am running maven 2.0.9 which IS released...
>>>>>>> From what I see on the maven's page, the latest version is 2.2.1. They
>>>>>>> are working on 2.8 already??
>>>>>>>
>>>>>>> Yaakov.
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Paul Benedict <pb...@apache.org>.
Yup, it was already posted in the beginning of this thread. Yaakov, do
not rename your jars but simply configure the plugin like you were
told to before:
<configuration>
<ajdtVersion>none</ajdtVersion>
</configuration>
http://jira.codehaus.org/browse/MECLIPSE-594
Paul
On Thu, Oct 29, 2009 at 6:56 AM, Brian Fox <br...@infinity.nu> wrote:
> Renaming it and installing it into your repo won't change anything if
> it's getting added to the classpath on the commandline, so NO don't do
> that. I believe someone already posted how to configure
> eclipse:eclipse to add the aspect support. Or you can install
> m2eclipse and use that instead.
>
> On Sun, Oct 25, 2009 at 8:42 AM, Yaakov Chaikin
> <ya...@gmail.com> wrote:
>> I spoke too soon. It does work on the command line... Given that it
>> now work on the command line, are you still suggesting that I NOT
>> renaming it and deploy it in our archiva under a different name? I
>> guess, I am not sure how I would force it into Eclipse's .classpath
>> any other way.
>>
>> Thanks,
>> Yaakov.
>>
>> On Fri, Oct 23, 2009 at 7:39 PM, Brian Fox <br...@infinity.nu> wrote:
>>> Can you send us some build logs with -X enabled? There is nothing in
>>> core that should be excluding aspectj, so something else is at play
>>> here. And loading them with a different coordinate into your repo
>>> manager is going to cause problems later, that is just patching the
>>> symptoms
>>>
>>> On Fri, Oct 23, 2009 at 4:09 PM, Yaakov Chaikin
>>> <ya...@gmail.com> wrote:
>>>> Oh, I see... However, classpath I was referring to was just regular
>>>> classpath, not .classpath of eclipse... It's excluded from the regular
>>>> Java classpath as well for some reason.
>>>>
>>>> Yaakov.
>>>>
>>>> On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk <ni...@gmail.com> wrote:
>>>>> The plugins have their own versioning. He means the 2.8 release of the
>>>>> eclipse plugin.
>>>>>
>>>>> Hth,
>>>>>
>>>>> Nick Stolwijk
>>>>> ~Java Developer~
>>>>>
>>>>> IPROFS BV.
>>>>> Claus Sluterweg 125
>>>>> 2012 WS Haarlem
>>>>> http://www.iprofs.nl
>>>>>
>>>>>
>>>>> On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>>>>>
>>>>>> > This won't happen anymore in (unreleased) 2.8. I agree with Barrie
>>>>>> > that this should be documented for users of 2.6 and 2.7. Anyone want
>>>>>> > to submit a patch for one of the help pages?
>>>>>>
>>>>>> Version 2.8 of maven? I am running maven 2.0.9 which IS released...
>>>>>> From what I see on the maven's page, the latest version is 2.2.1. They
>>>>>> are working on 2.8 already??
>>>>>>
>>>>>> Yaakov.
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Brian Fox <br...@infinity.nu>.
Renaming it and installing it into your repo won't change anything if
it's getting added to the classpath on the commandline, so NO don't do
that. I believe someone already posted how to configure
eclipse:eclipse to add the aspect support. Or you can install
m2eclipse and use that instead.
On Sun, Oct 25, 2009 at 8:42 AM, Yaakov Chaikin
<ya...@gmail.com> wrote:
> I spoke too soon. It does work on the command line... Given that it
> now work on the command line, are you still suggesting that I NOT
> renaming it and deploy it in our archiva under a different name? I
> guess, I am not sure how I would force it into Eclipse's .classpath
> any other way.
>
> Thanks,
> Yaakov.
>
> On Fri, Oct 23, 2009 at 7:39 PM, Brian Fox <br...@infinity.nu> wrote:
>> Can you send us some build logs with -X enabled? There is nothing in
>> core that should be excluding aspectj, so something else is at play
>> here. And loading them with a different coordinate into your repo
>> manager is going to cause problems later, that is just patching the
>> symptoms
>>
>> On Fri, Oct 23, 2009 at 4:09 PM, Yaakov Chaikin
>> <ya...@gmail.com> wrote:
>>> Oh, I see... However, classpath I was referring to was just regular
>>> classpath, not .classpath of eclipse... It's excluded from the regular
>>> Java classpath as well for some reason.
>>>
>>> Yaakov.
>>>
>>> On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk <ni...@gmail.com> wrote:
>>>> The plugins have their own versioning. He means the 2.8 release of the
>>>> eclipse plugin.
>>>>
>>>> Hth,
>>>>
>>>> Nick Stolwijk
>>>> ~Java Developer~
>>>>
>>>> IPROFS BV.
>>>> Claus Sluterweg 125
>>>> 2012 WS Haarlem
>>>> http://www.iprofs.nl
>>>>
>>>>
>>>> On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>>>>
>>>>> > This won't happen anymore in (unreleased) 2.8. I agree with Barrie
>>>>> > that this should be documented for users of 2.6 and 2.7. Anyone want
>>>>> > to submit a patch for one of the help pages?
>>>>>
>>>>> Version 2.8 of maven? I am running maven 2.0.9 which IS released...
>>>>> From what I see on the maven's page, the latest version is 2.2.1. They
>>>>> are working on 2.8 already??
>>>>>
>>>>> Yaakov.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Yaakov Chaikin <ya...@gmail.com>.
I spoke too soon. It does work on the command line... Given that it
now work on the command line, are you still suggesting that I NOT
renaming it and deploy it in our archiva under a different name? I
guess, I am not sure how I would force it into Eclipse's .classpath
any other way.
Thanks,
Yaakov.
On Fri, Oct 23, 2009 at 7:39 PM, Brian Fox <br...@infinity.nu> wrote:
> Can you send us some build logs with -X enabled? There is nothing in
> core that should be excluding aspectj, so something else is at play
> here. And loading them with a different coordinate into your repo
> manager is going to cause problems later, that is just patching the
> symptoms
>
> On Fri, Oct 23, 2009 at 4:09 PM, Yaakov Chaikin
> <ya...@gmail.com> wrote:
>> Oh, I see... However, classpath I was referring to was just regular
>> classpath, not .classpath of eclipse... It's excluded from the regular
>> Java classpath as well for some reason.
>>
>> Yaakov.
>>
>> On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk <ni...@gmail.com> wrote:
>>> The plugins have their own versioning. He means the 2.8 release of the
>>> eclipse plugin.
>>>
>>> Hth,
>>>
>>> Nick Stolwijk
>>> ~Java Developer~
>>>
>>> IPROFS BV.
>>> Claus Sluterweg 125
>>> 2012 WS Haarlem
>>> http://www.iprofs.nl
>>>
>>>
>>> On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>>>
>>>> > This won't happen anymore in (unreleased) 2.8. I agree with Barrie
>>>> > that this should be documented for users of 2.6 and 2.7. Anyone want
>>>> > to submit a patch for one of the help pages?
>>>>
>>>> Version 2.8 of maven? I am running maven 2.0.9 which IS released...
>>>> From what I see on the maven's page, the latest version is 2.2.1. They
>>>> are working on 2.8 already??
>>>>
>>>> Yaakov.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Brian Fox <br...@infinity.nu>.
Can you send us some build logs with -X enabled? There is nothing in
core that should be excluding aspectj, so something else is at play
here. And loading them with a different coordinate into your repo
manager is going to cause problems later, that is just patching the
symptoms
On Fri, Oct 23, 2009 at 4:09 PM, Yaakov Chaikin
<ya...@gmail.com> wrote:
> Oh, I see... However, classpath I was referring to was just regular
> classpath, not .classpath of eclipse... It's excluded from the regular
> Java classpath as well for some reason.
>
> Yaakov.
>
> On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk <ni...@gmail.com> wrote:
>> The plugins have their own versioning. He means the 2.8 release of the
>> eclipse plugin.
>>
>> Hth,
>>
>> Nick Stolwijk
>> ~Java Developer~
>>
>> IPROFS BV.
>> Claus Sluterweg 125
>> 2012 WS Haarlem
>> http://www.iprofs.nl
>>
>>
>> On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>>
>>> > This won't happen anymore in (unreleased) 2.8. I agree with Barrie
>>> > that this should be documented for users of 2.6 and 2.7. Anyone want
>>> > to submit a patch for one of the help pages?
>>>
>>> Version 2.8 of maven? I am running maven 2.0.9 which IS released...
>>> From what I see on the maven's page, the latest version is 2.2.1. They
>>> are working on 2.8 already??
>>>
>>> Yaakov.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Multi-module project dependencies not resolving
Posted by Michael Remijan <mj...@yahoo.com>.
I have a multi-module project, only two modules, where Module-A creates a jar during phase=package goal=jar using classifier=stubs. Module-B has it's only dependency set to this stubs jar which Module-A creates. When I run the top-level pom as 'maven package', all of Module-A gets created fine but then fails at Module-B because the dependency on the stubs jar from Module-A cannot be found. Is this the way it's suppose to work? I don't think a multi-module project build should fail because of dependencies between the modules. What can I be doing wrong? Is this a quark of the Eclipse m2 plugin?
Re: Aspectj jars refuse to get imported
Posted by Yaakov Chaikin <ya...@gmail.com>.
Oh, I see... However, classpath I was referring to was just regular
classpath, not .classpath of eclipse... It's excluded from the regular
Java classpath as well for some reason.
Yaakov.
On Fri, Oct 23, 2009 at 3:57 PM, Nick Stolwijk <ni...@gmail.com> wrote:
> The plugins have their own versioning. He means the 2.8 release of the
> eclipse plugin.
>
> Hth,
>
> Nick Stolwijk
> ~Java Developer~
>
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
>
>
> On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>
>> > This won't happen anymore in (unreleased) 2.8. I agree with Barrie
>> > that this should be documented for users of 2.6 and 2.7. Anyone want
>> > to submit a patch for one of the help pages?
>>
>> Version 2.8 of maven? I am running maven 2.0.9 which IS released...
>> From what I see on the maven's page, the latest version is 2.2.1. They
>> are working on 2.8 already??
>>
>> Yaakov.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Nick Stolwijk <ni...@gmail.com>.
The plugins have their own versioning. He means the 2.8 release of the
eclipse plugin.
Hth,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl
On Fri, Oct 23, 2009 at 7:42 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
> > This won't happen anymore in (unreleased) 2.8. I agree with Barrie
> > that this should be documented for users of 2.6 and 2.7. Anyone want
> > to submit a patch for one of the help pages?
>
> Version 2.8 of maven? I am running maven 2.0.9 which IS released...
> From what I see on the maven's page, the latest version is 2.2.1. They
> are working on 2.8 already??
>
> Yaakov.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Aspectj jars refuse to get imported
Posted by Yaakov Chaikin <ya...@gmail.com>.
> This won't happen anymore in (unreleased) 2.8. I agree with Barrie
> that this should be documented for users of 2.6 and 2.7. Anyone want
> to submit a patch for one of the help pages?
Version 2.8 of maven? I am running maven 2.0.9 which IS released...
>From what I see on the maven's page, the latest version is 2.2.1. They
are working on 2.8 already??
Yaakov.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Paul Benedict <pb...@apache.org>.
Yaakov,
This won't happen anymore in (unreleased) 2.8. I agree with Barrie
that this should be documented for users of 2.6 and 2.7. Anyone want
to submit a patch for one of the help pages?
Paul
On Fri, Oct 23, 2009 at 11:28 AM, Yaakov Chaikin
<ya...@gmail.com> wrote:
> 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 <ba...@gmail.com> wrote:
>> On Fri, Oct 23, 2009 at 11:53 AM, Paul Benedict <pb...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Yaakov Chaikin <ya...@gmail.com>.
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 <ba...@gmail.com> wrote:
> On Fri, Oct 23, 2009 at 11:53 AM, Paul Benedict <pb...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Barrie Treloar <ba...@gmail.com>.
On Fri, Oct 23, 2009 at 11:53 AM, Paul Benedict <pb...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Aspectj jars refuse to get imported
Posted by Paul Benedict <pb...@apache.org>.
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>.
Paul
On Thu, Oct 22, 2009 at 7:01 PM, Martin Gainty <mg...@hotmail.com> wrote:
>
> did you put these dependencies on the test project pom.xml?
> assuming you have maven-eclipse
> try exporting the test project pom.xml and placing these dependencies into the pom.xml manually
> then the project should see the plugins referenced from local repository
>
> Martin Gainty
> ______________________________________________
>
>> Date: Fri, 23 Oct 2009 08:37:41 +1030
>> Subject: Re: Aspectj jars refuse to get imported
>> From: baerrach@gmail.com
>> To: users@maven.apache.org
>>
>> On Fri, Oct 23, 2009 at 5:37 AM, Yaakov Chaikin
>> <ya...@gmail.com> wrote:
>> > Hi,
>> >
>> > Perhaps, someone can point out to me what I am doing wrong...
>> >
>> > I have the following simple pom.xml file:
>> > **************
>> > <?xml version="1.0" encoding="UTF-8"?>
>> > <project xmlns="http://maven.apache.org/POM/4.0.0"
>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>> > http://maven.apache.org/maven-v4_0_0.xsd">
>> > <modelVersion>4.0.0</modelVersion>
>> >
>> > <groupId>pull</groupId>
>> > <artifactId>spring-aop-example</artifactId>
>> > <packaging>jar</packaging>
>> > <version>1.0-SNAPSHOT</version>
>> > <name>Maven pull of dependencies project</name>
>> >
>> > <dependencies>
>> > <dependency>
>> > <groupId>org.aspectj</groupId>
>> > <artifactId>aspectjrt</artifactId>
>> > <version>1.6.0</version>
>> > </dependency>
>> > <dependency>
>> > <groupId>org.aspectj</groupId>
>> > <artifactId>aspectjweaver</artifactId>
>> > <version>1.6.0</version>
>> > </dependency>
>> > </dependencies>
>> > </project>
>> > **************
>> >
>> > When I run 'mvn clean install', the proper JARs get pulled into my
>> > local repository. However, when I need these on my classpath, they are
>> > not there!
>> >
>> > On top of that, running regular 'mvn eclipse:eclipse' DOES NOT import
>> > them into eclipse like any other regular dependency! It's as if they
>> > are not mentioned in the pom at all!
>>
>> For eclipse, did you check the docs?
>> http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html
>>
>> For why they are not on your regular classpath, no idea. I dont work
>> with aspectj.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Aspectj jars refuse to get imported
Posted by Martin Gainty <mg...@hotmail.com>.
did you put these dependencies on the test project pom.xml?
assuming you have maven-eclipse
try exporting the test project pom.xml and placing these dependencies into the pom.xml manually
then the project should see the plugins referenced from local repository
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Fri, 23 Oct 2009 08:37:41 +1030
> Subject: Re: Aspectj jars refuse to get imported
> From: baerrach@gmail.com
> To: users@maven.apache.org
>
> On Fri, Oct 23, 2009 at 5:37 AM, Yaakov Chaikin
> <ya...@gmail.com> wrote:
> > Hi,
> >
> > Perhaps, someone can point out to me what I am doing wrong...
> >
> > I have the following simple pom.xml file:
> > **************
> > <?xml version="1.0" encoding="UTF-8"?>
> > <project xmlns="http://maven.apache.org/POM/4.0.0"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > http://maven.apache.org/maven-v4_0_0.xsd">
> > <modelVersion>4.0.0</modelVersion>
> >
> > <groupId>pull</groupId>
> > <artifactId>spring-aop-example</artifactId>
> > <packaging>jar</packaging>
> > <version>1.0-SNAPSHOT</version>
> > <name>Maven pull of dependencies project</name>
> >
> > <dependencies>
> > <dependency>
> > <groupId>org.aspectj</groupId>
> > <artifactId>aspectjrt</artifactId>
> > <version>1.6.0</version>
> > </dependency>
> > <dependency>
> > <groupId>org.aspectj</groupId>
> > <artifactId>aspectjweaver</artifactId>
> > <version>1.6.0</version>
> > </dependency>
> > </dependencies>
> > </project>
> > **************
> >
> > When I run 'mvn clean install', the proper JARs get pulled into my
> > local repository. However, when I need these on my classpath, they are
> > not there!
> >
> > On top of that, running regular 'mvn eclipse:eclipse' DOES NOT import
> > them into eclipse like any other regular dependency! It's as if they
> > are not mentioned in the pom at all!
>
> For eclipse, did you check the docs?
> http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html
>
> For why they are not on your regular classpath, no idea. I dont work
> with aspectj.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
_________________________________________________________________
Windows 7: It works the way you want. Learn more.
http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen2:102009
Re: Aspectj jars refuse to get imported
Posted by Barrie Treloar <ba...@gmail.com>.
On Fri, Oct 23, 2009 at 5:37 AM, Yaakov Chaikin
<ya...@gmail.com> wrote:
> Hi,
>
> Perhaps, someone can point out to me what I am doing wrong...
>
> I have the following simple pom.xml file:
> **************
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
>
> <groupId>pull</groupId>
> <artifactId>spring-aop-example</artifactId>
> <packaging>jar</packaging>
> <version>1.0-SNAPSHOT</version>
> <name>Maven pull of dependencies project</name>
>
> <dependencies>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> <version>1.6.0</version>
> </dependency>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjweaver</artifactId>
> <version>1.6.0</version>
> </dependency>
> </dependencies>
> </project>
> **************
>
> When I run 'mvn clean install', the proper JARs get pulled into my
> local repository. However, when I need these on my classpath, they are
> not there!
>
> On top of that, running regular 'mvn eclipse:eclipse' DOES NOT import
> them into eclipse like any other regular dependency! It's as if they
> are not mentioned in the pom at all!
For eclipse, did you check the docs?
http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html
For why they are not on your regular classpath, no idea. I dont work
with aspectj.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org