[GRADLE-1422] Improper .classpath generation causes WTP to deploy all of the war's dependant project's dependencies Created: 05/Mar/11 Updated: 05/Dec/14 Resolved: 05/Dec/14
|Reporter:||Rob Winch||Assignee:||Radim Kubacki|
Every entry classpathentry in the .classpath that is a Library contains an attribute org.eclipse.jst.component.dependency. This means that test and provided dependencies of projects that the war depends on are also included in the war. In some cases this can cause the application to fail to start. For example, when the wrong jsp-api version is included JSPs fail to compile. I have attached a sample project to illustrate the issue. I have also attached init.gradle that provides a workaround for anyone else experiencing this issue. Below the actual .classpath file and the expected .classpath files are displayed.
|Comment by Magnus Heino [ 13/Nov/12 ]|
This makes gradle + eclipse wtp pretty useless for me :-P
Is there an updated workaround available for Gradle 1.2? Thanks.
|Comment by Radim Kubacki [ 05/Dec/14 ]|
Fixed provided by Andreas Schmid. Thanks for the contribution.