Incorrect classpath handling is incompatible with Maven 2.1.0+

saiddfhi / gwt-maven

Automatically exported from code.google.com/p/gwt-maven

0 stars 0 forks source link

Incorrect classpath handling is incompatible with Maven 2.1.0+ #200

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Maven 2.1.0 will now ensure that all source artifacts are recognised as such, 
and so the 
"addedToClasspath" flag is correctly set to false. This means that 
getCompileClasspathElements no 
longer returns them, causing failures under gwt:compile (see for example [1]).

Attached is a patch to correct the issue.

[1] http://markmail.org/message/mpcuj57ncdfbdvqt

Original issue reported on code.google.com by brett.po...@gmail.com on 20 Mar 2009 at 1:21

Attachments:

patch

GoogleCodeExporter commented 9 years ago

Original comment by keber...@gmail.com on 22 Mar 2009 at 8:20

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Committed revision 961

Original comment by keber...@gmail.com on 22 Mar 2009 at 8:22

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

In 2.0-RC1.

Original comment by charlie....@gmail.com on 3 Apr 2009 at 1:16

Added labels: Milestone-Release2.0-RC1