[GRADLE-780] War plugin should neither publish war archive nor disable the default jar task. Created: 14/Dec/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Hans Dockter Assignee: Unassigned
Resolution: Won't Fix Votes: 4


See: http://markmail.org/thread/l67rpwzpurkn4zur

Comment by Davide Cavestro [ 14/Jun/11 ]

Hi guys, is there any schedule for the

deployable and library plugin (based on the java plugin)

mentioned on the quoted thread ?
I'm just starting to write a simple gradle script that builds a web app and upload the war to artifactory (this time using the maven repository only as a way to share the artifact, not for dependency management) and I'd like to know if there's chances for breaking changes in the near future.
Moreover, I've not found yet if there's a standard naming strategy for war publishing (i.e. adding .war as last groupId token). Maybe this is a purely maven repository question, or maybe it's something you have to handle to enforce convention-over-configuration for enhancements you're thinking of.


Comment by Szczepan Faber [ 14/Jun/11 ]

The current plan is to be backwards compatible in regards to publishing. So you can build your script no worries. Hope that helps

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 11:38:43 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.