You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by neykov <gi...@git.apache.org> on 2017/05/08 16:41:58 UTC
[GitHub] brooklyn-server pull request #673: [WIP] Upgrade to jclouds 2.1
GitHub user neykov opened a pull request:
https://github.com/apache/brooklyn-server/pull/673
[WIP] Upgrade to jclouds 2.1
Here are the changes I needed to implement in order to run Brooklyn against current jclouds master.
Leaving them around to be reused for the jclouds 2.1.0 upgrade once released.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/neykov/brooklyn-server jclouds-2.1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/673.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #673
----
commit 8f56bc89d8d0983e1599cc50725652b2b5efeda4
Author: Svetoslav Neykov <sv...@cloudsoftcorp.com>
Date: 2017-05-08T16:40:14Z
Upgrade to jclouds 2.1.0-SNAPSHOT
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-server issue #673: [WIP] [JCLOUDS 2.1.0] Upgrade to jclouds 2.1
Posted by neykov <gi...@git.apache.org>.
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/673
Thanks @andreaturli, @geomacy, closing.
---
[GitHub] brooklyn-server issue #673: [WIP] [JCLOUDS 2.1.0] Upgrade to jclouds 2.1
Posted by geomacy <gi...@git.apache.org>.
Github user geomacy commented on the issue:
https://github.com/apache/brooklyn-server/pull/673
hi @neykov I think this can be retired now as superseded by https://github.com/apache/brooklyn-server/pull/950. Andrea cross checked against this one before his was merged.
---
[GitHub] brooklyn-server pull request #673: [WIP] [JCLOUDS 2.1.0] Upgrade to jclouds ...
Posted by neykov <gi...@git.apache.org>.
GitHub user neykov reopened a pull request:
https://github.com/apache/brooklyn-server/pull/673
[WIP] [JCLOUDS 2.1.0] Upgrade to jclouds 2.1
These are the changes I needed to implement in order to run Brooklyn against current jclouds master.
Leaving them around to be reused for the jclouds 2.1.0 upgrade once released.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/neykov/brooklyn-server jclouds-2.1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/673.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #673
----
commit b15ba3c9c3f30e152df1c5a6b497ae4451636b1c
Author: Svetoslav Neykov <sv...@cloudsoftcorp.com>
Date: 2017-05-08T16:40:14Z
Upgrade to jclouds 2.1.0-SNAPSHOT
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-server pull request #673: [WIP] [JCLOUDS 2.1.0] Upgrade to jclouds ...
Posted by neykov <gi...@git.apache.org>.
Github user neykov closed the pull request at:
https://github.com/apache/brooklyn-server/pull/673
---
[GitHub] brooklyn-server issue #673: [JCLOUDS 2.1.0] Upgrade to jclouds 2.1
Posted by aledsage <gi...@git.apache.org>.
Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/673
Thanks @neykov - can you include "[WIP]" or some such in the PR name, so we know not to merge this yet (given it points at 2.1.0-SNAPSHOT, and 2.1.0 isn't released yet).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-server issue #673: [WIP] [JCLOUDS 2.1.0] Upgrade to jclouds 2.1
Posted by neykov <gi...@git.apache.org>.
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/673
Github closed this by mistake, confused by the already merged commit (and later reverted). Cherry-picked the same commit and reopening.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] brooklyn-server pull request #673: [WIP] [JCLOUDS 2.1.0] Upgrade to jclouds ...
Posted by neykov <gi...@git.apache.org>.
Github user neykov closed the pull request at:
https://github.com/apache/brooklyn-server/pull/673
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---