[
https://issues.jboss.org/browse/JBIDE-21727?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-21727:
-------------------------------
Attachment: compositeContent.xml
compositeArtifacts.xml
mockup-change-1.png
mockup-change-2.png
openshiftv3-tools-server-adapter.png
openshiftv3-tools-server-adapter-no-license-found.png
Did a quick test today to see if this is easily doable.
First, you need to build the JBT update site with this patch applied to
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...:
{code}
<!-- openshift v3 -->
<feature id="org.jboss.tools.openshift.feature">
<category name="CoreTools" />
<category name="CloudTools" />
+ <category name="org.eclipse.wst.server.core.serverAdapter"/>
</feature>
{code}
Then build:
{code}
cd jbosstools-build-sites/aggregate/site; mvn clean install
{code}
Next, create a composite site in *jbosstools-build-sites/aggregate/target/composite/*
using files like these:
[^compositeArtifacts.xml]
[^compositeContent.xml]
Next, test out the site by pointing the WTP server discovery plugin at your new site:
0. unpack eclipse-jee-neon-M5-linux-gtk-x86_64.tar.gz
1. hack up eclipse/plugins/org.eclipse.wst.server.discovery_1.2.0.v201601132253.jar to
edit these files, in order to point at your local site:
* org.eclipse.wst.server.discovery_1.2.0.v201601132253.jar!/serverAdapterSitesDetails.xml
* org.eclipse.wst.server.discovery_1.2.0.v201601132253.jar!/serverAdapterSites.xml
Changes:
[^mockup-change-1.png]
{code}<site
url="file:///home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/site/target/composite/"/>{code}
[!mockup-change-2.png]
{code}
<feature
uri="file:///home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/site/target/composite/"
id="org.jboss.ide.eclipse.as.feature.feature.group" name="JBoss AS,
WildFly, & EAP Server Tools"
description="Provides WTP server adapters for JBoss installations. These adapters
are capable of deployment and providing classpaths for projects. Zipped or exploded
deployments, JMX integration, and other extensions are included."
provider="Red Hat JBoss Middleware"
version="3.2.0.Alpha1-v20160303-0134-B927" runtime-vendor="Red Hat JBoss
Middleware">
</feature>
<feature
uri="file:///home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/site/target/composite/"
id="org.jboss.tools.openshift.feature.feature.group" name="JBoss
OpenShift 3 Tools"
description="Provides Tooling to work with OpenShift architectural version
3."
provider="Red Hat JBoss Middleware"
version="3.2.0.Alpha1-v20160310-0336-B1191" runtime-vendor="Red Hat JBoss
Middleware">
</feature>{code}
2. start up Eclipse. check list of server adpaters available from the *Servers* view >
*No servers are available. Click this link to create a new server...*
3. scroll down to find Red Hat JBoss Middleware, expand section.
4. select "JBoss OpenShift 3 Tools"
[^openshiftv3-tools-server-adapter.png]
5. note the missing license -- not sure why this is happening.
[^openshiftv3-tools-server-adapter-no-license-found.png]
6. click Finish. ... nothing gets installed.
7. Repeat for the "JBoss AS, WildFly & EAP Server Tools" adapter and it
works fine.
add OpenShift server adapter to downloadable WTP server adapters
----------------------------------------------------------------
Key: JBIDE-21727
URL:
https://issues.jboss.org/browse/JBIDE-21727
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift, server
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Critical
Fix For: 4.4.0.Alpha1
Attachments: compositeArtifacts.xml, compositeContent.xml, mockup-change-1.png,
mockup-change-2.png, openshiftv3-tools-server-adapter-no-license-found.png,
openshiftv3-tools-server-adapter.png
We have JBoss server adapters available in Eclise new Server wizard; would be great if we
could put OpenShift in there too.
Anything preventing us from doing so ?
Is there a workflow from New server that helps users to create openshift connection etc.
?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)