Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AJDT » AspectJ project dependent on normal java project
AspectJ project dependent on normal java project [message #57185] Tue, 04 October 2005 14:33 Go to next message
Jason King is currently offline Jason King
Messages: 12
Registered: July 2009
Junior Member
Hi,

Java Version: 1.5.0_05 (win xpsp2)
Eclipse: 3.2M2
AJDT: 1.3.020050923175100

I'm trying to create an AspectJ project to monitor the coding standards on
serveral "vanilla" java projects.

I created my AspectJ project, and added my Java projects to the build path
as dependent projects (and exported the required entries). I put the
output path (bin) in the AspectJ inpath.

The Cross References View and Problems Tab don't seem to properly report
the source file where my advice applies in the java project.

e.g.
In the cross references view, the advice is reported as "binary aspect:
File.java" however I cannot click on it to take me to the location as I
can normally.

Also, the number of errors/warnings in the problems tab keeps on
increasing each time I touch any java file and save it (the number doubles
each time).

I've tried changing the aspect-J compiler options, (incremental etc) but
this does not help. The only way to reset the list of reported
errors/problems is to clean all the projects.

Any suggestions on how to fix this problem would be really helpful. I can
log a bug if you think this a valid problem.

Thanks
Jason King
Re: AspectJ project dependent on normal java project [message #57212 is a reply to message #57185] Tue, 04 October 2005 15:12 Go to previous messageGo to next message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Hi Jason,

The first issue is unfortunately a known limitation - by using inpath it
only knows about the class files and isn't (yet) smart enough to figure
out when the source is in the workspace, and so link to it. One
alternative is to create linked source folders in the AspectJ project, so
then it thinks all the source code is local to the AspectJ project.
Although you might sometimes get issues with there appearing to be two
versions of each source file.

The second issue, the ever-increasing errors/warnings is clearly a bug -
no doubt specific to 3.2M2, as it doesn't seem to do that on 3.1. Please
raise a bug for this.

Regards,

Matt.

Jason King wrote:

> Hi,

> Java Version: 1.5.0_05 (win xpsp2)
> Eclipse: 3.2M2
> AJDT: 1.3.020050923175100

> I'm trying to create an AspectJ project to monitor the coding standards on
> serveral "vanilla" java projects.

> I created my AspectJ project, and added my Java projects to the build path
> as dependent projects (and exported the required entries). I put the
> output path (bin) in the AspectJ inpath.

> The Cross References View and Problems Tab don't seem to properly report
> the source file where my advice applies in the java project.

> e.g.
> In the cross references view, the advice is reported as "binary aspect:
> File.java" however I cannot click on it to take me to the location as I
> can normally.

> Also, the number of errors/warnings in the problems tab keeps on
> increasing each time I touch any java file and save it (the number doubles
> each time).

> I've tried changing the aspect-J compiler options, (incremental etc) but
> this does not help. The only way to reset the list of reported
> errors/problems is to clean all the projects.

> Any suggestions on how to fix this problem would be really helpful. I can
> log a bug if you think this a valid problem.

> Thanks
> Jason King
Re: AspectJ project dependent on normal java project [message #57290 is a reply to message #57212] Thu, 06 October 2005 11:30 Go to previous message
Jason King is currently offline Jason King
Messages: 12
Registered: July 2009
Junior Member
Hi Matt,

Thank for your response. I'll log a bug for my second issue.

I looked into creating linked source folders to achieve the result I
wanted, however this doesn't really work for me because of the following:

o- Each user in our team has their eclipse workspace installed in a
different location. Some on windows and some on linux. The linked source
folders are absolute paths so it makes sharing the aspectJ project with
linked source folders difficult.

o- I have to import all of the project dependencies into the new project
(e.g. jarfiles, other dependent projects, other resource directories).
This is a bit brittle as I then need to keep both projects in-sync.

My aim is to demonstrate how Aspects (and AJDT) can be used within our
software projects without having to force those projects to convert to
AspectJ on day 1 (not an approved compiler :-(. Once I have demonstrated
some benefits it is my hope to get some groundswell and the indivdiual
projects could be converted to use Aspect libraries themselves. That will
be a longer road to travel.

Thanks again
Jason King
Re: AspectJ project dependent on normal java project [message #590282 is a reply to message #57185] Tue, 04 October 2005 15:12 Go to previous message
Matt Chapman is currently offline Matt Chapman
Messages: 429
Registered: July 2009
Senior Member
Hi Jason,

The first issue is unfortunately a known limitation - by using inpath it
only knows about the class files and isn't (yet) smart enough to figure
out when the source is in the workspace, and so link to it. One
alternative is to create linked source folders in the AspectJ project, so
then it thinks all the source code is local to the AspectJ project.
Although you might sometimes get issues with there appearing to be two
versions of each source file.

The second issue, the ever-increasing errors/warnings is clearly a bug -
no doubt specific to 3.2M2, as it doesn't seem to do that on 3.1. Please
raise a bug for this.

Regards,

Matt.

Jason King wrote:

> Hi,

> Java Version: 1.5.0_05 (win xpsp2)
> Eclipse: 3.2M2
> AJDT: 1.3.020050923175100

> I'm trying to create an AspectJ project to monitor the coding standards on
> serveral "vanilla" java projects.

> I created my AspectJ project, and added my Java projects to the build path
> as dependent projects (and exported the required entries). I put the
> output path (bin) in the AspectJ inpath.

> The Cross References View and Problems Tab don't seem to properly report
> the source file where my advice applies in the java project.

> e.g.
> In the cross references view, the advice is reported as "binary aspect:
> File.java" however I cannot click on it to take me to the location as I
> can normally.

> Also, the number of errors/warnings in the problems tab keeps on
> increasing each time I touch any java file and save it (the number doubles
> each time).

> I've tried changing the aspect-J compiler options, (incremental etc) but
> this does not help. The only way to reset the list of reported
> errors/problems is to clean all the projects.

> Any suggestions on how to fix this problem would be really helpful. I can
> log a bug if you think this a valid problem.

> Thanks
> Jason King
Re: AspectJ project dependent on normal java project [message #590324 is a reply to message #57212] Thu, 06 October 2005 11:30 Go to previous message
Jason King is currently offline Jason King
Messages: 12
Registered: July 2009
Junior Member
Hi Matt,

Thank for your response. I'll log a bug for my second issue.

I looked into creating linked source folders to achieve the result I
wanted, however this doesn't really work for me because of the following:

o- Each user in our team has their eclipse workspace installed in a
different location. Some on windows and some on linux. The linked source
folders are absolute paths so it makes sharing the aspectJ project with
linked source folders difficult.

o- I have to import all of the project dependencies into the new project
(e.g. jarfiles, other dependent projects, other resource directories).
This is a bit brittle as I then need to keep both projects in-sync.

My aim is to demonstrate how Aspects (and AJDT) can be used within our
software projects without having to force those projects to convert to
AspectJ on day 1 (not an approved compiler :-(. Once I have demonstrated
some benefits it is my hope to get some groundswell and the indivdiual
projects could be converted to use Aspect libraries themselves. That will
be a longer road to travel.

Thanks again
Jason King
Previous Topic:load time weaving with existing servlet
Next Topic:Changing the class hierarchy
Goto Forum:
  


Current Time: Sat Sep 20 08:14:43 GMT 2014

Powered by FUDForum. Page generated in 0.08893 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software