IDEA 10.5.2 Aspectj compiler - can't determine superclass of missing type org.springframework.transaction.interceptor.TransactionAspectSupport

Trying to make a module with spring aspects gives me:

can't determine superclass of missing type org.springframework.transaction.interceptor.TransactionAspectSupport

Works in other modules, what's up with this one? Missing dep?

/S

8 comments
Comment actions Permalink

AbstractTransactionAspect from spring-aspects references TransactionAspectSupport from spring-tx - do you have it in deps?

0
Comment actions Permalink

Yes, i just reinstalled the aspectj support plugin. Now it works! Magic!

0
Comment actions Permalink

Hmm, the problem came back. Work around: build with maven; switch to javac and build, switch back to ajc. Still I like to see a solution to this

0
Comment actions Permalink

So, in a module you're trying to compile, do you have a dependencies to both spring-aspects and spring-tx libs?

0
Comment actions Permalink

Missing in one dependent submodule (it inself has not such dep. though)

/S

0
Comment actions Permalink

Well, just try this: find all modules that depends on spring-aspects, and add dependency on spring-tx too. I think this should help.

0
Comment actions Permalink

Seems too :-) I have a few utilty modules with just spring-core dep, lot's of aspectjrt.jar not on classpath but it builds! No aspects though in those.

Adding this to a utility module with just a previous dep to spring-core prevents the warnings during build.

        <dependency>
            <groupId>org.aspectj</groupId>
            <artifactId>aspectjrt</artifactId>
            <scope>compile</scope>
        </dependency>

        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-aspects</artifactId>
            <scope>compile</scope>
        </dependency>

        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-tx</artifactId>
            <scope>compile</scope>
        </dependency>

        <dependency>
            <groupId>org.hibernate.javax.persistence</groupId>
            <artifactId>hibernate-jpa-2.0-api</artifactId>
            <scope>compile</scope>
        </dependency>

0
Comment actions Permalink

I do believe the problem was not in having aspects in a module, but in having such a classes to which aspects from spring-aspect may want to apply.

0

Please sign in to leave a comment.