Skip to content
This repository has been archived by the owner on Sep 16, 2022. It is now read-only.

Only one SDK for multiproject builds #11

Closed
RobertFischer opened this issue Jan 22, 2012 · 6 comments
Closed

Only one SDK for multiproject builds #11

RobertFischer opened this issue Jan 22, 2012 · 6 comments
Assignees
Milestone

Comments

@RobertFischer
Copy link
Contributor

Can you move the downloaded Google App Engine SDK directory to rootDir/build, and hook the downloadSdk task onto the rootProject instead of into the plugin-installed project? That way, multiple builds only need to download and expand the SDK once.

(You will want to version that SDK path in case there are multiproject builds that are built against multiple GAE SDK versions for some crazy reason.)

@ghost ghost assigned bmuschko Jan 24, 2012
@musketyr
Copy link
Contributor

in fact, it will make more reason to place the sdk somewhere in user dir in .gradle, .gae or some other reasonable sheard place. having 100MB+ SDK in each project is quite space consuming.

@RobertFischer
Copy link
Contributor Author

If we go with that approach, we'll want to make sure to version the
path, since different projects might use different SDKs.

~~ Robert.

On Thu, May 31, 2012 at 9:18 AM, musketyr
reply@reply.github.com
wrote:

in fact, it will make more reason to place the sdk somewhere in user dir in .gradle, .gae or some other reasonable sheard place. having 100MB+ SDK in each project is quite space consuming.


Reply to this email directly or view it on GitHub:
#11 (comment)

@musketyr
Copy link
Contributor

I can't see any problem. You already can have different SDK in single project if you upgrade the App Engine version. The shared folder should be similar to build\expoloded-gae-sdk content.

This means it should have following structure

.app-engine-sdks
  |
  + appengine-java-sdk-1.4.5
  |
  .
  .
  .
  |
  + appengine-java-sdk-1.6.6

@RobertFischer
Copy link
Contributor Author

Yeah, I don't see it as a problem, either. I just wanted to make sure
we were thinking about that.

~~ Robert.

On Thu, May 31, 2012 at 9:39 AM, musketyr
reply@reply.github.com
wrote:

I can't see any problem. You already can have different SDK in single project if you upgrade the App Engine version. The shared folder should be similar to build\expoloded-gae-sdk content.

This means it should have following structure

.app-engine-sdks
 |
 + appengine-java-sdk-1.4.5
 |
 .
 .
 .
 |
 + appengine-java-sdk-1.6.6

Reply to this email directly or view it on GitHub:
#11 (comment)

@bmuschko
Copy link
Owner

I like the idea of putting it into a common directory e.g. ~/.app-engine-sdks. IMHO we don't need a versioning-strategy as the SDK version number already indicates that.

bmuschko added a commit that referenced this issue Jun 3, 2012
@bmuschko
Copy link
Owner

bmuschko commented Jun 3, 2012

All downloaded App Engine SDKs will be stored in ~/.gradle/gae-sdk.

@bmuschko bmuschko closed this as completed Jun 3, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants