|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... JIRA
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... JIRA
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... JIRA
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... JIRA
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... Thomas Mortagne (JIRA)
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... Thomas Mortagne (JIRA)
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... JIRA
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... Thomas Mortagne (JIRA)
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... Thomas Mortagne (JIRA)
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... Thomas Mortagne (JIRA)
- [mojo-dev] [jira] (MASPECTJ-125) Issue with <wea... JIRA

True; upgrading the default AspectJ version used by the aspectj-maven-plugin
is slated for the 1.6 release. However, in the meantime you could upgrade the
underlying runtime by adding some configuration for the plugin itself.
Please refer to MASPECTJ-126 for an example (I pasted a comment where upgrading
the AspectJ dependency for the a-m-p is illustrated into that issue).