[GRADLE-1978] Ear Plugin incorrectly picks up application.xml Created: 01/Dec/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Matt Accola Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Attachments: Zip Archive ear-plugin-bug.zip    


The attached project shows that if there is a META-INF/application.xml file present in the project it is added to the EAR. According to the documentation this should not be. From the documentation:

appDirName Default Value = src/main/application

deploymentDescriptor Description = Metadata to generate a deployment descriptor file, e.g. application.xml. If this file already exists in the appDirName/META-INF then the existing file contents will be used and the explicit configuration in the ear.deploymentDescriptor will be ignored.

That means that it should use an application.xml only if it exists in src/main/application/META-INF.

See attached project for a demonstration of the defect.

Comment by David Nelson [ 12/Feb/13 ]

I am hitting this as well. It appears that there is no way to ignore the application.xml and generate a custom one instead. This is significant because we have an application.xml in our source tree that is used by RAD that we do not want to remove.

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:09:29 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.