|Re: [aspectj-users] bug-46665 : Output folder for source folder not utilized|
Matt, I've lost my Eclipse bugzilla credentials, so I cannot do it for now. However, I am attaching to this email a very small project that fails to compile the classes to different outputs.
The test is done inside Eclipse 3.2, with AJDT 188.8.131.52610061303 (one of the latest).
Please check the .classpath and .project to see that the description of the project is correct, and than try to compile and check the output directories. Everything goes to build/classes (the default one).
./alex -- .w( the_mindstorm )p.
If you can't get this working, please raise a bug and attach a testcase.
On 30/09/06, Alexandru Popescu <the.mindstorm.mailinglist@xxxxxxxxx> wrote: > Hi! > > I didn't know this bug was fixed, but I am trying it now with one of > the latest builds (184.108.40.206609271031 with Eclipse 3.2) and it is not > working correctly: > > Some more details: > I have 2 source folders: src/java and test/java having set a default > output build/classes and the 2nd one a custom output: > buid/test-classes. > > I have even tried to redefine all of them, but this hasn't helped. > > ./alex > -- > .w( the_mindstorm )p. > > > > On 9/1/06, Barry Kaplan <groups1@xxxxxxxxxxx> wrote: > > > > Ok Matt. I hope it doesn't fix itself when I create a standalone > > project.... > > > > -barry > > > > Matt Chapman wrote: > > Hi Barry, > > > > We have a test for this functionality which is still passing. So there must > > be something specific to your project or environment which is causing this > > problem. Could you raise a bug, and attach a test project for it? > > > > Regards, > > > > Matt. > > > > > > On 30/08/06, Barry Kaplan <groups1@xxxxxxxxxxx> wrote: > > > This bug has been marked as fixed sometime ago. Yet I cannot get any > > > AspectJ project to compile to a directory other than the default. Even > > > if I override the output folder for every source folder, all classes > > > (and other output) go to the default. > > > > > > This has killed me after a project combing-refactoring, where the > > > resulting project had a META-INF/aop.xml in both the production source > > > folder and the test source folder. The result being that only one > > > aop.xml survives the compile, causing all kinds of errors. > > > > > > Is anybody else actually using this feature in ajdt > > > 220.127.116.1160629124300 or better? > > > > > > -barry > > > _______________________________________________ > > > aspectj-users mailing list > > > aspectj-users@xxxxxxxxxxx > > > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > > > > > > ________________________________ > > > > _______________________________________________ > > aspectj-users mailing list > > aspectj-users@xxxxxxxxxxx > > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > > > > > > > _______________________________________________ > > aspectj-users mailing list > > aspectj-users@xxxxxxxxxxx > > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > > > > > > _______________________________________________ > aspectj-users mailing list > aspectj-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/aspectj-users > _______________________________________________ aspectj-users mailing list aspectj-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/aspectj-users
Description: Zip archive