|
||||||||
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-112) Allow modules not in ... Erwann Feat (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Erwann Feat (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Erwann Feat (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Erwann Feat (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Zsolt Szalai (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Zsolt Szalai (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Zsolt Szalai (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... JIRA
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Erwann Feat (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... JIRA
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... JIRA
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... JIRA
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Erwann Feat (JIRA)
- [mojo-dev] [jira] (MASPECTJ-112) Allow modules not in ... Erwann Feat (JIRA)
To alleviate any problems related to classpath length and Windows OS, we could
implement and use the same mechanics WRT classpath as the surefire plugin does;
i.e. create a temporary JAR where we synthesize the classpath within the META-INF/MANIFEST.MF
file.
This approach pretty much removes any classpath length problems.
However, I would recommend us doing that in the 2.0 release, when I intend to
simplify the internals of the AspectJ Maven Plugin, to align it with accepted
Maven best practises.
Moreover, 2.0 is not a distant-future release.