February 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3331: ------------------------------------- DownloadRuntimeLicenseFragment catches Exception and that is wrong because SWTError extends Error class which in turn extends Throwable so it never gets to try loading WebKit based browser (I'll create and link issue about this later) {code} try { >>> browser = new Browser(wrap, SWT.NONE); } catch (Exception e1) { browser = new Browser(wrap, SWT.WEBKIT); } {code} Using SWT.NONE style for Browser() force this code {code}package org.eclipse.swt.browser; import org.eclipse.swt.SWT; class BrowserFactory { WebBrowser createWebBrowser (int style) { boolean webkitInstalled = WebKit.IsInstalled (); if ((style & SWT.MOZILLA) != 0 || (!webkitInstalled && (style & SWT.WEBKIT) == 0)) { return new Mozilla (); } if (!webkitInstalled) return null; return new WebKit (); } } {code} to return new Mozilla() instance which fails to load native libraries. It looks like nether xulrunner nor webkit browser is available. > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RHEL66_jbosstools-diagnostics-20150127000831.zip, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19322) NPE when opening central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19322?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-19322. --------------------------------- Resolution: Done Fix has been committed in master. So the Project Example page or its preference page are off-limits in 4.3.0.Alpha1. Unless you add a dummy user site in the pref page. > NPE when opening central > ------------------------- > > Key: JBIDE-19322 > URL: https://issues.jboss.org/browse/JBIDE-19322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.3.0.Alpha2 > > Attachments: Preferences _002.png > > > I opened central via JBoss Central toolbar item and this NPE occured - An internal error occurred during: "Refreshing JBoss Tutorials...". Not always, but every second time. > {code} > java.lang.NullPointerException > at java.util.AbstractCollection.addAll(AbstractCollection.java:343) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getUserSites(ProjectExampleUtil.java:210) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getSites(ProjectExampleUtil.java:221) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:257) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:52) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-583) Add Section for OpenShift v3

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-583?page=com.atlassian.jira.plug... ] Jeff Cantrill commented on TOOLSDOC-583: ---------------------------------------- Trello cards that prompted this request: https://trello.com/c/f2fMXYjc and https://trello.com/c/3NflAHv0 > Add Section for OpenShift v3 > ---------------------------- > > Key: TOOLSDOC-583 > URL: https://issues.jboss.org/browse/TOOLSDOC-583 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: User Guide - OpenShift Tools > Affects Versions: 4.3.0 > Reporter: Jeff Cantrill > Assignee: Michelle Murray > Fix For: 4.3.0 > > > Add Section for OpenShift that is specific to architecture v3 which is based on Kubernetes and Docker. Should include similar section to what exists for v2 http://tools.jboss.org/documentation/howto/#developing-apps-for-the-cloud -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-583) Add Section for OpenShift v3

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-583?page=com.atlassian.jira.plug... ] Jeff Cantrill commented on TOOLSDOC-583: ---------------------------------------- [~mmurray] Is there something I can do to assist with this issue in way of documenting the items we have completed to date? > Add Section for OpenShift v3 > ---------------------------- > > Key: TOOLSDOC-583 > URL: https://issues.jboss.org/browse/TOOLSDOC-583 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: User Guide - OpenShift Tools > Affects Versions: 4.3.0 > Reporter: Jeff Cantrill > Assignee: Michelle Murray > Fix For: 4.3.0 > > > Add Section for OpenShift that is specific to architecture v3 which is based on Kubernetes and Docker. Should include similar section to what exists for v2 http://tools.jboss.org/documentation/howto/#developing-apps-for-the-cloud -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19164) Upgrade Forge Runtime to 2.14.0.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19164?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19164: ----------------------------------- Fix Version/s: 4.3.0.Alpha1 > Upgrade Forge Runtime to 2.14.0.Final > ------------------------------------- > > Key: JBIDE-19164 > URL: https://issues.jboss.org/browse/JBIDE-19164 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3356) Upgrade to newer JBoss Forge

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3356?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3356. ---------------------------------- Assignee: Koen Aers Resolution: Duplicate Issue > Upgrade to newer JBoss Forge > ---------------------------- > > Key: JBDS-3356 > URL: https://issues.jboss.org/browse/JBDS-3356 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: forge > Reporter: Claus Ibsen > Assignee: Koen Aers > Priority: Minor > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > Using latest JBDS download, and I did a Software/update, and there was a bunch of upgrades. > It upgraded forge to 2.13.0.Final. > As we work on some middleware tooling that would rely on a newer release of forge with bugfixes, then we would request to upgrade to 2.14.1 or newer when its released from the jboss forge team. > If there is some deadline, then upgrading to 2.14.0 is better than nothing. But we could maybe ask the forge team to do a quick 2.14.1 release. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3356) Upgrade to newer JBoss Forge

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3356?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3356: -------------------------------------- 4.2.x (JBDS 8.1.0) and master has already been upgraded to Forge Runtime to 2.14.0.Final - JBIDE-19164 So we can close this issue as a duplicate. But we need to fix N&N for 4.2.3.Beta1 because it states we bundle 2.13.1 - https://github.com/jbosstools/jbosstools-website/pull/339 > Upgrade to newer JBoss Forge > ---------------------------- > > Key: JBDS-3356 > URL: https://issues.jboss.org/browse/JBDS-3356 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: forge > Reporter: Claus Ibsen > Priority: Minor > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > Using latest JBDS download, and I did a Software/update, and there was a bunch of upgrades. > It upgraded forge to 2.13.0.Final. > As we work on some middleware tooling that would rely on a newer release of forge with bugfixes, then we would request to upgrade to 2.14.1 or newer when its released from the jboss forge team. > If there is some deadline, then upgrading to 2.14.0 is better than nothing. But we could maybe ask the forge team to do a quick 2.14.1 release. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3256: ----------------------------------- [~rruss]Wildfly is already available, we need the flexibility to point to any docker hub, either the docker hub where Kevin's images will live (could be public), the public docker hub [1] or a private docker hub (with and without a running with openshiftv3). [1] https://registry.hub.docker.com/search?q=library > JBoss specific Docker Tooling (Basic Integration) > ------------------------------------------------- > > Key: JBDS-3256 > URL: https://issues.jboss.org/browse/JBDS-3256 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Attachments: multiview_properties_docker_idea.bmml, multiview_properties_docker_idea.png > > > Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers. > Expected end-user flow 1: > 0) Installation - assumes boot2docker pre-installed on the end-user's machine > 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag. > 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location. > 3) I start (docker run) the image which auto-starts the embedded app server > 4) I can then deploy my .war or .ear to the running app server > 5) I can restart the running app server in debug mode and run the debugger > 6) I can undeploy and redeploy my .war or .ear > 7) I can stop/restart the running, embedded app server > 8) I can then commit (docker commit) > 9) then I can publish my changes (docker push) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19164) Upgrade Forge Runtime to 2.14.0.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19164?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19164: ----------------------------------- Labels: new_and_noteworthy (was: ) > Upgrade Forge Runtime to 2.14.0.Final > ------------------------------------- > > Key: JBIDE-19164 > URL: https://issues.jboss.org/browse/JBIDE-19164 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.2.3.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19334) Fix Refresh of a connection

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19334: ------------------------------------- Summary: Fix Refresh of a connection Key: JBIDE-19334 URL: https://issues.jboss.org/browse/JBIDE-19334 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha2 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Refreshing of a connection is broken because the handler was not registered properly -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2015