<dependent-module deploy-path="/WEB-INF/lib" handle="module:/classpath/lib/C:/Users/erizzo/.gradle/caches/modules-2/files-2.1/org.springframework.hateoas/spring-hateoas/0.8.0.RELEASE/819c25e1ff12b7fca483d76b4e7d20221f621fcd/spring-hateoas-0.8.0.RELEASE.jar">
On 1/28/2014 11:16 AM, I have done a minimal amount of work with Gradle based Dynamic Web
Projects. In a simple example, I have one that doesn't yet include any
jar dependencies. However, I do find in the project properties Java
Build Path Libraries tab, there is a Gradle Dependencies classpath
container. Under it is a "Publish/export dependency: /WEB-INF/lib"
entry. This means any jar in the Gradle Dependencies classpath
container will be copied to the WEB-INF/lib folder of the exported or
published project. If I examine the project properties Deployment
Assembly page, I see Gradle Dependencies listed with a deploy path of
WEB-INF/lib. This entry is not editable here because it is being
declared in the .classpath file. It's just visible here.
Given the above, and assuming your project is a Dynamic Web project and
not an EAR project, I don't know why Gradle would be creating direct jar
dependencies in the org.eclipse.wst.common.component file instead of
relying on the Gradle Dependencies classpath container. Is your project
also showing the Gradle Dependencies classpath container. And if so,
does it contain duplicates of the jars you find listed in the
org.eclipse.wst.common.component file? I would think that any
duplicates could be removed from the org.eclipse.wst.common.component file.
Cheers,
Larry
<attributes> <attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/> </attributes>