[GRADLE-3151] filtering files added to WEB-INF Created: 21/Aug/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


I'm trying to filter out and rename some files from the classpath when creating a war:

war {
from "${project(':frontend').projectDir}/app"

filesMatching('*/') {
println "main filesMatching: $it"

webInf {
filesMatching('*/') {
println "webInf filesMatching: $it"

I see all the files coming from the `../frontend/app` directory being printed as expected, from both filesMatching blocks, but none of the files coming from the classpath is being printed. So I haven't found any way to remove (or rename) some files, coming from the classpath, from the war.

Is that expected? How can I filter files from the classpath?

BTW, another thing that surprises me is that the `webInf.fileMatching` block prints files that don't go into WEB-INF.

Comment by Gradle Forums [ 21/Aug/14 ]

If you are trying to prevent classpath items from being included in the WAR you can use the ```providedCompile``` configuration.

Comment by Gradle Forums [ 21/Aug/14 ]

No, that's not what I'm trying to do. I'm trying to exclude and rename some files coming from the resources. I need them in build/resources/main when executing my unit tests, but I don't want them in the war.

Comment by Gradle Forums [ 21/Aug/14 ]


from ("${project(':frontend').projectDir}/app")

{ rename .... exclude ... }
Comment by Gradle Forums [ 21/Aug/14 ]

Nope. that would allow renaming and excluding files coming from the `../frontend/app` folder.

What I want is to rename and exclude files coming from the current project's `build/resources/main` folder and going to the `WEB-INF/classes` directory of the war. These are copied implicitely by the war task.

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 [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

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