Bug 42573

Summary:	.lst file entries not resolved relative to list file: {boot}classpath, extdirs,
Product:	[Tools] AspectJ	Reporter:	Wes Isberg <wes>
Component:	Compiler	Assignee:	Adrian Colyer <adrian.colyer>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	mik.kersten
Version:	1.1.0
Target Milestone:	1.2.1
Hardware:	PC
OS:	Windows NT
Whiteboard:

Description Wes Isberg

2003-09-04 18:40:22 EDT

My -classpath entry in a config/.lst file was resolved relative to the working
directory rather than to the config/.lst file.  BuildArgParser.java looks like
this would also be true for bootclasspath and extdirs, but not for injars,
aspectpath, or sourceroots.

Comment 1 Adrian Colyer

2004-01-29 11:29:47 EST

I'll look at this whilst considering what changes to make wrt. the larger ajdt.
core extension for AJDT building.

Comment 2 Adrian Colyer

2004-08-05 11:38:47 EDT

Hmmm... it looks to me like any relative file or path specified in a .lst file 
(be it source file name, entry in any path - even injars etc..) is resolved 
relative to the working directory, not to the config file. 

I could change it (for everything) to make this behaviour relative - which 
should be backwards compatible because any relative path in such an .lst file 
now is either (a) broken, or (b) in a .lst file that is in the working 
directory.

Should I switch it?

Comment 3 Adrian Colyer

2004-08-05 12:27:48 EDT

We discussed this on the call today. Consensus is that everything should indeed 
be relative. I will fix....

Comment 4 Mik Kersten

2004-08-05 12:29:52 EDT

Yup the change to make it relative to the .lst file sounds right.  It's too 
inconsistent and confusing otherwise.

Comment 5 Adrian Colyer

2004-08-05 13:44:50 EDT

Fix committed to tree. Will close bug once this is available in a build.

Comment 6 Adrian Colyer

2004-08-06 08:26:40 EDT

Fix now available in the latest jar from the download page.

Comment 7 Adrian Colyer

2004-10-21 04:30:54 EDT

Fix released as part of AspectJ 1.2.1