Seems to work for the compilation, but doesn't update the dependencies in
Eclipse web module. Even if I add the dependency to the main pom.xml. That
always worked before getting stuff loaded to Eclipse.

Anyway, with regards to delivery, I would be a strong proponent of nightly
development snapshots. It would allow us to use the material when it
contains all the stuff we need to work. 

Cheers,

Marc


mraible wrote:
> 
> You need to override the aspectj-maven-plugins dependency versions to fix
> this:
> 
>             <plugin>
>                 <groupId>org.codehaus.mojo</groupId>
>                 <artifactId>aspectj-maven-plugin</artifactId>
>                 <version>1.0</version>
>                 <configuration>
>                     <source>1.5</source>
>                     <verbose>true</verbose>
>                     <complianceLevel>1.5</complianceLevel>
>                     <showWeaveInfo>true</showWeaveInfo>
>                     <aspectLibraries>
>                         <aspectLibrary>
>                             <groupId>org.springframework</groupId>
>                             <artifactId>spring-aspects</artifactId>
>                         </aspectLibrary>
>                     </aspectLibraries>
>                 </configuration>
>                 <executions>
>                     <execution>
>                         <goals>
>                             <goal>compile</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>                 <dependencies>
>                     <dependency>
>                         <groupId>org.aspectj</groupId>
>                         <artifactId>aspectjrt</artifactId>
>                         <version>1.6.0</version>
>                     </dependency>
>                     <dependency>
>                         <groupId>org.aspectj</groupId>
>                         <artifactId>aspectjtools</artifactId>
>                         <version>1.6.0</version>
>                     </dependency>
>                 </dependencies>
>             </plugin>
> 
> 2.0.2 is pretty much done - I'm just working on a "copy-templates"
> mojo (for overridding CRUD) and writing up documentation.
> Unfortunately, I have a day job and I'm staying across the street from
> JavaOne, so it's difficult to free up time to get the release out.
> 
> Matt
> 
> On Tue, May 6, 2008 at 3:54 AM, mschipperheyn <[EMAIL PROTECTED]>
> wrote:
>>
>>  Hi,
>>
>>  I've been massaging my project configuration to add support for new
>> versions
>>  of Spring etc for a while now. Now, it seems I have run into a snag
>>  upgrading to Spring 2.5.4, I get the following error trying to run mvn
>> and
>>  following that, this one from Tomcat withing Eclipse
>>
>>  [WARNING] bad version number found in C:\Documents and
>>  Settings\marc\.m2\reposit
>>  ory\org\aspectj\aspectjrt\1.6.0\aspectjrt-1.6.0.jar expected 1.5.4 found
>>  1.6.0
>>
>>
>>  org.springframework.beans.factory.BeanCreationException: Error creating
>> bean
>>  with name
>> 'org.springframework.context.config.internalBeanConfigurerAspect':
>>  Instantiation of bean failed; nested exception is
>>  org.springframework.beans.factory.BeanDefinitionStoreException: Factory
>>  method [public static
>>  org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect
>> 
>> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.aspectOf()]
>>  threw exception; nested exception is
>>  org.aspectj.lang.NoAspectBoundException: Exception while initializing
>> 
>> org_springframework_beans_factory_aspectj_AnnotationBeanConfigurerAspect:
>>  java.lang.InstantiationError:
>>  org.springframework.beans.factory.wiring.BeanConfigurerSupport
>>
>>  Caused by:
>> org.springframework.beans.factory.BeanDefinitionStoreException:
>>  Factory method [public static
>>  org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect
>> 
>> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.aspectOf()]
>>  threw exception; nested exception is
>>  org.aspectj.lang.NoAspectBoundException: Exception while initializing
>> 
>> org_springframework_beans_factory_aspectj_AnnotationBeanConfigurerAspect:
>>  java.lang.InstantiationError:
>>  org.springframework.beans.factory.wiring.BeanConfigurerSupport
>>         at
>> 
>> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:127)
>>         at
>> 
>> org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:387)
>>         ... 40 more
>>  Caused by: org.aspectj.lang.NoAspectBoundException: Exception while
>>  initializing
>> 
>> org_springframework_beans_factory_aspectj_AnnotationBeanConfigurerAspect:
>>  java.lang.InstantiationError:
>>  org.springframework.beans.factory.wiring.BeanConfigurerSupport
>>         at
>> 
>> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.aspectOf(AnnotationBeanConfigurerAspect.aj:1)
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at
>> 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>         at
>> 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>         at java.lang.reflect.Method.invoke(Method.java:597)
>>         at
>> 
>> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:115)
>>         ... 41 more
>>  Caused by: java.lang.InstantiationError:
>>  org.springframework.beans.factory.wiring.BeanConfigurerSupport
>>         at
>> 
>> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.<init>(AnnotationBeanConfigurerAspect.aj:50)
>>         at
>> 
>> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.ajc$postClinit(AnnotationBeanConfigurerAspect.aj:1)
>>         at
>> 
>> org.springframework.beans.factory.aspectj.AnnotationBeanConfigurerAspect.<clinit>(AnnotationBeanConfigurerAspect.aj:46)
>>         ... 46 more
>>
>>  Anyway, since I made AspectJ 1.6.0 a dependency in my pom, I suspect
>> that
>>  this time round, I've run into a dependency within the Appfuse
>> framework. Is
>>  there a way around it? If not, when is Appfuse 2.02 coming out!!
>>
>>  Thanks,
>>
>>  Marc
>>  --
>>  View this message in context:
>> http://www.nabble.com/AspectJ-1.6-issues%2C-when-is-appfuse-2.02-coming-out--tp17080252s2369p17080252.html
>>  Sent from the AppFuse - User mailing list archive at Nabble.com.
>>
>>
>>  ---------------------------------------------------------------------
>>  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]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/AspectJ-1.6-issues%2C-when-is-appfuse-2.02-coming-out--tp17080252s2369p17114038.html
Sent from the AppFuse - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to