compile-time-weaving

I have a Spring Roo multi module project . I noticed that after including the jar/module containing my domain model in another project, the aspects had not been woven leaving me with domain classes without any usable getters/setters . How can I make sure that aspects generated by Spring roo are woven by the dependent project? EDIT : In order to be able to use Roo's aspects from another project, one needs to include the aspectJ plugin in the dependent project. Note that compile time loading is not needed that way. You need to include the aspectj maven plugin in the pom: <plugin> <groupId>org

I am using compile time weaving with aspectj to weave in Spring's transactional code so I can use @Transactional . When i run maven compile from inside Eclipse (which uses the aspectj-maven-plugin), eclipse synchronizes to the tomcat server and all goes well. But when Eclipse compiles (project->build automatically) it appears not to weave the spring transactional code and I get this error: javax.persistence.TransactionRequiredException: no transaction is in progress This is very annoying because I just want to code away and not manually call maven compile after eclipse compiles every time. Do

I want to configure compile time weaving for classes marked with @Configurable annotation to be able to inject spring dependencies to classes instatiated with new operator. I don't want to use load-time weaving because I don't have access to run script of application server, so I can't modify it. Also I want to be able to use this classes in tests, I mean to run test cases from IDE . I found information only about load time weaving on the web and spring reference and nothing about configuration of compile-time weaving. PS. I use spring with maven So the other answer is also valid but I thought

I have a project which uses compile time weaving of aspects. this project depends on another project, which is a included as a jar. I want to weave a class in the jar file while compiling. How can i achieve this. Thanks This jar needs to be added to the inpath of the project being compiled. The result will be a new set of class files. These new class files are the woven ones and should be used at runtime instead of the original jar. How to set the in path is dependent on how you compile your code: Within Eclipse/AJDT, you can set the in path on the AspectJ Build project properties page. Here

Update 5: I've downloaded the latest Spring ToolsSuite IDE based on the latest Eclipse. When I import my project as a Maven project, Eclipse/STS appears to use the Maven goals for building my project. This means AspectJ finally works correctly in Eclipse. Update 4: I have ended up just using Maven + AspectJ plugin for compile-time weaving, effectively bypassing Eclipse's mechanism. Update 3: It seems AspectJ's Eclipse plug-in breaks Eclipse's ability to correctly Publish to Tomcat. Only by removing the AspectJ capability on a project can I get it to properly Publish again. Very annoying.