[JBoss JIRA] (JBIDE-24411) Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24411?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24411:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24411
> URL: https://issues.jboss.org/browse/JBIDE-24411
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Labels: explorer, openshift_v3
> Fix For: 4.5.x
>
>
> Currently if I have an OpenSHift connection in OpenSHift Explorer which have bad credentials, if I expand it i have a little error message in the tree (which is nice)
> So I right-click -> Edit connection... I update my connection parameters and when I click finish, in the tree I still have the error. I need to manually right-click -> refresh.
> it would be nice to refresh automatically the tree when the connection has been edited
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24285) Java coredump when starting jboss server from Eclipse
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24285?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24285:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Java coredump when starting jboss server from Eclipse
> -----------------------------------------------------
>
> Key: JBIDE-24285
> URL: https://issues.jboss.org/browse/JBIDE-24285
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Environment: Windows 7
> System memory 24GB - memory checked and no issues found.
> JDK 1.8.0_121 x64
> JBoss EAP 6.4
> Eclipse Neon.3 with JBoss server support installed (Not full JBoss Developer Studio)
> Reporter: Beirti O'Nunain
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: hs_err_pid53068.log, hs_err_pid58832.log
>
>
> Intermittently, when starting a JBoss server from the "servers" view in Debug mode, the process coredumps shortly after starting the application. (3rd party application provided by Calypso) I've not seen this with non-jboss processes yet.
> Problematic frame always points to jvm.dll (same frame 0x68637). Logs attached.
> I've started the JBoss process with -Xcheck:jni but unfortunately the console is full of noise from
> WARNING: JNI local refs: zu, exceeds capacity: zu
> which causes the process to timeout on startup due to massively slowing down the startup. You can add this flag locally to see full logs
> Have also tried bumping Xmx/Xms from 1g to 4g but still getting the same issue. This issue does not occur if I start the server in 'run' mode instead of 'debug'.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23402:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> [WATCHER] Explorer: can "Deploy Latest" even if the build failed
> ----------------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24509) No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24509?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24509:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final
> ------------------------------------------------------------------------
>
> Key: JBIDE-24509
> URL: https://issues.jboss.org/browse/JBIDE-24509
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Environment: JBoss Tools 4.4.4.Final
> http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...
> Eclipse Neon 4.6.1
> Fedora 24 and Windows 10
> Reporter: Xia Zhao
> Priority: Blocker
> Fix For: 4.5.x
>
> Attachments: OpenShift3.png, Screenshot from 2017-05-25 13-37-32.png, Screenshot from 2017-05-25 14-25-53.png, Screenshot from 2017-06-02 10-20-42.png, Screenshot from 2017-06-02 10-39-16.png, Screenshot from 2017-06-02 10-54-54.png
>
>
> Description of problem:
> No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final, after installation, only these 3 tools exist without having the openshift v3 tools:
> JBoss OpenShift 2 Tools
> JBoss OpenShift JavaScript Tools
> JBoss Tools EGit Integration
> Version-Release number of selected component (if applicable):
> JBoss Tools 4.4.4.Final
> http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...
> How reproducible:
> Always
> Steps to Reproduce:
> 1.Install JBT for Openshift v3 Tools according to http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...:
> --> Add the following URL to Eclipse Neon 4.6.1 installation via:
> Help > Install New Software... > Work with:
> http://download.jboss.org/jbosstools/neon/stable/updates/
> Then select all the components, choose to install them.
> 2. Restart Eclipse Neon 4.6.1 after JTB installation finished
> 3. Go into Openshift Explorer window, click on "New Connections Wizard", choose "Openshift 3" for server type, the Authentication panel is empty
> 4. Go to Help > Intallation Details, search for openshift
> Actual results:
> 4. JBoss OpenShift 3 Tools are not installed, only the following 3 exist:
> JBoss OpenShift 2 Tools 3.3.3.v20170510-1453 org.jboss.tools.openshift.express.feature.feature.group JBoss by Red Hat
> JBoss OpenShift JavaScript Tools 3.3.3.v20170502-0607 org.jboss.tools.openshift.js.feature.feature.group JBoss by Red Hat
> JBoss Tools EGit Integration 3.3.3.v20170405-1252 org.jboss.tools.openshift.egit.integration.feature.feature.group JBoss by Red Hat
> Expected results:
> JBoss OpenShift 3 Tools should be installed if following http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...
> Additional info:
> Issue reproduced on both Fedora 24 and Windows 10.
> This is a regression, with old JBT build 4.3.3 Final, the openshift 3 tools existed and worked fine.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months