[JBoss JIRA] (JBIDE-22151) Failed to install JBT in Eclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22151?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22151 at 4/21/16 2:59 PM:
-------------------------------------------------------------
On Fedora 20, I can now install all of JBT "Abridged" category into eclipse-jee-neon-M6-linux-gtk-x86_64.tar.gz, including Openshift Tools 3.2.0.Alpha1-v20160420-0235-B1252.
{code}
./plugins/org.jboss.tools.openshift.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.client_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.client_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.egit.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.common.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.common.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.egit.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.cdk.server_3.2.0.Alpha1-v20160420-0235-B1252.jar
./features/org.jboss.tools.openshift.express.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.cdk.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.egit.integration.feature_3.2.0.Alpha1-v20160420-0235-B1252
./plugins/org.eclipse.jetty.client_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.continuation_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.http_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.io_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.proxy_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.security_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.server_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.servlet_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.servlets_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.util_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.webapp_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.websocket.api_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.websocket.client_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.websocket.common_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.websocket.server_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.websocket.servlet_9.3.5.v20151012.jar
./plugins/org.eclipse.jetty.xml_9.3.5.v20151012.jar
{code}
[^jbt44alpha1-os3.png]
[^jbt44alpha1-os3-1.png]
was (Author: nickboldt):
On Fedora 20, I can now install all of JBT "Abridged" category into eclipse-jee-neon-M6-linux-gtk-x86_64.tar.gz, including Openshift Tools 3.2.0.Alpha1-v20160420-0235-B1252.
{code}
./plugins/org.jboss.tools.openshift.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.client_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.client_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.egit.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.common.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.common.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.egit.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.cdk.server_3.2.0.Alpha1-v20160420-0235-B1252.jar
./features/org.jboss.tools.openshift.express.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.cdk.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.egit.integration.feature_3.2.0.Alpha1-v20160420-0235-B1252
{code}
[^jbt44alpha1-os3.png]
[^jbt44alpha1-os3-1.png]
> Failed to install JBT in Eclipse
> --------------------------------
>
> Key: JBIDE-22151
> URL: https://issues.jboss.org/browse/JBIDE-22151
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: Operating System: have tried Fedora 17 and 22
> jbt version: 3.2.0.Alpha1-v20160409-1043-B1241
> eclipse:
> Version: Neon Milestone 6 (4.6.0M6)
> Build id: 20160329-0659
> Reporter: Chunyun Chen
> Assignee: Fred Bricon
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbt44alpha1-os3-1.png, jbt44alpha1-os3.png, jbt_installation_1.png, jbt_installation_2.png
>
>
> Will meet below dependency errors when installing jbt in eclipse:
> "
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
> Missing requirement: Openshift 3 Client 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.client 3.2.0.Alpha1-v20160409-1043-B1241) requires 'bundle org.eclipse.jetty.websocket.client 9.2.13' but it could not be found
> Cannot satisfy dependency:
> From: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
> To: org.jboss.tools.openshift.client [3.2.0.Alpha1-v20160409-1043-B1241]
> "
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22151) Failed to install JBT in Eclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22151?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22151:
-------------------------------
Attachment: jbt44alpha1-os3.png
jbt44alpha1-os3-1.png
On Fedora 20, I can now install all of JBT "Abridged" category into eclipse-jee-neon-M6-linux-gtk-x86_64.tar.gz, including Openshift Tools 3.2.0.Alpha1-v20160420-0235-B1252.
{code}
./plugins/org.jboss.tools.openshift.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.client_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.client_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.egit.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.common.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.common.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.express.ui_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.egit.core_3.2.0.Alpha1-v20160420-0235-B1252.jar
./plugins/org.jboss.tools.openshift.cdk.server_3.2.0.Alpha1-v20160420-0235-B1252.jar
./features/org.jboss.tools.openshift.express.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.cdk.feature_3.2.0.Alpha1-v20160420-0235-B1252
./features/org.jboss.tools.openshift.egit.integration.feature_3.2.0.Alpha1-v20160420-0235-B1252
{code}
[^jbt44alpha1-os3.png]
[^jbt44alpha1-os3-1.png]
> Failed to install JBT in Eclipse
> --------------------------------
>
> Key: JBIDE-22151
> URL: https://issues.jboss.org/browse/JBIDE-22151
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: Operating System: have tried Fedora 17 and 22
> jbt version: 3.2.0.Alpha1-v20160409-1043-B1241
> eclipse:
> Version: Neon Milestone 6 (4.6.0M6)
> Build id: 20160329-0659
> Reporter: Chunyun Chen
> Assignee: Fred Bricon
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbt44alpha1-os3-1.png, jbt44alpha1-os3.png, jbt_installation_1.png, jbt_installation_2.png
>
>
> Will meet below dependency errors when installing jbt in eclipse:
> "
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
> Missing requirement: Openshift 3 Client 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.client 3.2.0.Alpha1-v20160409-1043-B1241) requires 'bundle org.eclipse.jetty.websocket.client 9.2.13' but it could not be found
> Cannot satisfy dependency:
> From: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241)
> To: org.jboss.tools.openshift.client [3.2.0.Alpha1-v20160409-1043-B1241]
> "
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21885) Remove "()" from context-menu name of Start Build
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21885:
--------------------------------
Summary: Remove "()" from context-menu name of Start Build (was: Remvoe "()" from context-menu name of Start Build )
> Remove "()" from context-menu name of Start Build
> --------------------------------------------------
>
> Key: JBIDE-21885
> URL: https://issues.jboss.org/browse/JBIDE-21885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202
> OS: Fedora 22 & Windows 10
> Reporter: Xia Zhao
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: build-config-properties-menu.png
>
>
> The "()" from context-menu name of Start Build should be removed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3846) Create container oriented perspective
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3846?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3846:
------------------------------
Fix Version/s: 10.0.0.Alpha2
> Create container oriented perspective
> -------------------------------------
>
> Key: JBDS-3846
> URL: https://issues.jboss.org/browse/JBDS-3846
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: cdk, docker, openshift
> Affects Versions: 10.0.0.Alpha1
> Reporter: Marián Labuda
> Priority: Critical
> Fix For: 10.0.0.Alpha2
>
>
> At the moment we have only JBoss perspective. We should create a new, more container oriented perspective, where Docker Explorer view would be opened by default and other views should be added and aligned to satisfy user needs. Layout of perspective should be more focused on container development.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21634:
-------------------------------------
I'm ok with the menu idea. To reduce clutter in main menu we could do:
{noformat}
Scale(or better word) > Up
> Down
> To...
{noformat}
So where would that menus go? to the deployment node or the pod?
Behavior should match the webconsole, i.e should be immediately active. I guess we could add a checkbox to make it permanent (change DC)
> Explorer, Properties: Allow a user to scale their deployment
> ------------------------------------------------------------
>
> Key: JBIDE-21634
> URL: https://issues.jboss.org/browse/JBIDE-21634
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_v3, properties
> Fix For: 4.4.0.Alpha1
>
>
> The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of:
> 1. deployment (replication controller)
> 2. eclipse view of a deployment (server) -> walk back to the currrent deployment
> 3. pod -> walk back to the current deployment
> updating 'spec.replicas' causes a new pods to spin up
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months