[
https://issues.jboss.org/browse/JBIDE-9105?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-9105 at 6/11/11 12:57 AM:
-------------------------------------------------------------
Removing o.j.t.dc.client is easy - just pull the plugin from its containing feature [1].
Adding o.a.dc is equally easy - add it to the containing feature [1].
[1]
http://anonsvn.jboss.org/repos/jbosstools/trunk/deltacloud/features/org.j...
The complicated part is figuring out where to get the o.a.dc plugin source or binary so
that it can either:
a) be committed to our svn and built as part of our build (if source)
or
b) fetched from an update site and added to the target platform so it can be resolved when
building the o.j.t.dc.feature (if binary).
was (Author: nickboldt):
Removing o.j.t.dc.client is easy - just pull the plugin from its containing feature
[1].
Adding o.a.dc is equally easy - add it to the containing feature [1].
[1]
http://anonsvn.jboss.org/repos/jbosstools/trunk/deltacloud/features/org.j...
The complicated part is figuring out where to get the o.a.dc plugin sources or binary so
that it can either:
a) be committed to our svn and built as part of our build (if source)
or
b) fetched from an update site and added to the target platform so it can be resolved when
building the o.j.t.dc.feature.
Change Deltacloud to use the client code that was moved to apache
Deltacloud
----------------------------------------------------------------------------
Key: JBIDE-9105
URL:
https://issues.jboss.org/browse/JBIDE-9105
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.3.0.M1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.M2
In JBIDE-8975 we moved the client to org.apache.deltacloud. We now need to remove the
client in our SVN and change the plugins to use the client from org.apache.deltacloud
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira