[GRADLE-1453] Partial checkout of multi-project should be stand-alone buildable Created: 21/Mar/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Gerwin Jansen Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

I work for an enterprise company and our SVN branch is huge (3.62GB / 170984 files).
The main structure looks like this:

root
  components
      basicutil
      eventservice
      bpmengine
      ...70 more...
  ..misc...

Every team is responsible for a few components. Components have dependencies on other components. A developer does a partial checkout of his component (a full checkout is not workable).

Now I have 2 scenario's:

  1. The main build server does a full checkout and full build every night.
  2. The developer wants to build and test only his component before he commits a change.

If I setup my project as regular multi-project, the build of the developer fails because he is missing build files in the parent folders (due to partial checkout).
As far as I know, Maven is capable of doing this. Maybe it's a good idea to see what they are doing?

 Comments   
Comment by Gerwin Jansen [ 21/Mar/11 ]

Just some thoughts from my side:

  1. Gradle starts looking for *.gradle files in parent directories which are not available
  2. Gradle checks and figures out that the current directory is a SVN checkout
  3. Gradle starts looking for *.gradle files in the parent directories using the SVN URL.

This proposal solves the problem of finding the build files. I'm aware that the problem of finding dependencies is unsolved. Maybe download them from repository if they are not available as project?

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