| Where to begin? java.lang.NoSuchFieldError: ajc$cflowCounter$0 [message #49776] |
Thu, 10 March 2005 12:24  |
Eclipse User |
|
|
|
Originally posted by: sdelap.metamatrix.com
I'm attempting to convert our Eclipse plugin based application to Eclipse
3.x. I'm using Eclipse 3.1 M5 as my IDE with the latest version of AJDT
installed. When I run our application I get:
java.lang.NoSuchFieldError: ajc$cflowCounter$0
at org.eclipse.uml2.impl.PackageImpl.eSet(PackageImpl.java:1)
PackageImpl.java:1 is only a comment of course which is no help. It
appears that other AspectJ related code in our application is working
fine. Where should I start to determine what is causing this problem?
I've searched around on Google and the Eclipse site but didnt' really find
anything.
|
|
|
|
|
| Re: Where to begin? java.lang.NoSuchFieldError: ajc$cflowCounter$0 [message #49894 is a reply to message #49864] |
Fri, 11 March 2005 04:45  |
| Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
hmmm... so everything affected by aspects is self contained in your
eclipse project? There are no external dependencies on code that
has been woven?
From your original message it looks like this class must be rebuilt:
>>> at org.eclipse.uml2.impl.PackageImpl.eSet(PackageImpl.java:1)
Is that in the project?
If you run javap against that class - do you see any ajc$cflowCounter
fields? Do you see any ajc$cflowStack fields?
cheers,
Andy.
Scott Delap wrote:
> Andy,
>
> I've cleaned/rebuilt everything several times in our project already.
> We have the aspectj project in our workspace so I also made sure and
> imported the new version. Anything I need to manually clean out?
>
> Scott
>
> Andy Clement wrote:
>
>> Hi Scott,
>
>
>> Changes in AspectJ between pre-eclipse 3.0 based code and 3.1 based
>> code are likely to be the problem - can you rebuild all the AspectJ
>> code with the same compiler? We put in some performance improvements
>> for cflow and you appear to have one 'end' of your cflow being built
>> to include the optimization but the other end still using the old
>> style. You ought to see some performance benefit if you can do
>> this rebuild (depending on how often you use cflow...)
>
>
>> Moving forward we are working on our binary compatibility so we get
>> into this kind of situation less and less.
>
>
>> (I can supply more gory details on request...)
>
>
>> cheers,
>> Andy.
>
>
>> Scott Delap wrote:
>>
>>> I'm attempting to convert our Eclipse plugin based application to
>>> Eclipse 3.x. I'm using Eclipse 3.1 M5 as my IDE with the latest
>>> version of AJDT installed. When I run our application I get:
>>>
>>> java.lang.NoSuchFieldError: ajc$cflowCounter$0
>>> at org.eclipse.uml2.impl.PackageImpl.eSet(PackageImpl.java:1)
>>>
>>> PackageImpl.java:1 is only a comment of course which is no help. It
>>> appears that other AspectJ related code in our application is working
>>> fine. Where should I start to determine what is causing this
>>> problem? I've searched around on Google and the Eclipse site but
>>> didnt' really find anything.
>
>
>
|
|
|
| Re: Where to begin? java.lang.NoSuchFieldError: ajc$cflowCounter$0 [message #587411 is a reply to message #49776] |
Thu, 10 March 2005 12:38 |
| Eclipse User |
|
|
|
Hi Scott,
Changes in AspectJ between pre-eclipse 3.0 based code and 3.1 based
code are likely to be the problem - can you rebuild all the AspectJ
code with the same compiler? We put in some performance improvements
for cflow and you appear to have one 'end' of your cflow being built
to include the optimization but the other end still using the old
style. You ought to see some performance benefit if you can do
this rebuild (depending on how often you use cflow...)
Moving forward we are working on our binary compatibility so we get
into this kind of situation less and less.
(I can supply more gory details on request...)
cheers,
Andy.
Scott Delap wrote:
> I'm attempting to convert our Eclipse plugin based application to
> Eclipse 3.x. I'm using Eclipse 3.1 M5 as my IDE with the latest version
> of AJDT installed. When I run our application I get:
>
> java.lang.NoSuchFieldError: ajc$cflowCounter$0
> at org.eclipse.uml2.impl.PackageImpl.eSet(PackageImpl.java:1)
>
> PackageImpl.java:1 is only a comment of course which is no help. It
> appears that other AspectJ related code in our application is working
> fine. Where should I start to determine what is causing this problem?
> I've searched around on Google and the Eclipse site but didnt' really
> find anything.
|
|
|
| Re: Where to begin? java.lang.NoSuchFieldError: ajc$cflowCounter$0 [message #587429 is a reply to message #49834] |
Thu, 10 March 2005 12:53 |
| Eclipse User |
|
|
|
Andy,
I've cleaned/rebuilt everything several times in our project already. We
have the aspectj project in our workspace so I also made sure and imported
the new version. Anything I need to manually clean out?
Scott
Andy Clement wrote:
> Hi Scott,
> Changes in AspectJ between pre-eclipse 3.0 based code and 3.1 based
> code are likely to be the problem - can you rebuild all the AspectJ
> code with the same compiler? We put in some performance improvements
> for cflow and you appear to have one 'end' of your cflow being built
> to include the optimization but the other end still using the old
> style. You ought to see some performance benefit if you can do
> this rebuild (depending on how often you use cflow...)
> Moving forward we are working on our binary compatibility so we get
> into this kind of situation less and less.
> (I can supply more gory details on request...)
> cheers,
> Andy.
> Scott Delap wrote:
>> I'm attempting to convert our Eclipse plugin based application to
>> Eclipse 3.x. I'm using Eclipse 3.1 M5 as my IDE with the latest version
>> of AJDT installed. When I run our application I get:
>>
>> java.lang.NoSuchFieldError: ajc$cflowCounter$0
>> at org.eclipse.uml2.impl.PackageImpl.eSet(PackageImpl.java:1)
>>
>> PackageImpl.java:1 is only a comment of course which is no help. It
>> appears that other AspectJ related code in our application is working
>> fine. Where should I start to determine what is causing this problem?
>> I've searched around on Google and the Eclipse site but didnt' really
>> find anything.
|
|
|
| Re: Where to begin? java.lang.NoSuchFieldError: ajc$cflowCounter$0 [message #587443 is a reply to message #49864] |
Fri, 11 March 2005 04:45 |
| Eclipse User |
|
|
|
hmmm... so everything affected by aspects is self contained in your
eclipse project? There are no external dependencies on code that
has been woven?
From your original message it looks like this class must be rebuilt:
>>> at org.eclipse.uml2.impl.PackageImpl.eSet(PackageImpl.java:1)
Is that in the project?
If you run javap against that class - do you see any ajc$cflowCounter
fields? Do you see any ajc$cflowStack fields?
cheers,
Andy.
Scott Delap wrote:
> Andy,
>
> I've cleaned/rebuilt everything several times in our project already.
> We have the aspectj project in our workspace so I also made sure and
> imported the new version. Anything I need to manually clean out?
>
> Scott
>
> Andy Clement wrote:
>
>> Hi Scott,
>
>
>> Changes in AspectJ between pre-eclipse 3.0 based code and 3.1 based
>> code are likely to be the problem - can you rebuild all the AspectJ
>> code with the same compiler? We put in some performance improvements
>> for cflow and you appear to have one 'end' of your cflow being built
>> to include the optimization but the other end still using the old
>> style. You ought to see some performance benefit if you can do
>> this rebuild (depending on how often you use cflow...)
>
>
>> Moving forward we are working on our binary compatibility so we get
>> into this kind of situation less and less.
>
>
>> (I can supply more gory details on request...)
>
>
>> cheers,
>> Andy.
>
>
>> Scott Delap wrote:
>>
>>> I'm attempting to convert our Eclipse plugin based application to
>>> Eclipse 3.x. I'm using Eclipse 3.1 M5 as my IDE with the latest
>>> version of AJDT installed. When I run our application I get:
>>>
>>> java.lang.NoSuchFieldError: ajc$cflowCounter$0
>>> at org.eclipse.uml2.impl.PackageImpl.eSet(PackageImpl.java:1)
>>>
>>> PackageImpl.java:1 is only a comment of course which is no help. It
>>> appears that other AspectJ related code in our application is working
>>> fine. Where should I start to determine what is causing this
>>> problem? I've searched around on Google and the Eclipse site but
>>> didnt' really find anything.
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04226 seconds
Home