Home » Language IDEs » AspectJ » Latest build still not creating any class files
| Latest build still not creating any class files [message #22847] |
Mon, 02 June 2003 18:51  |
Eclipse User |
|
|
|
Originally posted by: chad_woolley.choicehotels.com
Hello,
I am still having the problem of the latest build not creating any class
files. This was mentioned in a previous thread, but since this was not
mentioned in the "known AJDT bugs" just posted, I thought I would bring it
up again.
I am using AJDT dev build 1.1.3, installed via Eclipse Install/Update, on
eclipse 2.1.0.
Here is a detailed analysis of when the bug occurs and how to recreate it:
===========================================
Scenario 0 ("Control Group" - no aspectj):
- Removed aspectj nature
- Deleted default output folder
- Select Project -> Rebuild All
- default output folder and classes are all successfully created
- everything works fine (but is compiled without aspects)
---------------------------------------
Scenarios 1-4 common setup preparation:
- no other projects open in workspace
- suppress automatic builds SELECTED in global aspectj preference
- use AspectJ aware version of outline view DESELECTED in global aspectj
preference
- all input fields on AspectJ Compiler project settings empty (except
incremental checkbox)
- enabled aspectj nature
- delete default.lst file
Scenario 1:
- delete default output folder through eclipse resource perspective
- incremental compile DESELECTED
- Select Project -> Rebuild All
- default.lst is created
- NO default output folder or classes are created
Scenario 2:
- delete default output folder through eclipse resource perspective
- incremental compile SELECTED
- Select Project -> Rebuild All
- default.lst is created
- NO default output folder or classes are created
Scenario 3:
- delete default output folder through eclipse resource perspective
- manually create default output folder through eclipse resource
perspective
- incremental compile DESELECTED
- Select Project -> Rebuild All
- default.lst is created
- NO classes are created
Scenario 4:
- delete default output folder through eclipse resource perspective
- manually create default output folder through eclipse resource
perspective
- incremental compile SELECTED
- Select Project -> Rebuild All
- default.lst is created
- NO classes are created
|
|
|
| Re: Latest build still not creating any class files [message #22890 is a reply to message #22847] |
Tue, 03 June 2003 03:11  |
| Eclipse User |
|
|
|
Originally posted by: chad_woolley.choicehotels.com
Additional info based on comment in previous thread:
There is no aspectjrt.jar in my project. The only jar in my lib folder is
junit.jar, and this is the only jar (other than the JRE) on my classpath
in the project properties.
Chad Woolley wrote:
> Hello,
> I am still having the problem of the latest build not creating any class
> files. This was mentioned in a previous thread, but since this was not
> mentioned in the "known AJDT bugs" just posted, I thought I would bring it
> up again.
> I am using AJDT dev build 1.1.3, installed via Eclipse Install/Update, on
> eclipse 2.1.0.
> Here is a detailed analysis of when the bug occurs and how to recreate it:
> ===========================================
> Scenario 0 ("Control Group" - no aspectj):
> - Removed aspectj nature
> - Deleted default output folder
> - Select Project -> Rebuild All
> - default output folder and classes are all successfully created
> - everything works fine (but is compiled without aspects)
> ---------------------------------------
> Scenarios 1-4 common setup preparation:
> - no other projects open in workspace
> - suppress automatic builds SELECTED in global aspectj preference
> - use AspectJ aware version of outline view DESELECTED in global aspectj
> preference
> - all input fields on AspectJ Compiler project settings empty (except
> incremental checkbox)
> - enabled aspectj nature
> - delete default.lst file
> Scenario 1:
> - delete default output folder through eclipse resource perspective
> - incremental compile DESELECTED
> - Select Project -> Rebuild All
> - default.lst is created
> - NO default output folder or classes are created
> Scenario 2:
> - delete default output folder through eclipse resource perspective
> - incremental compile SELECTED
> - Select Project -> Rebuild All
> - default.lst is created
> - NO default output folder or classes are created
> Scenario 3:
> - delete default output folder through eclipse resource perspective
> - manually create default output folder through eclipse resource
> perspective
> - incremental compile DESELECTED
> - Select Project -> Rebuild All
> - default.lst is created
> - NO classes are created
> Scenario 4:
> - delete default output folder through eclipse resource perspective
> - manually create default output folder through eclipse resource
> perspective
> - incremental compile SELECTED
> - Select Project -> Rebuild All
> - default.lst is created
> - NO classes are created
|
|
|
| Re: Latest build still not creating any class files [message #22978 is a reply to message #22890] |
Wed, 04 June 2003 19:07 |
 George Harley
Messages: 70
Registered: July 2009 |
Member |
|
|
Hi Chad,
Are you saying that when you remove the aspectj nature and then re-enable
it you are not seeing aspectjrt.jar in your project dependencies ?
Best regards,
George
On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
<chad_woolley@choicehotels.com> wrote:
> Additional info based on comment in previous thread:
>
> There is no aspectjrt.jar in my project. The only jar in my lib folder
> is
> junit.jar, and this is the only jar (other than the JRE) on my classpath
> in the project properties.
>
> Chad Woolley wrote:
>
>> Hello,
>
>> I am still having the problem of the latest build not creating any class
>> files. This was mentioned in a previous thread, but since this was not
>> mentioned in the "known AJDT bugs" just posted, I thought I would bring
>> it
>> up again.
>
>> I am using AJDT dev build 1.1.3, installed via Eclipse Install/Update,
>> on
>> eclipse 2.1.0.
>
>> Here is a detailed analysis of when the bug occurs and how to recreate
>> it:
>
>
>> ===========================================
>
>
>> Scenario 0 ("Control Group" - no aspectj):
>> - Removed aspectj nature
>> - Deleted default output folder
>> - Select Project -> Rebuild All
>> - default output folder and classes are all successfully created
>> - everything works fine (but is compiled without aspects)
>
>> ---------------------------------------
>
>> Scenarios 1-4 common setup preparation: - no other projects open in
>> workspace
>> - suppress automatic builds SELECTED in global aspectj preference
>> - use AspectJ aware version of outline view DESELECTED in global aspectj
>> preference
>> - all input fields on AspectJ Compiler project settings empty (except
>> incremental checkbox)
>> - enabled aspectj nature
>> - delete default.lst file
>
>> Scenario 1:
>> - delete default output folder through eclipse resource perspective
>> - incremental compile DESELECTED
>> - Select Project -> Rebuild All
>> - default.lst is created
>> - NO default output folder or classes are created
>
>> Scenario 2:
>> - delete default output folder through eclipse resource perspective
>> - incremental compile SELECTED
>> - Select Project -> Rebuild All
>> - default.lst is created
>> - NO default output folder or classes are created
>
>> Scenario 3:
>> - delete default output folder through eclipse resource perspective
>> - manually create default output folder through eclipse resource
>> perspective
>> - incremental compile DESELECTED
>> - Select Project -> Rebuild All
>> - default.lst is created
>> - NO classes are created
>
>> Scenario 4:
>> - delete default output folder through eclipse resource perspective
>> - manually create default output folder through eclipse resource
>> perspective
>> - incremental compile SELECTED
>> - Select Project -> Rebuild All
>> - default.lst is created
>> - NO classes are created
>
>
>
>
>
>
>
>
--
George
|
|
|
| Re: Latest build still not creating any class files [message #23107 is a reply to message #22978] |
Thu, 05 June 2003 00:52 |
| Eclipse User |
|
|
|
Originally posted by: chad_woolley.choicehotels.com
George,
No, when I re-enable the aspectj nature, the aspectjrt.jar is added back
to the classpath just fine. The problem is that no class files are ever
generated when the aspectj nature is enabled.
Thanks for your response,
Chad
George Harley wrote:
> Hi Chad,
> Are you saying that when you remove the aspectj nature and then re-enable
> it you are not seeing aspectjrt.jar in your project dependencies ?
> Best regards,
> George
> On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> <chad_woolley@choicehotels.com> wrote:
> > Additional info based on comment in previous thread:
> >
> > There is no aspectjrt.jar in my project. The only jar in my lib folder
> > is
> > junit.jar, and this is the only jar (other than the JRE) on my classpath
> > in the project properties.
> >
> > Chad Woolley wrote:
> >
> >> Hello,
> >
> >> I am still having the problem of the latest build not creating any class
> >> files. This was mentioned in a previous thread, but since this was not
> >> mentioned in the "known AJDT bugs" just posted, I thought I would bring
> >> it
> >> up again.
> >
> >> I am using AJDT dev build 1.1.3, installed via Eclipse Install/Update,
> >> on
> >> eclipse 2.1.0.
> >
> >> Here is a detailed analysis of when the bug occurs and how to recreate
> >> it:
> >
> >
> >> ===========================================
> >
> >
> >> Scenario 0 ("Control Group" - no aspectj):
> >> - Removed aspectj nature
> >> - Deleted default output folder
> >> - Select Project -> Rebuild All
> >> - default output folder and classes are all successfully created
> >> - everything works fine (but is compiled without aspects)
> >
> >> ---------------------------------------
> >
> >> Scenarios 1-4 common setup preparation: - no other projects open in
> >> workspace
> >> - suppress automatic builds SELECTED in global aspectj preference
> >> - use AspectJ aware version of outline view DESELECTED in global aspectj
> >> preference
> >> - all input fields on AspectJ Compiler project settings empty (except
> >> incremental checkbox)
> >> - enabled aspectj nature
> >> - delete default.lst file
> >
> >> Scenario 1:
> >> - delete default output folder through eclipse resource perspective
> >> - incremental compile DESELECTED
> >> - Select Project -> Rebuild All
> >> - default.lst is created
> >> - NO default output folder or classes are created
> >
> >> Scenario 2:
> >> - delete default output folder through eclipse resource perspective
> >> - incremental compile SELECTED
> >> - Select Project -> Rebuild All
> >> - default.lst is created
> >> - NO default output folder or classes are created
> >
> >> Scenario 3:
> >> - delete default output folder through eclipse resource perspective
> >> - manually create default output folder through eclipse resource
> >> perspective
> >> - incremental compile DESELECTED
> >> - Select Project -> Rebuild All
> >> - default.lst is created
> >> - NO classes are created
> >
> >> Scenario 4:
> >> - delete default output folder through eclipse resource perspective
> >> - manually create default output folder through eclipse resource
> >> perspective
> >> - incremental compile SELECTED
> >> - Select Project -> Rebuild All
> >> - default.lst is created
> >> - NO classes are created
> >
> >
> >
> >
> >
> >
> >
> >
> --
> George
|
|
|
| Re: Latest build still not creating any class files [message #23399 is a reply to message #23107] |
Fri, 06 June 2003 18:45 |
Julie Waterhouse
Messages: 42
Registered: July 2009 |
Member |
|
|
Chad, I've been trying to recreate your problem, but cannot. I tried all
your scenarios, but they produced class files just fine for me.
After seeing Andy's reply to your post about this in another thread, I
also tried the following:
Using eclipse with ajdt plugin level 1.1.1
-create simple aspectJ project (one class, one aspect)
-build
-delete output folder & default.lst
-rebuild
->produces class files correctly
Then upgrade to plugin 1.1.2 via update site
-restart
-turn on incremental compile (I get the same results with or without this
step)
-delete output folder & default.lst
-rebuild
-get error (as Andy predicted): AspectJ Runtime error: bad version number
found in
D:\eclipse2.1\eclipse\plugins\org.aspectj.ajde_1.1.1\aspectj rt.jar
expected 1.1rc2 found 1.1rc1. Please place a valid aspectjrt.jar on the
classpath.
-replaced aspectjrt.jar on the Java build path with correct 1.1.2 version
-"OK" triggered empty Output folder to be created
-rebuild all
->produces class files correctly
Chad Woolley wrote:
> George,
> No, when I re-enable the aspectj nature, the aspectjrt.jar is added back
> to the classpath just fine. The problem is that no class files are ever
> generated when the aspectj nature is enabled.
> Thanks for your response,
> Chad
> George Harley wrote:
> > Hi Chad,
> > Are you saying that when you remove the aspectj nature and then re-enable
> > it you are not seeing aspectjrt.jar in your project dependencies ?
> > Best regards,
> > George
> > On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> > <chad_woolley@choicehotels.com> wrote:
> > > Additional info based on comment in previous thread:
> > >
> > > There is no aspectjrt.jar in my project. The only jar in my lib folder
> > > is
> > > junit.jar, and this is the only jar (other than the JRE) on my classpath
> > > in the project properties.
> > >
> > > Chad Woolley wrote:
> > >
> > >> Hello,
> > >
> > >> I am still having the problem of the latest build not creating any class
> > >> files. This was mentioned in a previous thread, but since this was not
> > >> mentioned in the "known AJDT bugs" just posted, I thought I would bring
> > >> it
> > >> up again.
> > >
> > >> I am using AJDT dev build 1.1.3, installed via Eclipse Install/Update,
> > >> on
> > >> eclipse 2.1.0.
> > >
> > >> Here is a detailed analysis of when the bug occurs and how to recreate
> > >> it:
> > >
> > >
> > >> ===========================================
> > >
> > >
> > >> Scenario 0 ("Control Group" - no aspectj):
> > >> - Removed aspectj nature
> > >> - Deleted default output folder
> > >> - Select Project -> Rebuild All
> > >> - default output folder and classes are all successfully created
> > >> - everything works fine (but is compiled without aspects)
> > >
> > >> ---------------------------------------
> > >
> > >> Scenarios 1-4 common setup preparation: - no other projects open in
> > >> workspace
> > >> - suppress automatic builds SELECTED in global aspectj preference
> > >> - use AspectJ aware version of outline view DESELECTED in global aspectj
> > >> preference
> > >> - all input fields on AspectJ Compiler project settings empty (except
> > >> incremental checkbox)
> > >> - enabled aspectj nature
> > >> - delete default.lst file
> > >
> > >> Scenario 1:
> > >> - delete default output folder through eclipse resource perspective
> > >> - incremental compile DESELECTED
> > >> - Select Project -> Rebuild All
> > >> - default.lst is created
> > >> - NO default output folder or classes are created
> > >
> > >> Scenario 2:
> > >> - delete default output folder through eclipse resource perspective
> > >> - incremental compile SELECTED
> > >> - Select Project -> Rebuild All
> > >> - default.lst is created
> > >> - NO default output folder or classes are created
> > >
> > >> Scenario 3:
> > >> - delete default output folder through eclipse resource perspective
> > >> - manually create default output folder through eclipse resource
> > >> perspective
> > >> - incremental compile DESELECTED
> > >> - Select Project -> Rebuild All
> > >> - default.lst is created
> > >> - NO classes are created
> > >
> > >> Scenario 4:
> > >> - delete default output folder through eclipse resource perspective
> > >> - manually create default output folder through eclipse resource
> > >> perspective
> > >> - incremental compile SELECTED
> > >> - Select Project -> Rebuild All
> > >> - default.lst is created
> > >> - NO classes are created
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > --
> > George
|
|
|
| Re: Latest build still not creating any class files [message #23445 is a reply to message #23399] |
Fri, 06 June 2003 18:54 |
Julie Waterhouse
Messages: 42
Registered: July 2009 |
Member |
|
|
Okay, maybe I'm getting closer. I saw that James Howe reported similar
problems with class files not appearing when he was using incremental
compile.
(as far as I can see, you're not using incremental compile no matter what
you have set on the compiler properties because you always have the
workbench preference set to suppress automatic builds -- I turned that off
for the following tests, and turned incremental on).
With incremental on, I tried deleting the .class files and making a change
to the aspect. After saving, I did not see the class files show up in the
workspace, however, if I ran the program the changes were there, and in
fact, the class files were visible from the file system. So...
delete .class files
make change
save
see no class files
can run program and see changes
F5 refresh
class files appear.
I then tried deleting the entire output directory and default.lst file,
making a change to the aspect and saving. In that case:
delete output dir and default.lst
make change
save
see no output dir/default.lst
get error when trying to run program - cannot find class
however dir and class files exist on the filesystem
F5 refresh
output dir and default.lst appear
can run program.
I'll look to see whether we can do this refresh programatically, but
wanted to share my findings so far.
Julie
AJDT Developement
Julie Waterhouse wrote:
> Chad, I've been trying to recreate your problem, but cannot. I tried all
> your scenarios, but they produced class files just fine for me.
> After seeing Andy's reply to your post about this in another thread, I
> also tried the following:
> Using eclipse with ajdt plugin level 1.1.1
> -create simple aspectJ project (one class, one aspect)
> -build
> -delete output folder & default.lst
> -rebuild
> ->produces class files correctly
> Then upgrade to plugin 1.1.2 via update site
> -restart
> -turn on incremental compile (I get the same results with or without this
> step)
> -delete output folder & default.lst
> -rebuild
> -get error (as Andy predicted): AspectJ Runtime error: bad version number
> found in
> D:\eclipse2.1\eclipse\plugins\org.aspectj.ajde_1.1.1\aspectj rt.jar
> expected 1.1rc2 found 1.1rc1. Please place a valid aspectjrt.jar on the
> classpath.
> -replaced aspectjrt.jar on the Java build path with correct 1.1.2 version
> -"OK" triggered empty Output folder to be created
> -rebuild all
> ->produces class files correctly
> Chad Woolley wrote:
> > George,
> > No, when I re-enable the aspectj nature, the aspectjrt.jar is added back
> > to the classpath just fine. The problem is that no class files are ever
> > generated when the aspectj nature is enabled.
> > Thanks for your response,
> > Chad
> > George Harley wrote:
> > > Hi Chad,
> > > Are you saying that when you remove the aspectj nature and then
re-enable
> > > it you are not seeing aspectjrt.jar in your project dependencies ?
> > > Best regards,
> > > George
> > > On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> > > <chad_woolley@choicehotels.com> wrote:
> > > > Additional info based on comment in previous thread:
> > > >
> > > > There is no aspectjrt.jar in my project. The only jar in my lib
folder
> > > > is
> > > > junit.jar, and this is the only jar (other than the JRE) on my
classpath
> > > > in the project properties.
> > > >
> > > > Chad Woolley wrote:
> > > >
> > > >> Hello,
> > > >
> > > >> I am still having the problem of the latest build not creating any
class
> > > >> files. This was mentioned in a previous thread, but since this was
not
> > > >> mentioned in the "known AJDT bugs" just posted, I thought I would
bring
> > > >> it
> > > >> up again.
> > > >
> > > >> I am using AJDT dev build 1.1.3, installed via Eclipse
Install/Update,
> > > >> on
> > > >> eclipse 2.1.0.
> > > >
> > > >> Here is a detailed analysis of when the bug occurs and how to
recreate
> > > >> it:
> > > >
> > > >
> > > >> ===========================================
> > > >
> > > >
> > > >> Scenario 0 ("Control Group" - no aspectj):
> > > >> - Removed aspectj nature
> > > >> - Deleted default output folder
> > > >> - Select Project -> Rebuild All
> > > >> - default output folder and classes are all successfully created
> > > >> - everything works fine (but is compiled without aspects)
> > > >
> > > >> ---------------------------------------
> > > >
> > > >> Scenarios 1-4 common setup preparation: - no other projects open in
> > > >> workspace
> > > >> - suppress automatic builds SELECTED in global aspectj preference
> > > >> - use AspectJ aware version of outline view DESELECTED in global
aspectj
> > > >> preference
> > > >> - all input fields on AspectJ Compiler project settings empty (except
> > > >> incremental checkbox)
> > > >> - enabled aspectj nature
> > > >> - delete default.lst file
> > > >
> > > >> Scenario 1:
> > > >> - delete default output folder through eclipse resource perspective
> > > >> - incremental compile DESELECTED
> > > >> - Select Project -> Rebuild All
> > > >> - default.lst is created
> > > >> - NO default output folder or classes are created
> > > >
> > > >> Scenario 2:
> > > >> - delete default output folder through eclipse resource perspective
> > > >> - incremental compile SELECTED
> > > >> - Select Project -> Rebuild All
> > > >> - default.lst is created
> > > >> - NO default output folder or classes are created
> > > >
> > > >> Scenario 3:
> > > >> - delete default output folder through eclipse resource perspective
> > > >> - manually create default output folder through eclipse resource
> > > >> perspective
> > > >> - incremental compile DESELECTED
> > > >> - Select Project -> Rebuild All
> > > >> - default.lst is created
> > > >> - NO classes are created
> > > >
> > > >> Scenario 4:
> > > >> - delete default output folder through eclipse resource perspective
> > > >> - manually create default output folder through eclipse resource
> > > >> perspective
> > > >> - incremental compile SELECTED
> > > >> - Select Project -> Rebuild All
> > > >> - default.lst is created
> > > >> - NO classes are created
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > --
> > > George
|
|
|
| Re: Latest build still not creating any class files [message #23616 is a reply to message #23445] |
Mon, 09 June 2003 21:52 |
| Eclipse User |
|
|
|
Originally posted by: chad_woolley.choicehotels.com
Julie,
Thanks for looking into this. I wanted to mention a couple of things:
1. When I said the class files are generated, they are not generated AT
ALL. There is nothing in the filesystem - it's not just that eclipse
isn't refreshing and showing them.
2. When I run this same scenario on a different machine, the class files
are generated for some projects! (Yes, it is build 1.1.3 on both
machines). The funny thing is, the eclipse install on the second machine
is a clone of the first machine (I copied the entire eclipse dir over the
network). Also, another aspectJ project (a much larger one), still has
the problem. It is a much smaller and simpler project that works on one
machine but doesn't work on the other.
I'm trying to figure out what the variable factor is, but I can't. My
best guess is that some other plugin I have is interacting and causing
problems (I do have different plugins installed since I cloned the eclipse
install).
Anyway, thanks for looking into this. I will also keep trying to figure
out what the cause is.
-- Chad
Julie Waterhouse wrote:
> Okay, maybe I'm getting closer. I saw that James Howe reported similar
> problems with class files not appearing when he was using incremental
> compile.
> (as far as I can see, you're not using incremental compile no matter what
> you have set on the compiler properties because you always have the
> workbench preference set to suppress automatic builds -- I turned that off
> for the following tests, and turned incremental on).
> With incremental on, I tried deleting the .class files and making a change
> to the aspect. After saving, I did not see the class files show up in the
> workspace, however, if I ran the program the changes were there, and in
> fact, the class files were visible from the file system. So...
> delete .class files
> make change
> save
> see no class files
> can run program and see changes
> F5 refresh
> class files appear.
> I then tried deleting the entire output directory and default.lst file,
> making a change to the aspect and saving. In that case:
> delete output dir and default.lst
> make change
> save
> see no output dir/default.lst
> get error when trying to run program - cannot find class
> however dir and class files exist on the filesystem
> F5 refresh
> output dir and default.lst appear
> can run program.
> I'll look to see whether we can do this refresh programatically, but
> wanted to share my findings so far.
> Julie
> AJDT Developement
> Julie Waterhouse wrote:
> > Chad, I've been trying to recreate your problem, but cannot. I tried all
> > your scenarios, but they produced class files just fine for me.
> > After seeing Andy's reply to your post about this in another thread, I
> > also tried the following:
> > Using eclipse with ajdt plugin level 1.1.1
> > -create simple aspectJ project (one class, one aspect)
> > -build
> > -delete output folder & default.lst
> > -rebuild
> > ->produces class files correctly
> > Then upgrade to plugin 1.1.2 via update site
> > -restart
> > -turn on incremental compile (I get the same results with or without this
> > step)
> > -delete output folder & default.lst
> > -rebuild
> > -get error (as Andy predicted): AspectJ Runtime error: bad version number
> > found in
> > D:\eclipse2.1\eclipse\plugins\org.aspectj.ajde_1.1.1\aspectj rt.jar
> > expected 1.1rc2 found 1.1rc1. Please place a valid aspectjrt.jar on the
> > classpath.
> > -replaced aspectjrt.jar on the Java build path with correct 1.1.2 version
> > -"OK" triggered empty Output folder to be created
> > -rebuild all
> > ->produces class files correctly
> > Chad Woolley wrote:
> > > George,
> > > No, when I re-enable the aspectj nature, the aspectjrt.jar is added back
> > > to the classpath just fine. The problem is that no class files are ever
> > > generated when the aspectj nature is enabled.
> > > Thanks for your response,
> > > Chad
> > > George Harley wrote:
> > > > Hi Chad,
> > > > Are you saying that when you remove the aspectj nature and then
> re-enable
> > > > it you are not seeing aspectjrt.jar in your project dependencies ?
> > > > Best regards,
> > > > George
> > > > On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> > > > <chad_woolley@choicehotels.com> wrote:
> > > > > Additional info based on comment in previous thread:
> > > > >
> > > > > There is no aspectjrt.jar in my project. The only jar in my lib
> folder
> > > > > is
> > > > > junit.jar, and this is the only jar (other than the JRE) on my
> classpath
> > > > > in the project properties.
> > > > >
> > > > > Chad Woolley wrote:
> > > > >
> > > > >> Hello,
> > > > >
> > > > >> I am still having the problem of the latest build not creating any
> class
> > > > >> files. This was mentioned in a previous thread, but since this was
> not
> > > > >> mentioned in the "known AJDT bugs" just posted, I thought I would
> bring
> > > > >> it
> > > > >> up again.
> > > > >
> > > > >> I am using AJDT dev build 1.1.3, installed via Eclipse
> Install/Update,
> > > > >> on
> > > > >> eclipse 2.1.0.
> > > > >
> > > > >> Here is a detailed analysis of when the bug occurs and how to
> recreate
> > > > >> it:
> > > > >
> > > > >
> > > > >> ===========================================
> > > > >
> > > > >
> > > > >> Scenario 0 ("Control Group" - no aspectj):
> > > > >> - Removed aspectj nature
> > > > >> - Deleted default output folder
> > > > >> - Select Project -> Rebuild All
> > > > >> - default output folder and classes are all successfully created
> > > > >> - everything works fine (but is compiled without aspects)
> > > > >
> > > > >> ---------------------------------------
> > > > >
> > > > >> Scenarios 1-4 common setup preparation: - no other projects open in
> > > > >> workspace
> > > > >> - suppress automatic builds SELECTED in global aspectj preference
> > > > >> - use AspectJ aware version of outline view DESELECTED in global
> aspectj
> > > > >> preference
> > > > >> - all input fields on AspectJ Compiler project settings empty
(except
> > > > >> incremental checkbox)
> > > > >> - enabled aspectj nature
> > > > >> - delete default.lst file
> > > > >
> > > > >> Scenario 1:
> > > > >> - delete default output folder through eclipse resource perspective
> > > > >> - incremental compile DESELECTED
> > > > >> - Select Project -> Rebuild All
> > > > >> - default.lst is created
> > > > >> - NO default output folder or classes are created
> > > > >
> > > > >> Scenario 2:
> > > > >> - delete default output folder through eclipse resource perspective
> > > > >> - incremental compile SELECTED
> > > > >> - Select Project -> Rebuild All
> > > > >> - default.lst is created
> > > > >> - NO default output folder or classes are created
> > > > >
> > > > >> Scenario 3:
> > > > >> - delete default output folder through eclipse resource perspective
> > > > >> - manually create default output folder through eclipse resource
> > > > >> perspective
> > > > >> - incremental compile DESELECTED
> > > > >> - Select Project -> Rebuild All
> > > > >> - default.lst is created
> > > > >> - NO classes are created
> > > > >
> > > > >> Scenario 4:
> > > > >> - delete default output folder through eclipse resource perspective
> > > > >> - manually create default output folder through eclipse resource
> > > > >> perspective
> > > > >> - incremental compile SELECTED
> > > > >> - Select Project -> Rebuild All
> > > > >> - default.lst is created
> > > > >> - NO classes are created
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > --
> > > > George
|
|
|
| Re: Latest build still not creating any class files [message #23701 is a reply to message #23616] |
Thu, 12 June 2003 19:51 |
Julie Waterhouse
Messages: 42
Registered: July 2009 |
Member |
|
|
Chad,
I have tried many scenarios to reproduce this, but cannot. I've even
tried creating a project in a 1.1.1 environment and upgrading through
1.1.2 and 1.1.3, but class files are always generated for me.
We have put a few changes into the latest 1.1.3 dev build (mostly related
to incremental), so you may want to pick that up just to give it a try
(you will need to manually uninstall your current 1.1.3 build in order to
get the latest via the update site). Quite frankly, I don't think it will
fix the problem. Because you had suppressed automatic builds, you were
not getting incremental no matter what your project level setting was, so
our fixes likely won't affect you. Worth a try just in case.
If that fails, then I think we need you to send us the minimal test case
you have that reproduces the problem. If you can export the smallest
project you that exhibits this behaviour, and send it to me, I'll try it
in my Eclipse environment and see if I have the problem.
Regards,
~Julie
juliew@ca.ibm.com
AJDT Development
Chad Woolley wrote:
> Julie,
> Thanks for looking into this. I wanted to mention a couple of things:
> 1. When I said the class files are generated, they are not generated AT
> ALL. There is nothing in the filesystem - it's not just that eclipse
> isn't refreshing and showing them.
> 2. When I run this same scenario on a different machine, the class files
> are generated for some projects! (Yes, it is build 1.1.3 on both
> machines). The funny thing is, the eclipse install on the second machine
> is a clone of the first machine (I copied the entire eclipse dir over the
> network). Also, another aspectJ project (a much larger one), still has
> the problem. It is a much smaller and simpler project that works on one
> machine but doesn't work on the other.
> I'm trying to figure out what the variable factor is, but I can't. My
> best guess is that some other plugin I have is interacting and causing
> problems (I do have different plugins installed since I cloned the eclipse
> install).
> Anyway, thanks for looking into this. I will also keep trying to figure
> out what the cause is.
> -- Chad
> Julie Waterhouse wrote:
> > Okay, maybe I'm getting closer. I saw that James Howe reported similar
> > problems with class files not appearing when he was using incremental
> > compile.
> > (as far as I can see, you're not using incremental compile no matter what
> > you have set on the compiler properties because you always have the
> > workbench preference set to suppress automatic builds -- I turned that off
> > for the following tests, and turned incremental on).
> > With incremental on, I tried deleting the .class files and making a change
> > to the aspect. After saving, I did not see the class files show up in the
> > workspace, however, if I ran the program the changes were there, and in
> > fact, the class files were visible from the file system. So...
> > delete .class files
> > make change
> > save
> > see no class files
> > can run program and see changes
> > F5 refresh
> > class files appear.
> > I then tried deleting the entire output directory and default.lst file,
> > making a change to the aspect and saving. In that case:
> > delete output dir and default.lst
> > make change
> > save
> > see no output dir/default.lst
> > get error when trying to run program - cannot find class
> > however dir and class files exist on the filesystem
> > F5 refresh
> > output dir and default.lst appear
> > can run program.
> > I'll look to see whether we can do this refresh programatically, but
> > wanted to share my findings so far.
> > Julie
> > AJDT Developement
> > Julie Waterhouse wrote:
> > > Chad, I've been trying to recreate your problem, but cannot. I tried all
> > > your scenarios, but they produced class files just fine for me.
> > > After seeing Andy's reply to your post about this in another thread, I
> > > also tried the following:
> > > Using eclipse with ajdt plugin level 1.1.1
> > > -create simple aspectJ project (one class, one aspect)
> > > -build
> > > -delete output folder & default.lst
> > > -rebuild
> > > ->produces class files correctly
> > > Then upgrade to plugin 1.1.2 via update site
> > > -restart
> > > -turn on incremental compile (I get the same results with or without this
> > > step)
> > > -delete output folder & default.lst
> > > -rebuild
> > > -get error (as Andy predicted): AspectJ Runtime error: bad version number
> > > found in
> > > D:\eclipse2.1\eclipse\plugins\org.aspectj.ajde_1.1.1\aspectj rt.jar
> > > expected 1.1rc2 found 1.1rc1. Please place a valid aspectjrt.jar on the
> > > classpath.
> > > -replaced aspectjrt.jar on the Java build path with correct 1.1.2 version
> > > -"OK" triggered empty Output folder to be created
> > > -rebuild all
> > > ->produces class files correctly
> > > Chad Woolley wrote:
> > > > George,
> > > > No, when I re-enable the aspectj nature, the aspectjrt.jar is added
back
> > > > to the classpath just fine. The problem is that no class files are
ever
> > > > generated when the aspectj nature is enabled.
> > > > Thanks for your response,
> > > > Chad
> > > > George Harley wrote:
> > > > > Hi Chad,
> > > > > Are you saying that when you remove the aspectj nature and then
> > re-enable
> > > > > it you are not seeing aspectjrt.jar in your project dependencies ?
> > > > > Best regards,
> > > > > George
> > > > > On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> > > > > <chad_woolley@choicehotels.com> wrote:
> > > > > > Additional info based on comment in previous thread:
> > > > > >
> > > > > > There is no aspectjrt.jar in my project. The only jar in my lib
> > folder
> > > > > > is
> > > > > > junit.jar, and this is the only jar (other than the JRE) on my
> > classpath
> > > > > > in the project properties.
> > > > > >
> > > > > > Chad Woolley wrote:
> > > > > >
> > > > > >> Hello,
> > > > > >
> > > > > >> I am still having the problem of the latest build not creating any
> > class
> > > > > >> files. This was mentioned in a previous thread, but since this
was
> > not
> > > > > >> mentioned in the "known AJDT bugs" just posted, I thought I would
> > bring
> > > > > >> it
> > > > > >> up again.
> > > > > >
> > > > > >> I am using AJDT dev build 1.1.3, installed via Eclipse
> > Install/Update,
> > > > > >> on
> > > > > >> eclipse 2.1.0.
> > > > > >
> > > > > >> Here is a detailed analysis of when the bug occurs and how to
> > recreate
> > > > > >> it:
> > > > > >
> > > > > >
> > > > > >> ===========================================
> > > > > >
> > > > > >
> > > > > >> Scenario 0 ("Control Group" - no aspectj):
> > > > > >> - Removed aspectj nature
> > > > > >> - Deleted default output folder
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default output folder and classes are all successfully created
> > > > > >> - everything works fine (but is compiled without aspects)
> > > > > >
> > > > > >> ---------------------------------------
> > > > > >
> > > > > >> Scenarios 1-4 common setup preparation: - no other projects open
in
> > > > > >> workspace
> > > > > >> - suppress automatic builds SELECTED in global aspectj preference
> > > > > >> - use AspectJ aware version of outline view DESELECTED in global
> > aspectj
> > > > > >> preference
> > > > > >> - all input fields on AspectJ Compiler project settings empty
> (except
> > > > > >> incremental checkbox)
> > > > > >> - enabled aspectj nature
> > > > > >> - delete default.lst file
> > > > > >
> > > > > >> Scenario 1:
> > > > > >> - delete default output folder through eclipse resource
perspective
> > > > > >> - incremental compile DESELECTED
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default.lst is created
> > > > > >> - NO default output folder or classes are created
> > > > > >
> > > > > >> Scenario 2:
> > > > > >> - delete default output folder through eclipse resource
perspective
> > > > > >> - incremental compile SELECTED
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default.lst is created
> > > > > >> - NO default output folder or classes are created
> > > > > >
> > > > > >> Scenario 3:
> > > > > >> - delete default output folder through eclipse resource
perspective
> > > > > >> - manually create default output folder through eclipse resource
> > > > > >> perspective
> > > > > >> - incremental compile DESELECTED
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default.lst is created
> > > > > >> - NO classes are created
> > > > > >
> > > > > >> Scenario 4:
> > > > > >> - delete default output folder through eclipse resource
perspective
> > > > > >> - manually create default output folder through eclipse resource
> > > > > >> perspective
> > > > > >> - incremental compile SELECTED
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default.lst is created
> > > > > >> - NO classes are created
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > --
> > > > > George
|
|
| |
| Re: Latest build still not creating any class files [message #568097 is a reply to message #22890] |
Wed, 04 June 2003 19:07 |
George Harley
Messages: 70
Registered: July 2009 |
Member |
|
|
Hi Chad,
Are you saying that when you remove the aspectj nature and then re-enable
it you are not seeing aspectjrt.jar in your project dependencies ?
Best regards,
George
On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
<chad_woolley@choicehotels.com> wrote:
> Additional info based on comment in previous thread:
>
> There is no aspectjrt.jar in my project. The only jar in my lib folder
> is
> junit.jar, and this is the only jar (other than the JRE) on my classpath
> in the project properties.
>
> Chad Woolley wrote:
>
>> Hello,
>
>> I am still having the problem of the latest build not creating any class
>> files. This was mentioned in a previous thread, but since this was not
>> mentioned in the "known AJDT bugs" just posted, I thought I would bring
>> it
>> up again.
>
>> I am using AJDT dev build 1.1.3, installed via Eclipse Install/Update,
>> on
>> eclipse 2.1.0.
>
>> Here is a detailed analysis of when the bug occurs and how to recreate
>> it:
>
>
>> ===========================================
>
>
>> Scenario 0 ("Control Group" - no aspectj):
>> - Removed aspectj nature
>> - Deleted default output folder
>> - Select Project -> Rebuild All
>> - default output folder and classes are all successfully created
>> - everything works fine (but is compiled without aspects)
>
>> ---------------------------------------
>
>> Scenarios 1-4 common setup preparation: - no other projects open in
>> workspace
>> - suppress automatic builds SELECTED in global aspectj preference
>> - use AspectJ aware version of outline view DESELECTED in global aspectj
>> preference
>> - all input fields on AspectJ Compiler project settings empty (except
>> incremental checkbox)
>> - enabled aspectj nature
>> - delete default.lst file
>
>> Scenario 1:
>> - delete default output folder through eclipse resource perspective
>> - incremental compile DESELECTED
>> - Select Project -> Rebuild All
>> - default.lst is created
>> - NO default output folder or classes are created
>
>> Scenario 2:
>> - delete default output folder through eclipse resource perspective
>> - incremental compile SELECTED
>> - Select Project -> Rebuild All
>> - default.lst is created
>> - NO default output folder or classes are created
>
>> Scenario 3:
>> - delete default output folder through eclipse resource perspective
>> - manually create default output folder through eclipse resource
>> perspective
>> - incremental compile DESELECTED
>> - Select Project -> Rebuild All
>> - default.lst is created
>> - NO classes are created
>
>> Scenario 4:
>> - delete default output folder through eclipse resource perspective
>> - manually create default output folder through eclipse resource
>> perspective
>> - incremental compile SELECTED
>> - Select Project -> Rebuild All
>> - default.lst is created
>> - NO classes are created
>
>
>
>
>
>
>
>
--
George
|
|
|
| Re: Latest build still not creating any class files [message #568199 is a reply to message #22978] |
Thu, 05 June 2003 00:52 |
Chad Woolley
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
George,
No, when I re-enable the aspectj nature, the aspectjrt.jar is added back
to the classpath just fine. The problem is that no class files are ever
generated when the aspectj nature is enabled.
Thanks for your response,
Chad
George Harley wrote:
> Hi Chad,
> Are you saying that when you remove the aspectj nature and then re-enable
> it you are not seeing aspectjrt.jar in your project dependencies ?
> Best regards,
> George
> On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> <chad_woolley@choicehotels.com> wrote:
> > Additional info based on comment in previous thread:
> >
> > There is no aspectjrt.jar in my project. The only jar in my lib folder
> > is
> > junit.jar, and this is the only jar (other than the JRE) on my classpath
> > in the project properties.
> >
> > Chad Woolley wrote:
> >
> >> Hello,
> >
> >> I am still having the problem of the latest build not creating any class
> >> files. This was mentioned in a previous thread, but since this was not
> >> mentioned in the "known AJDT bugs" just posted, I thought I would bring
> >> it
> >> up again.
> >
> >> I am using AJDT dev build 1.1.3, installed via Eclipse Install/Update,
> >> on
> >> eclipse 2.1.0.
> >
> >> Here is a detailed analysis of when the bug occurs and how to recreate
> >> it:
> >
> >
> >> ===========================================
> >
> >
> >> Scenario 0 ("Control Group" - no aspectj):
> >> - Removed aspectj nature
> >> - Deleted default output folder
> >> - Select Project -> Rebuild All
> >> - default output folder and classes are all successfully created
> >> - everything works fine (but is compiled without aspects)
> >
> >> ---------------------------------------
> >
> >> Scenarios 1-4 common setup preparation: - no other projects open in
> >> workspace
> >> - suppress automatic builds SELECTED in global aspectj preference
> >> - use AspectJ aware version of outline view DESELECTED in global aspectj
> >> preference
> >> - all input fields on AspectJ Compiler project settings empty (except
> >> incremental checkbox)
> >> - enabled aspectj nature
> >> - delete default.lst file
> >
> >> Scenario 1:
> >> - delete default output folder through eclipse resource perspective
> >> - incremental compile DESELECTED
> >> - Select Project -> Rebuild All
> >> - default.lst is created
> >> - NO default output folder or classes are created
> >
> >> Scenario 2:
> >> - delete default output folder through eclipse resource perspective
> >> - incremental compile SELECTED
> >> - Select Project -> Rebuild All
> >> - default.lst is created
> >> - NO default output folder or classes are created
> >
> >> Scenario 3:
> >> - delete default output folder through eclipse resource perspective
> >> - manually create default output folder through eclipse resource
> >> perspective
> >> - incremental compile DESELECTED
> >> - Select Project -> Rebuild All
> >> - default.lst is created
> >> - NO classes are created
> >
> >> Scenario 4:
> >> - delete default output folder through eclipse resource perspective
> >> - manually create default output folder through eclipse resource
> >> perspective
> >> - incremental compile SELECTED
> >> - Select Project -> Rebuild All
> >> - default.lst is created
> >> - NO classes are created
> >
> >
> >
> >
> >
> >
> >
> >
> --
> George
|
|
|
| Re: Latest build still not creating any class files [message #568635 is a reply to message #23107] |
Fri, 06 June 2003 18:45 |
Julie Waterhouse
Messages: 42
Registered: July 2009 |
Member |
|
|
Chad, I've been trying to recreate your problem, but cannot. I tried all
your scenarios, but they produced class files just fine for me.
After seeing Andy's reply to your post about this in another thread, I
also tried the following:
Using eclipse with ajdt plugin level 1.1.1
-create simple aspectJ project (one class, one aspect)
-build
-delete output folder & default.lst
-rebuild
->produces class files correctly
Then upgrade to plugin 1.1.2 via update site
-restart
-turn on incremental compile (I get the same results with or without this
step)
-delete output folder & default.lst
-rebuild
-get error (as Andy predicted): AspectJ Runtime error: bad version number
found in
D:\eclipse2.1\eclipse\plugins\org.aspectj.ajde_1.1.1\aspectj rt.jar
expected 1.1rc2 found 1.1rc1. Please place a valid aspectjrt.jar on the
classpath.
-replaced aspectjrt.jar on the Java build path with correct 1.1.2 version
-"OK" triggered empty Output folder to be created
-rebuild all
->produces class files correctly
Chad Woolley wrote:
> George,
> No, when I re-enable the aspectj nature, the aspectjrt.jar is added back
> to the classpath just fine. The problem is that no class files are ever
> generated when the aspectj nature is enabled.
> Thanks for your response,
> Chad
> George Harley wrote:
> > Hi Chad,
> > Are you saying that when you remove the aspectj nature and then re-enable
> > it you are not seeing aspectjrt.jar in your project dependencies ?
> > Best regards,
> > George
> > On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> > <chad_woolley@choicehotels.com> wrote:
> > > Additional info based on comment in previous thread:
> > >
> > > There is no aspectjrt.jar in my project. The only jar in my lib folder
> > > is
> > > junit.jar, and this is the only jar (other than the JRE) on my classpath
> > > in the project properties.
> > >
> > > Chad Woolley wrote:
> > >
> > >> Hello,
> > >
> > >> I am still having the problem of the latest build not creating any class
> > >> files. This was mentioned in a previous thread, but since this was not
> > >> mentioned in the "known AJDT bugs" just posted, I thought I would bring
> > >> it
> > >> up again.
> > >
> > >> I am using AJDT dev build 1.1.3, installed via Eclipse Install/Update,
> > >> on
> > >> eclipse 2.1.0.
> > >
> > >> Here is a detailed analysis of when the bug occurs and how to recreate
> > >> it:
> > >
> > >
> > >> ===========================================
> > >
> > >
> > >> Scenario 0 ("Control Group" - no aspectj):
> > >> - Removed aspectj nature
> > >> - Deleted default output folder
> > >> - Select Project -> Rebuild All
> > >> - default output folder and classes are all successfully created
> > >> - everything works fine (but is compiled without aspects)
> > >
> > >> ---------------------------------------
> > >
> > >> Scenarios 1-4 common setup preparation: - no other projects open in
> > >> workspace
> > >> - suppress automatic builds SELECTED in global aspectj preference
> > >> - use AspectJ aware version of outline view DESELECTED in global aspectj
> > >> preference
> > >> - all input fields on AspectJ Compiler project settings empty (except
> > >> incremental checkbox)
> > >> - enabled aspectj nature
> > >> - delete default.lst file
> > >
> > >> Scenario 1:
> > >> - delete default output folder through eclipse resource perspective
> > >> - incremental compile DESELECTED
> > >> - Select Project -> Rebuild All
> > >> - default.lst is created
> > >> - NO default output folder or classes are created
> > >
> > >> Scenario 2:
> > >> - delete default output folder through eclipse resource perspective
> > >> - incremental compile SELECTED
> > >> - Select Project -> Rebuild All
> > >> - default.lst is created
> > >> - NO default output folder or classes are created
> > >
> > >> Scenario 3:
> > >> - delete default output folder through eclipse resource perspective
> > >> - manually create default output folder through eclipse resource
> > >> perspective
> > >> - incremental compile DESELECTED
> > >> - Select Project -> Rebuild All
> > >> - default.lst is created
> > >> - NO classes are created
> > >
> > >> Scenario 4:
> > >> - delete default output folder through eclipse resource perspective
> > >> - manually create default output folder through eclipse resource
> > >> perspective
> > >> - incremental compile SELECTED
> > >> - Select Project -> Rebuild All
> > >> - default.lst is created
> > >> - NO classes are created
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > --
> > George
|
|
|
| Re: Latest build still not creating any class files [message #568661 is a reply to message #23399] |
Fri, 06 June 2003 18:54 |
Julie Waterhouse
Messages: 42
Registered: July 2009 |
Member |
|
|
Okay, maybe I'm getting closer. I saw that James Howe reported similar
problems with class files not appearing when he was using incremental
compile.
(as far as I can see, you're not using incremental compile no matter what
you have set on the compiler properties because you always have the
workbench preference set to suppress automatic builds -- I turned that off
for the following tests, and turned incremental on).
With incremental on, I tried deleting the .class files and making a change
to the aspect. After saving, I did not see the class files show up in the
workspace, however, if I ran the program the changes were there, and in
fact, the class files were visible from the file system. So...
delete .class files
make change
save
see no class files
can run program and see changes
F5 refresh
class files appear.
I then tried deleting the entire output directory and default.lst file,
making a change to the aspect and saving. In that case:
delete output dir and default.lst
make change
save
see no output dir/default.lst
get error when trying to run program - cannot find class
however dir and class files exist on the filesystem
F5 refresh
output dir and default.lst appear
can run program.
I'll look to see whether we can do this refresh programatically, but
wanted to share my findings so far.
Julie
AJDT Developement
Julie Waterhouse wrote:
> Chad, I've been trying to recreate your problem, but cannot. I tried all
> your scenarios, but they produced class files just fine for me.
> After seeing Andy's reply to your post about this in another thread, I
> also tried the following:
> Using eclipse with ajdt plugin level 1.1.1
> -create simple aspectJ project (one class, one aspect)
> -build
> -delete output folder & default.lst
> -rebuild
> ->produces class files correctly
> Then upgrade to plugin 1.1.2 via update site
> -restart
> -turn on incremental compile (I get the same results with or without this
> step)
> -delete output folder & default.lst
> -rebuild
> -get error (as Andy predicted): AspectJ Runtime error: bad version number
> found in
> D:\eclipse2.1\eclipse\plugins\org.aspectj.ajde_1.1.1\aspectj rt.jar
> expected 1.1rc2 found 1.1rc1. Please place a valid aspectjrt.jar on the
> classpath.
> -replaced aspectjrt.jar on the Java build path with correct 1.1.2 version
> -"OK" triggered empty Output folder to be created
> -rebuild all
> ->produces class files correctly
> Chad Woolley wrote:
> > George,
> > No, when I re-enable the aspectj nature, the aspectjrt.jar is added back
> > to the classpath just fine. The problem is that no class files are ever
> > generated when the aspectj nature is enabled.
> > Thanks for your response,
> > Chad
> > George Harley wrote:
> > > Hi Chad,
> > > Are you saying that when you remove the aspectj nature and then
re-enable
> > > it you are not seeing aspectjrt.jar in your project dependencies ?
> > > Best regards,
> > > George
> > > On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> > > <chad_woolley@choicehotels.com> wrote:
> > > > Additional info based on comment in previous thread:
> > > >
> > > > There is no aspectjrt.jar in my project. The only jar in my lib
folder
> > > > is
> > > > junit.jar, and this is the only jar (other than the JRE) on my
classpath
> > > > in the project properties.
> > > >
> > > > Chad Woolley wrote:
> > > >
> > > >> Hello,
> > > >
> > > >> I am still having the problem of the latest build not creating any
class
> > > >> files. This was mentioned in a previous thread, but since this was
not
> > > >> mentioned in the "known AJDT bugs" just posted, I thought I would
bring
> > > >> it
> > > >> up again.
> > > >
> > > >> I am using AJDT dev build 1.1.3, installed via Eclipse
Install/Update,
> > > >> on
> > > >> eclipse 2.1.0.
> > > >
> > > >> Here is a detailed analysis of when the bug occurs and how to
recreate
> > > >> it:
> > > >
> > > >
> > > >> ===========================================
> > > >
> > > >
> > > >> Scenario 0 ("Control Group" - no aspectj):
> > > >> - Removed aspectj nature
> > > >> - Deleted default output folder
> > > >> - Select Project -> Rebuild All
> > > >> - default output folder and classes are all successfully created
> > > >> - everything works fine (but is compiled without aspects)
> > > >
> > > >> ---------------------------------------
> > > >
> > > >> Scenarios 1-4 common setup preparation: - no other projects open in
> > > >> workspace
> > > >> - suppress automatic builds SELECTED in global aspectj preference
> > > >> - use AspectJ aware version of outline view DESELECTED in global
aspectj
> > > >> preference
> > > >> - all input fields on AspectJ Compiler project settings empty (except
> > > >> incremental checkbox)
> > > >> - enabled aspectj nature
> > > >> - delete default.lst file
> > > >
> > > >> Scenario 1:
> > > >> - delete default output folder through eclipse resource perspective
> > > >> - incremental compile DESELECTED
> > > >> - Select Project -> Rebuild All
> > > >> - default.lst is created
> > > >> - NO default output folder or classes are created
> > > >
> > > >> Scenario 2:
> > > >> - delete default output folder through eclipse resource perspective
> > > >> - incremental compile SELECTED
> > > >> - Select Project -> Rebuild All
> > > >> - default.lst is created
> > > >> - NO default output folder or classes are created
> > > >
> > > >> Scenario 3:
> > > >> - delete default output folder through eclipse resource perspective
> > > >> - manually create default output folder through eclipse resource
> > > >> perspective
> > > >> - incremental compile DESELECTED
> > > >> - Select Project -> Rebuild All
> > > >> - default.lst is created
> > > >> - NO classes are created
> > > >
> > > >> Scenario 4:
> > > >> - delete default output folder through eclipse resource perspective
> > > >> - manually create default output folder through eclipse resource
> > > >> perspective
> > > >> - incremental compile SELECTED
> > > >> - Select Project -> Rebuild All
> > > >> - default.lst is created
> > > >> - NO classes are created
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > --
> > > George
|
|
|
| Re: Latest build still not creating any class files [message #568800 is a reply to message #23445] |
Mon, 09 June 2003 21:52 |
Chad Woolley
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
Julie,
Thanks for looking into this. I wanted to mention a couple of things:
1. When I said the class files are generated, they are not generated AT
ALL. There is nothing in the filesystem - it's not just that eclipse
isn't refreshing and showing them.
2. When I run this same scenario on a different machine, the class files
are generated for some projects! (Yes, it is build 1.1.3 on both
machines). The funny thing is, the eclipse install on the second machine
is a clone of the first machine (I copied the entire eclipse dir over the
network). Also, another aspectJ project (a much larger one), still has
the problem. It is a much smaller and simpler project that works on one
machine but doesn't work on the other.
I'm trying to figure out what the variable factor is, but I can't. My
best guess is that some other plugin I have is interacting and causing
problems (I do have different plugins installed since I cloned the eclipse
install).
Anyway, thanks for looking into this. I will also keep trying to figure
out what the cause is.
-- Chad
Julie Waterhouse wrote:
> Okay, maybe I'm getting closer. I saw that James Howe reported similar
> problems with class files not appearing when he was using incremental
> compile.
> (as far as I can see, you're not using incremental compile no matter what
> you have set on the compiler properties because you always have the
> workbench preference set to suppress automatic builds -- I turned that off
> for the following tests, and turned incremental on).
> With incremental on, I tried deleting the .class files and making a change
> to the aspect. After saving, I did not see the class files show up in the
> workspace, however, if I ran the program the changes were there, and in
> fact, the class files were visible from the file system. So...
> delete .class files
> make change
> save
> see no class files
> can run program and see changes
> F5 refresh
> class files appear.
> I then tried deleting the entire output directory and default.lst file,
> making a change to the aspect and saving. In that case:
> delete output dir and default.lst
> make change
> save
> see no output dir/default.lst
> get error when trying to run program - cannot find class
> however dir and class files exist on the filesystem
> F5 refresh
> output dir and default.lst appear
> can run program.
> I'll look to see whether we can do this refresh programatically, but
> wanted to share my findings so far.
> Julie
> AJDT Developement
> Julie Waterhouse wrote:
> > Chad, I've been trying to recreate your problem, but cannot. I tried all
> > your scenarios, but they produced class files just fine for me.
> > After seeing Andy's reply to your post about this in another thread, I
> > also tried the following:
> > Using eclipse with ajdt plugin level 1.1.1
> > -create simple aspectJ project (one class, one aspect)
> > -build
> > -delete output folder & default.lst
> > -rebuild
> > ->produces class files correctly
> > Then upgrade to plugin 1.1.2 via update site
> > -restart
> > -turn on incremental compile (I get the same results with or without this
> > step)
> > -delete output folder & default.lst
> > -rebuild
> > -get error (as Andy predicted): AspectJ Runtime error: bad version number
> > found in
> > D:\eclipse2.1\eclipse\plugins\org.aspectj.ajde_1.1.1\aspectj rt.jar
> > expected 1.1rc2 found 1.1rc1. Please place a valid aspectjrt.jar on the
> > classpath.
> > -replaced aspectjrt.jar on the Java build path with correct 1.1.2 version
> > -"OK" triggered empty Output folder to be created
> > -rebuild all
> > ->produces class files correctly
> > Chad Woolley wrote:
> > > George,
> > > No, when I re-enable the aspectj nature, the aspectjrt.jar is added back
> > > to the classpath just fine. The problem is that no class files are ever
> > > generated when the aspectj nature is enabled.
> > > Thanks for your response,
> > > Chad
> > > George Harley wrote:
> > > > Hi Chad,
> > > > Are you saying that when you remove the aspectj nature and then
> re-enable
> > > > it you are not seeing aspectjrt.jar in your project dependencies ?
> > > > Best regards,
> > > > George
> > > > On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> > > > <chad_woolley@choicehotels.com> wrote:
> > > > > Additional info based on comment in previous thread:
> > > > >
> > > > > There is no aspectjrt.jar in my project. The only jar in my lib
> folder
> > > > > is
> > > > > junit.jar, and this is the only jar (other than the JRE) on my
> classpath
> > > > > in the project properties.
> > > > >
> > > > > Chad Woolley wrote:
> > > > >
> > > > >> Hello,
> > > > >
> > > > >> I am still having the problem of the latest build not creating any
> class
> > > > >> files. This was mentioned in a previous thread, but since this was
> not
> > > > >> mentioned in the "known AJDT bugs" just posted, I thought I would
> bring
> > > > >> it
> > > > >> up again.
> > > > >
> > > > >> I am using AJDT dev build 1.1.3, installed via Eclipse
> Install/Update,
> > > > >> on
> > > > >> eclipse 2.1.0.
> > > > >
> > > > >> Here is a detailed analysis of when the bug occurs and how to
> recreate
> > > > >> it:
> > > > >
> > > > >
> > > > >> ===========================================
> > > > >
> > > > >
> > > > >> Scenario 0 ("Control Group" - no aspectj):
> > > > >> - Removed aspectj nature
> > > > >> - Deleted default output folder
> > > > >> - Select Project -> Rebuild All
> > > > >> - default output folder and classes are all successfully created
> > > > >> - everything works fine (but is compiled without aspects)
> > > > >
> > > > >> ---------------------------------------
> > > > >
> > > > >> Scenarios 1-4 common setup preparation: - no other projects open in
> > > > >> workspace
> > > > >> - suppress automatic builds SELECTED in global aspectj preference
> > > > >> - use AspectJ aware version of outline view DESELECTED in global
> aspectj
> > > > >> preference
> > > > >> - all input fields on AspectJ Compiler project settings empty
(except
> > > > >> incremental checkbox)
> > > > >> - enabled aspectj nature
> > > > >> - delete default.lst file
> > > > >
> > > > >> Scenario 1:
> > > > >> - delete default output folder through eclipse resource perspective
> > > > >> - incremental compile DESELECTED
> > > > >> - Select Project -> Rebuild All
> > > > >> - default.lst is created
> > > > >> - NO default output folder or classes are created
> > > > >
> > > > >> Scenario 2:
> > > > >> - delete default output folder through eclipse resource perspective
> > > > >> - incremental compile SELECTED
> > > > >> - Select Project -> Rebuild All
> > > > >> - default.lst is created
> > > > >> - NO default output folder or classes are created
> > > > >
> > > > >> Scenario 3:
> > > > >> - delete default output folder through eclipse resource perspective
> > > > >> - manually create default output folder through eclipse resource
> > > > >> perspective
> > > > >> - incremental compile DESELECTED
> > > > >> - Select Project -> Rebuild All
> > > > >> - default.lst is created
> > > > >> - NO classes are created
> > > > >
> > > > >> Scenario 4:
> > > > >> - delete default output folder through eclipse resource perspective
> > > > >> - manually create default output folder through eclipse resource
> > > > >> perspective
> > > > >> - incremental compile SELECTED
> > > > >> - Select Project -> Rebuild All
> > > > >> - default.lst is created
> > > > >> - NO classes are created
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > --
> > > > George
|
|
|
| Re: Latest build still not creating any class files [message #568862 is a reply to message #23616] |
Thu, 12 June 2003 19:51 |
Julie Waterhouse
Messages: 42
Registered: July 2009 |
Member |
|
|
Chad,
I have tried many scenarios to reproduce this, but cannot. I've even
tried creating a project in a 1.1.1 environment and upgrading through
1.1.2 and 1.1.3, but class files are always generated for me.
We have put a few changes into the latest 1.1.3 dev build (mostly related
to incremental), so you may want to pick that up just to give it a try
(you will need to manually uninstall your current 1.1.3 build in order to
get the latest via the update site). Quite frankly, I don't think it will
fix the problem. Because you had suppressed automatic builds, you were
not getting incremental no matter what your project level setting was, so
our fixes likely won't affect you. Worth a try just in case.
If that fails, then I think we need you to send us the minimal test case
you have that reproduces the problem. If you can export the smallest
project you that exhibits this behaviour, and send it to me, I'll try it
in my Eclipse environment and see if I have the problem.
Regards,
~Julie
juliew@ca.ibm.com
AJDT Development
Chad Woolley wrote:
> Julie,
> Thanks for looking into this. I wanted to mention a couple of things:
> 1. When I said the class files are generated, they are not generated AT
> ALL. There is nothing in the filesystem - it's not just that eclipse
> isn't refreshing and showing them.
> 2. When I run this same scenario on a different machine, the class files
> are generated for some projects! (Yes, it is build 1.1.3 on both
> machines). The funny thing is, the eclipse install on the second machine
> is a clone of the first machine (I copied the entire eclipse dir over the
> network). Also, another aspectJ project (a much larger one), still has
> the problem. It is a much smaller and simpler project that works on one
> machine but doesn't work on the other.
> I'm trying to figure out what the variable factor is, but I can't. My
> best guess is that some other plugin I have is interacting and causing
> problems (I do have different plugins installed since I cloned the eclipse
> install).
> Anyway, thanks for looking into this. I will also keep trying to figure
> out what the cause is.
> -- Chad
> Julie Waterhouse wrote:
> > Okay, maybe I'm getting closer. I saw that James Howe reported similar
> > problems with class files not appearing when he was using incremental
> > compile.
> > (as far as I can see, you're not using incremental compile no matter what
> > you have set on the compiler properties because you always have the
> > workbench preference set to suppress automatic builds -- I turned that off
> > for the following tests, and turned incremental on).
> > With incremental on, I tried deleting the .class files and making a change
> > to the aspect. After saving, I did not see the class files show up in the
> > workspace, however, if I ran the program the changes were there, and in
> > fact, the class files were visible from the file system. So...
> > delete .class files
> > make change
> > save
> > see no class files
> > can run program and see changes
> > F5 refresh
> > class files appear.
> > I then tried deleting the entire output directory and default.lst file,
> > making a change to the aspect and saving. In that case:
> > delete output dir and default.lst
> > make change
> > save
> > see no output dir/default.lst
> > get error when trying to run program - cannot find class
> > however dir and class files exist on the filesystem
> > F5 refresh
> > output dir and default.lst appear
> > can run program.
> > I'll look to see whether we can do this refresh programatically, but
> > wanted to share my findings so far.
> > Julie
> > AJDT Developement
> > Julie Waterhouse wrote:
> > > Chad, I've been trying to recreate your problem, but cannot. I tried all
> > > your scenarios, but they produced class files just fine for me.
> > > After seeing Andy's reply to your post about this in another thread, I
> > > also tried the following:
> > > Using eclipse with ajdt plugin level 1.1.1
> > > -create simple aspectJ project (one class, one aspect)
> > > -build
> > > -delete output folder & default.lst
> > > -rebuild
> > > ->produces class files correctly
> > > Then upgrade to plugin 1.1.2 via update site
> > > -restart
> > > -turn on incremental compile (I get the same results with or without this
> > > step)
> > > -delete output folder & default.lst
> > > -rebuild
> > > -get error (as Andy predicted): AspectJ Runtime error: bad version number
> > > found in
> > > D:\eclipse2.1\eclipse\plugins\org.aspectj.ajde_1.1.1\aspectj rt.jar
> > > expected 1.1rc2 found 1.1rc1. Please place a valid aspectjrt.jar on the
> > > classpath.
> > > -replaced aspectjrt.jar on the Java build path with correct 1.1.2 version
> > > -"OK" triggered empty Output folder to be created
> > > -rebuild all
> > > ->produces class files correctly
> > > Chad Woolley wrote:
> > > > George,
> > > > No, when I re-enable the aspectj nature, the aspectjrt.jar is added
back
> > > > to the classpath just fine. The problem is that no class files are
ever
> > > > generated when the aspectj nature is enabled.
> > > > Thanks for your response,
> > > > Chad
> > > > George Harley wrote:
> > > > > Hi Chad,
> > > > > Are you saying that when you remove the aspectj nature and then
> > re-enable
> > > > > it you are not seeing aspectjrt.jar in your project dependencies ?
> > > > > Best regards,
> > > > > George
> > > > > On Tue, 3 Jun 2003 03:11:46 +0000 (UTC), Chad Woolley
> > > > > <chad_woolley@choicehotels.com> wrote:
> > > > > > Additional info based on comment in previous thread:
> > > > > >
> > > > > > There is no aspectjrt.jar in my project. The only jar in my lib
> > folder
> > > > > > is
> > > > > > junit.jar, and this is the only jar (other than the JRE) on my
> > classpath
> > > > > > in the project properties.
> > > > > >
> > > > > > Chad Woolley wrote:
> > > > > >
> > > > > >> Hello,
> > > > > >
> > > > > >> I am still having the problem of the latest build not creating any
> > class
> > > > > >> files. This was mentioned in a previous thread, but since this
was
> > not
> > > > > >> mentioned in the "known AJDT bugs" just posted, I thought I would
> > bring
> > > > > >> it
> > > > > >> up again.
> > > > > >
> > > > > >> I am using AJDT dev build 1.1.3, installed via Eclipse
> > Install/Update,
> > > > > >> on
> > > > > >> eclipse 2.1.0.
> > > > > >
> > > > > >> Here is a detailed analysis of when the bug occurs and how to
> > recreate
> > > > > >> it:
> > > > > >
> > > > > >
> > > > > >> ===========================================
> > > > > >
> > > > > >
> > > > > >> Scenario 0 ("Control Group" - no aspectj):
> > > > > >> - Removed aspectj nature
> > > > > >> - Deleted default output folder
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default output folder and classes are all successfully created
> > > > > >> - everything works fine (but is compiled without aspects)
> > > > > >
> > > > > >> ---------------------------------------
> > > > > >
> > > > > >> Scenarios 1-4 common setup preparation: - no other projects open
in
> > > > > >> workspace
> > > > > >> - suppress automatic builds SELECTED in global aspectj preference
> > > > > >> - use AspectJ aware version of outline view DESELECTED in global
> > aspectj
> > > > > >> preference
> > > > > >> - all input fields on AspectJ Compiler project settings empty
> (except
> > > > > >> incremental checkbox)
> > > > > >> - enabled aspectj nature
> > > > > >> - delete default.lst file
> > > > > >
> > > > > >> Scenario 1:
> > > > > >> - delete default output folder through eclipse resource
perspective
> > > > > >> - incremental compile DESELECTED
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default.lst is created
> > > > > >> - NO default output folder or classes are created
> > > > > >
> > > > > >> Scenario 2:
> > > > > >> - delete default output folder through eclipse resource
perspective
> > > > > >> - incremental compile SELECTED
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default.lst is created
> > > > > >> - NO default output folder or classes are created
> > > > > >
> > > > > >> Scenario 3:
> > > > > >> - delete default output folder through eclipse resource
perspective
> > > > > >> - manually create default output folder through eclipse resource
> > > > > >> perspective
> > > > > >> - incremental compile DESELECTED
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default.lst is created
> > > > > >> - NO classes are created
> > > > > >
> > > > > >> Scenario 4:
> > > > > >> - delete default output folder through eclipse resource
perspective
> > > > > >> - manually create default output folder through eclipse resource
> > > > > >> perspective
> > > > > >> - incremental compile SELECTED
> > > > > >> - Select Project -> Rebuild All
> > > > > >> - default.lst is created
> > > > > >> - NO classes are created
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > --
> > > > > George
|
|
|
Goto Forum:
Current Time: Fri Apr 19 21:43:06 GMT 2024
Powered by FUDForum. Page generated in 0.03865 seconds |
] 
Search
Help
Register
Login
Home
