Home » Language IDEs » AspectJ » Some other strange compile problems with AJDT 1.1.2
| Some other strange compile problems with AJDT 1.1.2 [message #21249] |
Wed, 14 May 2003 10:41  |
Eclipse User |
|
|
|
Originally posted by: eclipse.wingspread.fastmail.fm
I've noticed some other strange problems with AJDT 1.1.2 when compiling my
AspectJ project. I have the source code for my project in a 'src'
directory. I have incremental compilation turned on. When I save my
aspect definition I get compiler errors if errors exist. If I fix the
errors, and save, the errors go away. No problem. However, class files
are not always generated. For example, if I delete the class files that
got generated and then do a rebuild project, the class files are not
created. I have to make some change to my aspect file and save it before
the class files will be regenerated. Also, under no circumstances can I
get the AspectJ compiler to produce an 'outjar'. If I specify an outjar,
when I save my aspect, the compiler compiles, but nothing is generated.
There is no outjar file and there are no classes in my 'bin' directory
either. Am I misunderstading how to configure the AspectJ compiler?
Thanks.
--
James Howe
|
|
|
| Re: Some other strange compile problems with AJDT 1.1.2 [message #21501 is a reply to message #21249] |
Thu, 15 May 2003 03:14  |
| Eclipse User |
|
|
|
Originally posted by: clemas.hursley.ibm.com
James Howe wrote:
> I've noticed some other strange problems with AJDT 1.1.2 when compiling my
> AspectJ project. I have the source code for my project in a 'src'
> directory. I have incremental compilation turned on. When I save my
> aspect definition I get compiler errors if errors exist. If I fix the
> errors, and save, the errors go away. No problem. However, class files
> are not always generated. For example, if I delete the class files that
> got generated and then do a rebuild project, the class files are not
> created. I have to make some change to my aspect file and save it before
> the class files will be regenerated. Also, under no circumstances can I
> get the AspectJ compiler to produce an 'outjar'. If I specify an outjar,
> when I save my aspect, the compiler compiles, but nothing is generated.
> There is no outjar file and there are no classes in my 'bin' directory
> either. Am I misunderstading how to configure the AspectJ compiler?
Hi James,
You really are on the 'bleeding edge' :) I put AJDT 1.1.2 up yesterday
and its had a minimum of testing unfortunately - we don't have enough
sophisticated unit tests like AspectJ does. For the first part of your
problem, does everything 'recover' if you switch off incremental and do a
full project build? I have marked incremental as experimental because we
don't have incremental support in the structure view or task list.
For your second problem with outjar - what kind of value do you have in
outjar? A relative or absolute path - with or without drive letter?
Andy.
AJDT Development
|
|
| | |
| Re: Some other strange compile problems with AJDT 1.1.2 [message #22127 is a reply to message #21541] |
Fri, 16 May 2003 09:21 |
| Eclipse User |
|
|
|
Originally posted by: eclipse.wingspread.fastmail.fm
On Thu, 15 May 2003 07:37:51 +0000 (UTC), Andy Clement
<clemas@hursley.ibm.com> wrote:
> And yet another append from me - I just fixed this in 1.1.2 - outjar is
> working perfectly for me now. Unfortunately I haven't rev'd the minor
> version so you will need to reinstall 1.1.2 by deleting your current
> 1.1.2
> first - I hope that is OK? I put 1.1.2 up on the site so some of my
> co-developers could download it and test it before we announced it - but
> you are ahead of the game :)
>
The outjar stuff seems to be working in 1.1.2. There is still some
strangeness with incremental compilation. For example, if I erase the
generated class files, make a change to the aspect source code and save, no
new class files are generated. Also, if I change the source to
deliberately cause a compile error, the first time I save there is no
indication of the error. If I make a nop change (add/delete a space) and
resave, the error will be displayed. Similarly if I then fix my deliberate
error, the error still shows up until I make one more change and save
again. In all cases no new class files are generated until I rebuild the
project. The same is true with the outjar. No jar file is generated when
the file is saved, only when the project is rebuilt.
--
James Howe
|
|
| | | |
| Re: Some other strange compile problems with AJDT 1.1.2 [message #23486 is a reply to message #22127] |
Fri, 06 June 2003 14:59 |
| Eclipse User |
|
|
|
See my post of June 6 in response to Chad Woolley's other thread "Latest
build not creating any class files" -- I think it address your comment
about new class files not being generated.
Julie
AJDT Development
James Howe wrote:
> On Thu, 15 May 2003 07:37:51 +0000 (UTC), Andy Clement
> <clemas@hursley.ibm.com> wrote:
> > And yet another append from me - I just fixed this in 1.1.2 - outjar is
> > working perfectly for me now. Unfortunately I haven't rev'd the minor
> > version so you will need to reinstall 1.1.2 by deleting your current
> > 1.1.2
> > first - I hope that is OK? I put 1.1.2 up on the site so some of my
> > co-developers could download it and test it before we announced it - but
> > you are ahead of the game :)
> >
> The outjar stuff seems to be working in 1.1.2. There is still some
> strangeness with incremental compilation. For example, if I erase the
> generated class files, make a change to the aspect source code and save, no
> new class files are generated. Also, if I change the source to
> deliberately cause a compile error, the first time I save there is no
> indication of the error. If I make a nop change (add/delete a space) and
> resave, the error will be displayed. Similarly if I then fix my deliberate
> error, the error still shows up until I make one more change and save
> again. In all cases no new class files are generated until I rebuild the
> project. The same is true with the outjar. No jar file is generated when
> the file is saved, only when the project is rebuilt.
> --
> James Howe
|
|
|
| Re: Some other strange compile problems with AJDT 1.1.2 [message #566976 is a reply to message #21249] |
Thu, 15 May 2003 03:14 |
| Eclipse User |
|
|
|
James Howe wrote:
> I've noticed some other strange problems with AJDT 1.1.2 when compiling my
> AspectJ project. I have the source code for my project in a 'src'
> directory. I have incremental compilation turned on. When I save my
> aspect definition I get compiler errors if errors exist. If I fix the
> errors, and save, the errors go away. No problem. However, class files
> are not always generated. For example, if I delete the class files that
> got generated and then do a rebuild project, the class files are not
> created. I have to make some change to my aspect file and save it before
> the class files will be regenerated. Also, under no circumstances can I
> get the AspectJ compiler to produce an 'outjar'. If I specify an outjar,
> when I save my aspect, the compiler compiles, but nothing is generated.
> There is no outjar file and there are no classes in my 'bin' directory
> either. Am I misunderstading how to configure the AspectJ compiler?
Hi James,
You really are on the 'bleeding edge' :) I put AJDT 1.1.2 up yesterday
and its had a minimum of testing unfortunately - we don't have enough
sophisticated unit tests like AspectJ does. For the first part of your
problem, does everything 'recover' if you switch off incremental and do a
full project build? I have marked incremental as experimental because we
don't have incremental support in the structure view or task list.
For your second problem with outjar - what kind of value do you have in
outjar? A relative or absolute path - with or without drive letter?
Andy.
AJDT Development
|
|
| |
| Re: Some other strange compile problems with AJDT 1.1.2 [message #567039 is a reply to message #21519] |
Thu, 15 May 2003 03:37 |
| Eclipse User |
|
|
|
And yet another append from me - I just fixed this in 1.1.2 - outjar is
working perfectly for me now. Unfortunately I haven't rev'd the minor
version so you will need to reinstall 1.1.2 by deleting your current 1.1.2
first - I hope that is OK? I put 1.1.2 up on the site so some of my
co-developers could download it and test it before we announced it - but
you are ahead of the game :)
We really need some unit tests for this tool ...
cheers,
Andy.
|
|
|
| Re: Some other strange compile problems with AJDT 1.1.2 [message #567471 is a reply to message #21541] |
Fri, 16 May 2003 09:21 |
| Eclipse User |
|
|
|
On Thu, 15 May 2003 07:37:51 +0000 (UTC), Andy Clement
<clemas@hursley.ibm.com> wrote:
> And yet another append from me - I just fixed this in 1.1.2 - outjar is
> working perfectly for me now. Unfortunately I haven't rev'd the minor
> version so you will need to reinstall 1.1.2 by deleting your current
> 1.1.2
> first - I hope that is OK? I put 1.1.2 up on the site so some of my
> co-developers could download it and test it before we announced it - but
> you are ahead of the game :)
>
The outjar stuff seems to be working in 1.1.2. There is still some
strangeness with incremental compilation. For example, if I erase the
generated class files, make a change to the aspect source code and save, no
new class files are generated. Also, if I change the source to
deliberately cause a compile error, the first time I save there is no
indication of the error. If I make a nop change (add/delete a space) and
resave, the error will be displayed. Similarly if I then fix my deliberate
error, the error still shows up until I make one more change and save
again. In all cases no new class files are generated until I rebuild the
project. The same is true with the outjar. No jar file is generated when
the file is saved, only when the project is rebuilt.
--
James Howe
|
|
|
| Re: Some other strange compile problems with AJDT 1.1.2 [message #567705 is a reply to message #22127] |
Mon, 19 May 2003 15:46 |
| Eclipse User |
|
|
|
I have this same problem. However, it doesn't seem to matter whether I
have incremental compile turned on or off. In eclipse, if I delete the
class files, and then rebuild all, class files are never generated.
-- Chad Woolley
James Howe wrote:
> ...There is still some
> strangeness with incremental compilation. For example, if I erase the
> generated class files, make a change to the aspect source code and save, no
> new class files are generated...
> --
> James Howe
|
|
| |
| Re: Some other strange compile problems with AJDT 1.1.2 [message #567842 is a reply to message #22543] |
Fri, 30 May 2003 09:35 |
| Eclipse User |
|
|
|
Chad Woolley wrote:
> Here's some more info: If I make a brand-new, simple Aspect project, it
> seems to compile fine, incremental or otherwise. It only seems like my
> existing project has problems creating the class files.
I have seen problems with existing projects because of where they are
getting the necessary aspectjrt.jar from. By either starting a new
project, or removing and readding the aspectj nature it should attempt to
locate the right aspectjrt.jar. Where is your aspectjrt.jar - installed
as part of the JDK (in the ext directory) or is it represented as a
resource in the project?
Basically, in AJDT1.1.1 we added some logic to locate aspectjrt.jar and
add it as a project dependency - with the move to AJDT1.1.2, the location
it was using may no longer be valid. But I would have expected a proper
error when doing a compile - about a mismatch in aspectj levels - rather
than silently not building anything.
Andy.
AJDT Development
|
|
|
| Re: Some other strange compile problems with AJDT 1.1.2 [message #568676 is a reply to message #22127] |
Fri, 06 June 2003 14:59 |
| Eclipse User |
|
|
|
See my post of June 6 in response to Chad Woolley's other thread "Latest
build not creating any class files" -- I think it address your comment
about new class files not being generated.
Julie
AJDT Development
James Howe wrote:
> On Thu, 15 May 2003 07:37:51 +0000 (UTC), Andy Clement
> <clemas@hursley.ibm.com> wrote:
> > And yet another append from me - I just fixed this in 1.1.2 - outjar is
> > working perfectly for me now. Unfortunately I haven't rev'd the minor
> > version so you will need to reinstall 1.1.2 by deleting your current
> > 1.1.2
> > first - I hope that is OK? I put 1.1.2 up on the site so some of my
> > co-developers could download it and test it before we announced it - but
> > you are ahead of the game :)
> >
> The outjar stuff seems to be working in 1.1.2. There is still some
> strangeness with incremental compilation. For example, if I erase the
> generated class files, make a change to the aspect source code and save, no
> new class files are generated. Also, if I change the source to
> deliberately cause a compile error, the first time I save there is no
> indication of the error. If I make a nop change (add/delete a space) and
> resave, the error will be displayed. Similarly if I then fix my deliberate
> error, the error still shows up until I make one more change and save
> again. In all cases no new class files are generated until I rebuild the
> project. The same is true with the outjar. No jar file is generated when
> the file is saved, only when the project is rebuilt.
> --
> James Howe
|
|
|
Goto Forum:
Current Time: Tue Jul 22 13:04:18 EDT 2025
Powered by FUDForum. Page generated in 0.25709 seconds |
Home