[GRADLE-10] Create hierachy of non-Gradle projects Created: 15/Feb/08  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Steven Devijver Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

A Maven project that is depended upon by a Gradle project could have a hierarchy.groovy file that list other non-Gradle projects. These projects don't need to have any specific configuration.

When the Gradle project is build the Maven project will be build first. However, because of the hierarchy declaration the other projects in the hierarchy will be build first and then the Maven project.

This should work stand-alone too, so that with a hierarchy.groovy file you can build a hierarchy of Maven projects, effectively replacing the <modules/> section in Maven pom.xml files.

Gradle projects can be considered as a non-Gradle projects too. In that case a new Gradle command would be launched to build these projects.

 Comments   
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:19:47 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.