I am using your aspectj plugin to compile my code.

Below is the code.

when i compile without aspectj it is compiling without any errors. but when i apply aspectj plugin it is giving below errors.

[ant:iajc] D:\src\main\com\\config\common\Factory.java:47 [error] The method setApplicationContext(ApplicationContext) of type Factory must override a superclass method
[ant:iajc] public void setApplicationContext(ApplicationContext arg0) throws BeansException {
[ant:iajc] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

but i can see setApplicationContext is present in spring-context jar.

Can you help me in this regard

Envirnment (every thing new)
- Windows 7 64bit
- Eclipse Indigo (3.7 SR1)
- AJDT 2.1.3 (AspectJ 1.6.12) from the developer url (http://download.eclipse.org/tools/ajdt/37/dev/update)
Problem also exists with the “stable release”
- Gradle 1.0-milestone-5 (Path variable extended to bin folder, no other gradle environment variable set).

Eclipse project created: “New->Project->AspectJ->AspectJ Project”
Eclipse project exported „General->File System“ and zipped, attached to e-mail

- Which eclipse ajdt version do you use?
- which gradle version do you use?

As exercise I want to play around with AspectJ (AJDT in Ecplise) and
started with Maven, but got some problems (but that is another story).
So I switched to Gradle and found this article. Downloaded Gradle and your example (aspectJ.gradle).

With this setup I have the following problem (maybe this is a understanding problem).
– The project is created as “AspectJ Project” with AJDT in eclipse.
I add classes and aspects and it works.
– I add the build.gradle + aspectJ.grade to the project and use Gradle from CLI.
– If I add some dependencies in the build.gradle (e.g. log4j),
I run “gradle eclipse” to download the jars into the repo and update eclipse.
– Back in eclipse I press a F5 for refesh.
– Now the aspect file is “red” and can’t be compiled. (from the cli: gradle test is working well!).

– I get the project back to working in eclipse with the following sequence:
– Disable “build automatically” and clean the project.
– Open the project properties and look at “Builders”
– Here the list of “Java Builder” is growing every time I call gradle eclipse and one “Java Builder” is enabled
– Disable the “Java Builder”
– Enable “build automatically”
– Project is working again from eclipse level

BTW: – gradle’s compiles with the example from this article in directory “build”.
– eclipse compiles the outputs into “bin” folder.

If somebody can help me, it will be great.
I also can export the eclipse project send send it by email, because, I haven’t seen
how to attach a file to this blog.

Uwe

I had to make a couple of mods in order to get this to work for a multi project scenario with gradle 1.0-milestone-1

1. on the ant.iajc invocation, I had to add a ‘forkclasspath’ attribute. I set this to: configurations.ajc.asPath,
2. in each child project’s dependency secion, you need to refer to any other projects it depends on for both compile AND ajc. For example, if project foo depends on project bar, then you’d list the following in foo’s dependencies section:

compile project(‘:bar’)
ajc project(‘:bar’)

3. in the overriden version of compileJava, as camechis says, you have to change which phase you’re referring to in the “dependsOn” statement (replace “compileJava” with “jar”).

dependsOn configurations.ajc.getTaskDependencyFromProjectDependency(true, “jar”)

Also for the multi-project example shown here : https://github.com/breskeby/gradleplugins/tree/0.9-upgrade/aspectjPlugin/examples/MultiProject

I would suggest changing the project names.

In the absence of declared dependencies, I believe gradle executes the child projects in alphanumeric order (based on the name of the child project). Since “ProjectA” comes before “ProjectB”, Gradle will build it first anyway (even if you leave off a dependency declaration). I think this is why its working even though its left off item #2 above.

dependsOn configurations.ajc.getTaskDependencyFromProjectDependency(true, “jar”) and now it behaves correctly. Not sure if this is the correct fix or not.

the “apply url” is outdated. you can use “apply from:http:https://github.com/breskeby/gradleplugins/raw/0.9-upgrade/aspectjPlugin/aspectJ.gradle” in gradle-1.0-milestone-1

regards,
René

On a note, I am not use the “apply :Url” this did not work. I have the tasked defined in the build file and I am using 1.0-M1 version of gradle.