Perhaps you should chat with the OEPE maintainers and mention this.
On Fri, Jul 19, 2013 at 12:30 AM, Sina <my.linked.acco...@googlemail.com> wrote: > Thanks Andrew, > Comparing Indigo (OEPE) and Kepler plugins I've somehow found out that this > Configurator was missing but was not quite sure about it. > > Btw. you saved me and sorry for the messy question. While copying I messed > some parts ;) > Cheers, > Sina > > On Jul 19, 2013, at 1:12 AM, Andrew Eisenberg <and...@eisenberg.as> wrote: > >> Apologies for not answering sooner...this slipped through my inbox. >> You need to install the aspectj configurator for m2e. It should be >> available from the discovery page of the m2e preferences, or you can >> install it from the following update site: >> >> http://dist.springsource.org/release/AJDT/configurator/ >> >> On Thu, Jul 11, 2013 at 2:37 PM, Sina <my.linked.acco...@googlemail.com> >> wrote: >>> Hi everybody! >>> >>> I've just downloaded the OEPE (Kepler) and installed m2e and m2e-wtp >>> connectors. >>> This is how it looks like in my pom file >>> I found out that under this path: Preferences ->Maven->Lifecycle >>> mappings->Open workspace lifecycle mapping data there is a preconfigured xml >>> file which says that maven should ignore the compile goal for AspectJ and I >>> assume that's why the AspectJ runtime libraries are not added to the project >>> hence the project is not recognized as an AspectJ project by eclipse. >>> <?xml version="1.0" encoding="UTF-8"?> >>> <lifecycleMappingMetadata> >>> <pluginExecutions> >>> <pluginExecution> >>> <pluginExecutionFilter> >>> <groupId>org.codehaus.mojo</groupId> >>> <artifactId>aspectj-maven-plugin</artifactId> >>> <versionRange>1.6</versionRange> >>> <goals> >>> <goal>compile</goal> >>> </goals> >>> </pluginExecutionFilter> >>> <action> >>> <ignore /> >>> </action> >>> </pluginExecution> >>> </pluginExecutions> >>> </lifecycleMappingMetadata> >>> >>> I commented out these lines in the xml file and reloaded it once again. >>> Now the IDE is going does not ignore AspectJ plugin tag in the lifecycle but >>> pom file is complaining that it cannot recognize the execution tag. >>> <plugin> >>> <groupId>org.codehaus.mojo</groupId> >>> <artifactId>aspectj-maven-plugin</artifactId> >>> <version>1.4</version> >>> <dependencies> >>> <dependency> >>> <groupId>org.aspectj</groupId> >>> <artifactId>aspectjrt</artifactId> >>> <version>${aspectj.version}</version> >>> </dependency> >>> </dependencies> >>> <configuration> >>> <source>1.6</source> >>> <target>1.6</target> >>> </configuration> >>> <executions> >>> <execution> >>> <goals> >>> <goal>compile</goal> >>> </goals> >>> </execution> >>> </executions> >>> </plugin> >>> >>> Using indigo the m2e-wtp was able to recognize the <exectuion> tag for >>> aspectj plugin and able to add the AspectJ runtime libraries >>> automatically to the project, though this is not the case in Kepler. (I >>> think it is m2e-wtp's job to make an AspectJ project out of the pom but not >>> quite sure.) >>> >>> Btw. the how can I make things work like in Indigo?? >>> I know I can right click on the project and convert it to aspect project in >>> order to solve the problem but I want the IDE and plugins realize from the >>> pom file that this project needs AspectJ jars. >>> >>> Any idea? >>> Cheers. >>> >>> >>> >>> _______________________________________________ >>> aspectj-users mailing list >>> aspectj-users@eclipse.org >>> https://dev.eclipse.org/mailman/listinfo/aspectj-users >>> >> _______________________________________________ >> aspectj-users mailing list >> aspectj-users@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/aspectj-users > _______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
