[GRADLE-2398] Gradle and tomcat7 cannot co-exist on Debian & Ubuntu due to bad package dependencies Created: 21/Jul/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Jon Cox Assignee: Unassigned
Resolution: Won't Fix Votes: 2


Having to choose between running gradle and installing tomcat7
on .deb based systems is clearly a really bad thing.

Here's a copy of the bug posted for Ubuntu systems;
the same issue effects the Debian distro itself.
It would be nice if whomever is responsible for this
package push the changes to the Debian, Ubuntu & whomever
else uses .deb packaging:

  • - - - - - - -

gradle depends on libtomcat6-java. tomcat7 depends on tomcat7-common, which depends on libtomcat7-java, which conflicts with libtomcat6-java; thus you cannot install both gradle and tomcat7.

Perhaps there should be a libtomcat-java meta-package (provided by libtomcat6-java | libtomcat7-java) that gradle depends on, or Gradle's Tomcat plugin should be split out to a separate package. Or maybe libtomcat6-java and libtomcat6-java do not really need to conflict.


Comment by Jon Cox [ 21/Jul/12 ]

The latest Eclipse cannot co-exist with gradle on
Debian & Ubuntu systems either...

Again, this is due to the same Gradle packaging bug.
That's why I'm guessing this should be prioritized
as "critical", as it may effect easy adoption & upgrades.

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