|
||||||||
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-109) Weaving partially ... Bruce Edge (JIRA)
- [mojo-dev] [jira] (MASPECTJ-109) Weaving parti... Nicolas Daniels (JIRA)
- [mojo-dev] [jira] (MASPECTJ-109) Weaving parti... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MASPECTJ-109) Weaving parti... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MASPECTJ-109) Weaving parti... JIRA
- [mojo-dev] [jira] (MASPECTJ-109) Weaving parti... JIRA
I'm having the exact same problem with 1.4. Is this still broken 8 months later?
It's completely inconsistent. Randomly changing irrelevant details affects the output. For example, changing the jenkins job name that builds the project changes which jars are missing aspects.
I've re-hosted the build env to multiple different environments with no consistent results. This is a 'very bad thing' given that it makes the output from all builds inconsistent and suspect.