Home » Language IDEs » AspectJ » Problem in default.lst "Use relative paths only, omitting..."
| Problem in default.lst "Use relative paths only, omitting..." [message #30125] |
Wed, 28 January 2004 18:13  |
Eclipse User |
|
|
|
I tried to "split" a working AspectJ project into 2 projects (one an
AspectJ
project holding just the aspect classes, and the other a regular Java
project
with the "regular" classes). I then tried many different ways to link the
files from one project to the other, when I finally gave up and just
put them back together again. However, in Removing Aspect Nature from
my original project (making it a Java project), then reconverting back
into an AspectJ project, my default.lst build file got messed up and I
cannot get rid of it, nor edit it to correct it!
I am using Eclipse 2.1.2, build id 200311030802 on Win2000
AJDT version 1.1.0, build id 1.1.1
The default.lst file shows up in config editor with my hierarchy of
classes unchecked, followed by a list of checkboxes of ALL my classes
saying "Use relative paths only, omitting: D:/projectname/.....java"
Even if I check the packages in the hierarchy view, the Use relative
paths overrides them, and the aspects never get compiled in. All the
checkboxes show a red "X" on them as well.
I've tried removing Aspect Nature, deleting *.lst files, deleting the
*.ajsym files, and converting back "fresh" to an AspectJ project. The
generated
build files ALL come up the same way.
Any ideas how to fix this??
KL
|
|
| |
| Re: Problem in default.lst "Use relative paths only, omitting..." [message #31002 is a reply to message #30161] |
Thu, 12 February 2004 16:56  |
| Eclipse User |
|
|
|
I'll second that!
Key problem: if you have multiple .lst files (as I do) then add new classes
to the project source tree, you have to *manually* update all of the .lst
files!!
An exlusionary filter might be better (build everything exception this list)
FAR better would be ant's support for filesets and path-like structures.
Should not be that hard as eclipse is ant-based.
"KL Simunich" <simunich@dis.anl.gov> wrote in message
news:bvdqjl$kov$1@eclipse.org...
> Well, it appears I got things corrected. I closed/opened
> perspectives, closed/opened projects, restarted eclipse,
> then created a new workspace. One of those things worked...
>
> Anyway, I'd like to put my $.02 in for getting rid of the
> *.lst files for building. Perhaps using the source code
> filtering on project properties could be utilized. OR better
> yet, incremental compilation support!
>
> Onward,
> KL
>
|
|
|
| Re: Problem in default.lst "Use relative paths only, omitting..." [message #574510 is a reply to message #30125] |
Fri, 30 January 2004 09:44 |
| Eclipse User |
|
|
|
Well, it appears I got things corrected. I closed/opened
perspectives, closed/opened projects, restarted eclipse,
then created a new workspace. One of those things worked...
Anyway, I'd like to put my $.02 in for getting rid of the
*.lst files for building. Perhaps using the source code
filtering on project properties could be utilized. OR better
yet, incremental compilation support!
Onward,
KL
|
|
|
| Re: Problem in default.lst "Use relative paths only, omitting..." [message #575398 is a reply to message #30161] |
Thu, 12 February 2004 16:56 |
| Eclipse User |
|
|
|
I'll second that!
Key problem: if you have multiple .lst files (as I do) then add new classes
to the project source tree, you have to *manually* update all of the .lst
files!!
An exlusionary filter might be better (build everything exception this list)
FAR better would be ant's support for filesets and path-like structures.
Should not be that hard as eclipse is ant-based.
"KL Simunich" <simunich@dis.anl.gov> wrote in message
news:bvdqjl$kov$1@eclipse.org...
> Well, it appears I got things corrected. I closed/opened
> perspectives, closed/opened projects, restarted eclipse,
> then created a new workspace. One of those things worked...
>
> Anyway, I'd like to put my $.02 in for getting rid of the
> *.lst files for building. Perhaps using the source code
> filtering on project properties could be utilized. OR better
> yet, incremental compilation support!
>
> Onward,
> KL
>
|
|
|
Goto Forum:
Current Time: Sat May 10 04:56:55 EDT 2025
Powered by FUDForum. Page generated in 0.02782 seconds |
Home