[GRADLE-1990] Jetty plugin only searches sub-project dependencies and Gradle jars for TLD files Created: 09/Dec/11  Updated: 16/Jan/17  Resolved: 16/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-5
Fix Version/s: None

Type: Bug
Reporter: Stanford S. Guillory Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

I have the following dependencies in a war project:

compile project(':utility')
compile project(':web-paths')
runtime project(':features')

compile group: 'org.springframework', name: 'spring-webmvc', version: "${springVersion}"

The spring-webmvc has two tld files in it that describe tags my JSPs use. During startup, only the jars for the project dependences and the gradle jars are searched for tld files. The spring-mvc jar is not searched as shown in the log snippet below:

10:10:31.094 [DEBUG] [org.mortbay.log] Configuring web-jetty.xml
10:10:31.095 [DEBUG] [org.mortbay.log] TLD search of file:/home/developer/work/commerce-git/commerce-project/features/build/libs/features-5.11.0-SNAPSHOT.jar
10:10:31.096 [DEBUG] [org.mortbay.log] TLD search of file:/home/developer/work/commerce-git/commerce-project/utility/build/libs/utility-5.11.0-SNAPSHOT.jar
10:10:31.101 [DEBUG] [org.mortbay.log] TLD search of file:/home/developer/work/commerce-git/commerce-project/web-paths/build/libs/web-paths-5.11.0-SNAPSHOT.jar
10:10:31.102 [DEBUG] [org.mortbay.log] TLD search of file:/opt/gradle-1.0-milestone-5/lib/plugins/bsh-2.0b4.jar
10:10:31.102 [DEBUG] [org.mortbay.log] TLD search of file:/opt/gradle-1.0-milestone-5/lib/plugins/gradle-plugins-1.0-milestone-5.jar
10:10:31.104 [DEBUG] [org.mortbay.log] TLD search of file:/opt/gradle-1.0-milestone-5/lib/asm-all-3.3.1.jar
1

 Comments   
Comment by Assaf Berg [ 16/Jan/12 ]

Is there a workaround?

Comment by Stanford S. Guillory [ 16/Jan/12 ]

Currently the only one I am aware of is to switch to the Tomcat plugin. Since we actually use Tomcat in production, this option wasn't too hard to accept, and the switch was a lot easier than with Maven where we never did get the Tomcat plugin working quite right with our app.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 16/Jan/17 ]

The Jetty plugin has been deprecated and is scheduled to be removed with Gradle 4.0. We are not going to work on this issue anymore.

Generated at Wed Jun 30 12:09:49 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.