Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TIMOB-25059] Add Hyperloop as a pre-packged module #9578

Merged
merged 4 commits into from Nov 10, 2017

Conversation

janvennemann
Copy link
Contributor

JIRA: https://jira.appcelerator.org/browse/TIMOB-25059

Optional Description:
First step of integrating Hyperloop into our SDK by bundling it as a pre-packaged module.

First step of integrating Hyperloop into our SDK by bundling it as a pre-packaged module.

// Hyperloop has no single platform downloads yet, so we use a fake platform
// that will download the all-in-one distribution.
supportedPlatforms = supportedPlatforms.concat([ 'hyperloop' ]);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so you can just hijack the "commonjs" entry to mean "All platforms" too. That's what I did locally when I took a look at this.

@sgtcoolguy
Copy link
Contributor

LGTM 👍

@@ -15,5 +15,8 @@
],
"commonjs": [
"https://github.com/appcelerator-modules/ti.cloud/releases/download/3.2.11/ti.cloud-commonjs-3.2.11.zip"
],
"hyperloop": [
"https://appcelerator-modules.s3.amazonaws.com/hyperloop-2.2.2.zip"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change to 3.0.0. Eventually, we should create a hyperloop-releases repo to store those, which would also have the benefit to attach changelogs and beta-versions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We probably should do that right away. I can't update this link right now because that would break builds since ee don't have a 3.0.0 published yet. That would also trigger the automatic update in SDKs <= 6.3.0 so we shouldn't even publish Hyperloop 3.0.0 the old way?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should. Then people with an old SDK can still download it, but that on the other hand still breaks their app because of the bumped api-version that requires 7.0.0 anyway.

@hansemannn
Copy link
Collaborator

PR approved. We should merge this one and do another PR once Hyperloop 3.0.0 GA is ready.

@sgtcoolguy sgtcoolguy merged commit 13c3c16 into tidev:master Nov 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants