So, looking into this more (and having created a simple example project to
demonstrate it), it looks like the the aspectj plugin is compiling things
correctly, its just that the tests are being run from the incorrect place.
So, for example, the output of the aspectj compilation goes into
target/classes/...
but the tests run from a folder called
target/test-classes/...
which has the compiled test code, but not the aspectj compiled code. So, if
a test is affected by an aspect, it isn't in this folder.
diyfiesta wrote:
>
> Hi,
>
> Thanks for the note, I tried this but still don't have any luck, for
> example, I'm using the convention main/src/java and main/src/test for my
> source trees, so adding an src/aspectj folder doesn't really fit in, if I
> add it to main/src/aspectj, I get the same problem (and just for
> completness, setting it to src/aspectj causes is the same!).
>
> From the plugin's homepage, I didn't get the impression that setting the
> soruce directiory to src/aspectj was a requirement more of an example, and
> you should be able to set this to whatever your folder is. Is this not the
> case?
>
> I think I'll have a go at creating a simple test project that demonstrates
> the problem, see if I can get some feedback.
>
> Any other ideas?
>
> Cheers
>
>
> Alexandre Touret wrote:
>>
>> Hello,
>> There are 2 builds : the classes and test classes.
>> If you specify the aspectsourcedirectory in src/java, aspectj doesn t
>> parse any file in src/test. Its the default behaviour
>> I can suggest you to put all the aspects file have in
>> ${maven.src.dir}/aspectj (as described in the plugin homepage). I
>> suppose this directory is accessible in both the build classpaths and
>> test classpath.
>>
>> Hope this helps.
>> Alexandre
>>
>> Toby Weston wrote:
>>> Hi Folks,
>>> [...]
>>> I've got my source code under main/src and the unit tests under
>>> main/test, however I can't get aspectj compiling both. I added this to
>>> my project.xml hoping it would pick up both, but it doesn't seem to,,,
>>>
>>> <aspectSourceDirectory>main/src/java</aspectSourceDirectory>
>>> <aspectSourceDirectory>main/test/java</aspectSourceDirectory>
>>>
>>> I'm kind of not confident I know the correct process, so may be doing
>>> something really silly. I was thinking that the pregoal for compile to
>>> run the aspectj compiler would apply my aspects to the code that they
>>> affect? After running this though, my unit tests confirm that the
>>> aspect isn't applied, and if I reverse engineer the test code, there
>>> is no aspect code in there (and there is if I do a normal eclipse
>>> aspectj compile).
>>>
>>> So, for some reason, its not applying my aspects to test code in the
>>> second source tree... :(
>>>
>>> Cheers,
>>> Toby
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/-M1--AspectJ-with-two-source-trees-%28main-src---main-test%29-tf2556159s177.html#a7319470
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
