Community
Participate
Working Groups
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.
I'll look at this whilst considering what changes to make wrt. the larger ajdt. core extension for AJDT building.
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?
We discussed this on the call today. Consensus is that everything should indeed be relative. I will fix....
Yup the change to make it relative to the .lst file sounds right. It's too inconsistent and confusing otherwise.
Fix committed to tree. Will close bug once this is available in a build.
Fix now available in the latest jar from the download page.
Fix released as part of AspectJ 1.2.1