AspectJ Supported in IntelliJ 7.0.x?

Hello JavaTek,

IntelliJ IDEA doesn't support aspects in standalone Java files. Only the
Spring-AOP subset of AspectJ is supported in IDEA 7.0.4, and AspectJ is only
understood inside annotations.

I started with AspectJ today and downloaded an AspectJ plugin and
integrated but when I create an aspect (.java file) with
public aspect ExceptionLoggerAspect {
}

IntelliJ puts those red squiggly lines under some lines and says
'class' or 'interface' expected. How do I tell IntelliJ to syntax
check an Aspect?

thanks

JavaTek

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

Thanks for the help. I guess the AspectJ plugins are misleading but that explains why I get a red squiggly under the following:

@Pointcut("call(* .(..)) && !within(ExceptionLoggerAspect")
public void throwableThrown() { }


=> squiggly under the <space>.*(

saying: ") expected"

---
With AspectJ seeing massive adoptions daily and supported in other IDE's, how can I help so that it is better supported in the IDE?

JavaTek wrote:

Thanks for the help. I guess the AspectJ plugins are misleading but that explains why I get a red squiggly under the following:

@Pointcut("call(* .(..)) && !within(ExceptionLoggerAspect")
public void throwableThrown() { }


=> squiggly under the <space>.*(

saying: ") expected"

---
With AspectJ seeing massive adoptions daily and supported in other IDE's, how can I help so that it is better supported in the IDE?

In the lastest IDEA8 EAP all pointcut denotations should be recognized.
But there's no navigation yet to join points.

Hi JavaTek,

It's great that you want to help support the AspectJ efforts, but if you browse the forums, you'll see that it's one of the most sought after features, and the standard reply is that IntelliJ doesn't support AspectJ. My guess is that IntelliJ will never support it, but I wish you good luck in your quest ;)

IMHO AspectJ looks like a dying hype. A few years ago it was prayed to solve
all programming problems, but it looks like the "community" realized, that
AspectJ introduced also a couple of new problems (unreadable code). Bad for
those, who followed this hype and now miss the right tool support for it.