[
https://issues.apache.org/jira/browse/JCLOUDS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604756#comment-14604756
]
Andrew Kennedy commented on JCLOUDS-172:
----------------------------------------
Now that the GCE provider has been promoted to core, the commit history is no
longer present on jclouds-labs. So looking at
https://github.com/jclouds/jclouds-labs/tree/1.9.x/google-compute-engine will
give a 404, similalry for all other older release branches. However the
provider was only ported to the 2.0.0-SNAPSHOT (i.e. master) branch of jclouds
core, so the 1.9.x branch of core does not include GCE. This means that a build
of 1.9.1-SNAPSHOT will not have the GCE provider included.
I think we should reinstate GCE into labs, with the entire commit history, and
then add a commit to master on labs that deletes the tree and removes it from
the POM file. That way all old builds will still work, and 1.9.1 (when it is
released) will still have the GCE provider in labs, which is what I would
expect - I shouldn't have to change my code for a minor release, even in labs.
This is important for us at Apache Brooklyn as we use the GCE provider from
labs as a dependency, and we are still using the 1.9.x stream of jclouds.
> "Graduate" GCE to core
> ----------------------
>
> Key: JCLOUDS-172
> URL: https://issues.apache.org/jira/browse/JCLOUDS-172
> Project: jclouds
> Issue Type: Task
> Components: jclouds-compute, jclouds-labs-google
> Affects Versions: 1.8.0
> Reporter: Andrew Bayer
> Assignee: Ignasi Barrera
> Priority: Critical
> Labels: google-compute-engine
> Fix For: 2.0.0
>
>
> We should really get GCE to a "finished" state and include it in 1.7.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
