Re: [aspectwerkz-dev] important patch for AnnotationCTask
the_mindstorm <[email protected]> Wed, 03 Nov 2004 17:26:37 +0200
| Newsgroups | gmane.comp.java.aspectwerkz.devel |
|---|---|
| Message-ID | <[email protected]> |
Quote [Alexandre Vasseur]: > Thanks myp > > Indeed it seems to have some weird effect when we define a task with > Ant and when this ones executes. > > I could fix the issue by removing a ClassLoader.getSystemClassLoader() > and using a someAWClass.class.getClassLoader() instead. > I suggest that a better solution is that we have used in AspectWerkzC - AspectWerkzCTask, and I mean to pass around the ClassLoader. > I still don't get why we don't see the issue in AW build.xml. As I commented yesterday, I think that the log annotation isn't used in fact and this is why the build works. I will dig into it and come back. :the_mindstorm > > Alex > > > On Tue, 02 Nov 2004 16:38:07 +0200, the_mindstorm > <[email protected]> wrote: >> The test: >> >> Attached is the test failing. >> Custom annotation: net.noco.unit.aw.ContextAnnotationProxy >> Class under test: net.noco.unit.SimpleTestImpl >> >> Before running pls follow the indications in README. >> >> To test run: >> >> [old mode => passing] >> ant aw:annotation:direct run:test >> >> [task mode => failing with ClassCastException] >> ant aw:annotation:task run:test >> >> After applying the patch both will run. >> >> I wait with interest your opinions. >> >> :the_mindstorm >> >> >> >