|
||||||||
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 ... 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)
The classpath length is not a problem for maven but for m2e (eclipse) which launches any class in the workspace with a "java -cp". Then with a large classpath, our test units and main class fail in eclipse. It's not the topic here but it's an illustration of our dependencies list size.