[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] badWeaverState exception on iajc w/out prior clean
- From: "Andy Clement" <andrew.clement@xxxxxxxxx>
- Date: Wed, 22 Feb 2006 09:10:29 +0000
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=fniMHpUF2ouw5hr/0JNt3Rw4Bd37jer77LHnjxBjgXPFJaEZlhR5asCu9ehGx5ujWTXX2XpQAAX2IhljiokSQ3xZptIjzlhO+Pr6f0GYf3WRmD4t1f363LK4S2+QcGpdlQ1luRNvCR6UG076U0kEJNfIHUvhAwwIPk0HDxYfQf8=
On 21/02/06, Nguyen, Diane <dianen@xxxxxxxxx> wrote:
Thanks for the response!
Unfortunately, I don't think that's what is causing my bad WeaverState
exception. I'm using ajdt 1.3.0 (the latest from the eclipse AJDT site)
and AspectJ 1.5.0 from Dec 20 2005. These are the only aspectJ downloads
I've installed on my computer, and this is the only iajc compilation in
my build.xml file.
Does it matter what was used to compile the jars in my inpath? Just a
stab in the dark...
It may be important - if they contain aspects and were built using
an old build of AspectJ5 then you would see this problem.