| Issue 634: | unhook vcloud and vcloud-express | |
| 2 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Right now, we have the following vCloud-related modules org.jclouds.common/vcloud-common org.jclouds.common/trmk-common org.jclouds.api/vcloudexpress <- untestable as there is no implementation of this org.jclouds.api/vcloud <- testable vcloud depends on vcloud-common trmk-common depends on vcloudexpress which depends on vcloud-common and overrides some classes that are incompatible in the 1.0 spec Let's unhook these in the following way org.jclouds.common/vcloud-common < fold into vcloud org.jclouds.common/trmk-common org.jclouds.api/vcloudexpress < fold into trmk-common, repackage code under vcloudexpress We'd end up with 2 less modules, easier maintenance, no more confusing vCloud 0.8 with incompatible 1.0 and no more package conflicts captured in the following discussion: http://groups.google.com/group/jclouds-dev/browse_thread/thread/b7b87cb710982349
Comment
1
by
project member
adrian.f...@gmail.com,
Jul 22, 2011
,
Jul 22, 2011
vcloudexpress and common-vcloud no longer exist completed the repackaging of the terremark modules trmk-common into org.jclouds.trmk.vcloud_0_8; trmk-ecloud into org.jclouds.trmk.ecloud; trmk-vcloudexpress into org.jclouds.trmk.vcloudexpress flattening classes within vcloud and trmk-common is not complete
Status: Started
,
Jul 24, 2011
just committed this. Please note that in the new terremark structure, the vcloud'like package is under org.jclouds.trmk.vcloud_0_8
Status: Fixed
|
||||||||||
| ► Sign in to add a comment | |||||||||||