[
http://jira.codehaus.org/browse/MOJO-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93827
]
Kaare Nilsen commented on MOJO-620:
-----------------------------------
hmm.. tricky
There would be difficult for me figuring out if something has changed in the
aspect library or in the jar to weave for that sake, but when you mention it
this could also explain some strange behaviour in my own project, forcing me to
do a clean install sometimes :)
But one thought come to mind, would it be ok with a forceCompile flag to be set
eighter from the CLI or the pom ?
> compilation skipped when all aspects and classes are external
> -------------------------------------------------------------
>
> Key: MOJO-620
> URL: http://jira.codehaus.org/browse/MOJO-620
> Project: Mojo
> Issue Type: Bug
> Components: aspectj
> Environment: Affects versions: 1.0-beta-2,
> 1.0-beta-4-20060921.212218-1
> Reporter: Ken Geis
>
> I am trying to weave a jar with an aspect library. There are no aspects or
> classes in the project. The plugin exits without weaving the jar. If I run
> mvn -X, I get this:
> [DEBUG] No sources found skipping aspectJ compile
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
