|
||||||||
|
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] (MGWT-369) compileSourcesArti... Jason Pell (JIRA)
- [mojo-dev] [jira] (MGWT-369) compileSource... Jason Pell (JIRA)
- [mojo-dev] [jira] (MGWT-369) compileSource... Jason Pell (JIRA)
- [mojo-dev] [jira] (MGWT-369) compileSource... Jason Pell (JIRA)
- [mojo-dev] [jira] (MGWT-369) compileSource... Samuele Arcidiacono (JIRA)

I managed to solve the problem by including the various projects sources jars using the classifier sources and scope test. So I was going to add a new mojo to gwt-maven-plugin to populate the test class path of the project with the compile Source artifacts list so that surefire would pick them up also.
I will raise a pull request for this. I also added the ability to specify a wild card for the compile source artifacts which I will submit as part of the PR.