|
Re: AJDT fiddling with the Java Build path? [message #41759 is a reply to message #41696] |
Mon, 04 October 2004 09:51 |
Eclipse User |
|
|
|
Originally posted by: hawkinsh.uk.ibm.com
Michael Moser wrote:
> I have a strange observation:
> apparently since I converted a former Java Project to an AspectJ
> project I noticed that "something" is fiddling with the build path
> (right click on project => Properties => Java Build Path) of that
> project:
> I repeatedly now observed that all project imports (second tab at the
> right "Projects") get unchecked and instead I get corresponding new
> entries on the "Libraries" tab pointing to <project>/build/classes.
> Who/which component is changing this and why?
> Michael
Hi Michael,
There has been a lot of discussion in the last few months about what type
of dependencies there should be between projects when an AJ project is
involved. The problem is all because when Java projects depend on AJ
projects, the Java builder decides that it's not worth building the java
project because it doesn't understand the AJ project.
We were advised not to use project dependencies, and instead replace them
with class folder dependencies. This is the behaviour you're seeing (and
is in AJDT 1.1.11 and 1.1.12). Unfortunately, this leads to a number of
special cases which are broken when the dependencies are class folder, but
work when you have project dependencies. We've had various discussions
about this and have decided to revert to keeping the dependencies as
defined by the user. The remaining failing scenario can be found in the
following bug report:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=73435
The dev releases of AJDT remove the work done to convert to class folder
dependencies, and the lastest version can be found at the following update
site:
http://download.eclipse.org/technology/ajdt/30/dev/update
This will therefore be included in the 1.2 M1 release of AJDT.
Hope this helps,
Thanks, Helen
|
|
|
|
Re: AJDT fiddling with the Java Build path? [message #583623 is a reply to message #41696] |
Mon, 04 October 2004 09:51 |
Eclipse User |
|
|
|
Originally posted by: hawkinsh.uk.ibm.com
Michael Moser wrote:
> I have a strange observation:
> apparently since I converted a former Java Project to an AspectJ
> project I noticed that "something" is fiddling with the build path
> (right click on project => Properties => Java Build Path) of that
> project:
> I repeatedly now observed that all project imports (second tab at the
> right "Projects") get unchecked and instead I get corresponding new
> entries on the "Libraries" tab pointing to <project>/build/classes.
> Who/which component is changing this and why?
> Michael
Hi Michael,
There has been a lot of discussion in the last few months about what type
of dependencies there should be between projects when an AJ project is
involved. The problem is all because when Java projects depend on AJ
projects, the Java builder decides that it's not worth building the java
project because it doesn't understand the AJ project.
We were advised not to use project dependencies, and instead replace them
with class folder dependencies. This is the behaviour you're seeing (and
is in AJDT 1.1.11 and 1.1.12). Unfortunately, this leads to a number of
special cases which are broken when the dependencies are class folder, but
work when you have project dependencies. We've had various discussions
about this and have decided to revert to keeping the dependencies as
defined by the user. The remaining failing scenario can be found in the
following bug report:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=73435
The dev releases of AJDT remove the work done to convert to class folder
dependencies, and the lastest version can be found at the following update
site:
http://download.eclipse.org/technology/ajdt/30/dev/update
This will therefore be included in the 1.2 M1 release of AJDT.
Hope this helps,
Thanks, Helen
|
|
|
|
Powered by
FUDForum. Page generated in 0.01737 seconds