May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24302) Circular fragment workflow for optional runtime use case

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24302?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24302: ------------------------------------- How did you even know to open this bug? Did I tell you about the upstream? I'm baffled! > Circular fragment workflow for optional runtime use case > -------------------------------------------------------- > > Key: JBIDE-24302 > URL: https://issues.jboss.org/browse/JBIDE-24302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > This is a tracking issue for this upstream bug: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=514888 > > Rob's description: > While playing with the changes dropped for Bug 513486, I found a small bug. > When a runtime is optional, the wtp framework does not add the runtime fragment directly. It will only add the server fragment, and assume that the server fragment will introduce the runtime fragment in the workflow as it chooses. > A workflow was discovered where the NewServerWizardFragment is still adding the runtime fragment before the server fragment. Since the server may also be adding that fragment later, it leads to circular behavior because the runtime fragment is in the list of fragments twice. The user will then press next continually but never advance. > Sorry for this bug. It only happens under specific situations. > Workflow: > 1) new server wizard, choose server type with optional runtime > 2) Go forward, change settings in server fragment, causing server fragment to designate runtime fragment as a child > 3) go back to main page of server wizard to change host > 4) Change host to 127.0.0.1 > 5) Press forward, forward, forward, etc. never ends. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24350) Forge New and Noteworthy for 4.4.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24350?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-24350. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24350 > URL: https://issues.jboss.org/browse/JBIDE-24350 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24345 #comment Create N&N for Forge 4.4.4.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.4.Final since the AM3 release of Forge, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.4.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.4.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23784) WF 11 / EAP 7.1 Incremental MGMT publishing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23784?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23784: ------------------------------------- I added this stuff to maintenance final. Please beat the hell out of it. It works for me, but if it's a no-op on your end, that's fine. Just make sure nothing is broken or crapping out or worse than it was without the app. > WF 11 / EAP 7.1 Incremental MGMT publishing > ------------------------------------------- > > Key: JBIDE-23784 > URL: https://issues.jboss.org/browse/JBIDE-23784 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.4.Final, 4.5.0.AM2 > > > WF 11 and EAP 7.1 will have support for management deployment in an incremental fashion. > WF 11 nightly builds for the pre-alpha are here: https://developer.jboss.org/thread/224262 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23784) WF 11 / EAP 7.1 Incremental MGMT publishing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23784?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23784: -------------------------------- Fix Version/s: 4.4.4.Final > WF 11 / EAP 7.1 Incremental MGMT publishing > ------------------------------------------- > > Key: JBIDE-23784 > URL: https://issues.jboss.org/browse/JBIDE-23784 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.4.Final, 4.5.0.AM2 > > > WF 11 and EAP 7.1 will have support for management deployment in an incremental fashion. > WF 11 nightly builds for the pre-alpha are here: https://developer.jboss.org/thread/224262 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24383) Connection wizard: offer openshift.io as default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24383?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24383: ------------------------------------- Priority: Blocker (was: Major) > Connection wizard: offer openshift.io as default server > ------------------------------------------------------- > > Key: JBIDE-24383 > URL: https://issues.jboss.org/browse/JBIDE-24383 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.4.Final > > > now that https://openshift.io is launched we should provide it as default server in the connection wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24212) Server New and Noteworthy for 4.4.4.AM3

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24212?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-24212. ------------------------------- Fix Version/s: 4.4.4.AM3 Resolution: Done Jolokia thing isn't enough for me to make a n&n out of. =/ It's more of an improvement. > Server New and Noteworthy for 4.4.4.AM3 > --------------------------------------------------- > > Key: JBIDE-24212 > URL: https://issues.jboss.org/browse/JBIDE-24212 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.4.AM3 > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24190 #comment Create N&N for Server 4.4.4.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24294) "Starting Container Development Environment 3" stays blocked when cdk launch is failing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24294?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24294: -------------------------------- Fix Version/s: 4.5.0.AM1 > "Starting Container Development Environment 3" stays blocked when cdk launch is failing > --------------------------------------------------------------------------------------- > > Key: JBIDE-24294 > URL: https://issues.jboss.org/browse/JBIDE-24294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > Attachments: image-2017-04-24-14-46-36-250.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24373) Can't push an image to the CDK3 Docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24373?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24373: ------------------------------------- Description: Pushing an image to the CDK3 Docker registry is not possible. When the image is tagged, the registry port is not used thus Docker will try to contact the CDK Docker registry in port 80 causing a timeout to occur at the UI level. Steps to reproduce: # Create a Docker and OpenShift connection to CDK3 (using the server adapter or manually) # Edit the OpenShift connection and add http://172.30.1.1:5000 as the registry address ("minishift docker-env" should tell you about this url) # Build your own Docker image on the CDK3 Docker connection # Deploy that image and select Push to registry: a timeout will occur after 30s was: Pushing an image to the CDK3 Docker registry is not possible. When the image is tagged, the registry port is not used thus Docker will try to contact the CDK Docker registry in port 80 causing a timeout to occur at the UI level. Steps to reproduce: # Create a Docker and OpenShift connection to CDK3 (using the server adapter or manually) # Edit the OpenShift connection and add http://172.30.1.1:5000 as the registry address # Build your own Docker image on the CDK3 Docker connection # Deploy that image and select Push to registry: a timeout will occur after 30s > Can't push an image to the CDK3 Docker registry > ----------------------------------------------- > > Key: JBIDE-24373 > URL: https://issues.jboss.org/browse/JBIDE-24373 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.4.Final > > > Pushing an image to the CDK3 Docker registry is not possible. When the image is tagged, the registry port is not used thus Docker will try to contact the CDK Docker registry in port 80 causing a timeout to occur at the UI level. > Steps to reproduce: > # Create a Docker and OpenShift connection to CDK3 (using the server adapter or manually) > # Edit the OpenShift connection and add http://172.30.1.1:5000 as the registry address ("minishift docker-env" should tell you about this url) > # Build your own Docker image on the CDK3 Docker connection > # Deploy that image and select Push to registry: a timeout will occur after 30s -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23869: ------------------------------------- Sent a PR for jbt-server, but, this PR won't build yet. I've had to ask Roland Huss to create a snapshot. http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.jolokia%22 doesn't have any snapshots listed. :| > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.4.4.Final > > Attachments: image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24384) archives.prcheck needs to be fixed or disabled; annoying AF

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24384?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-24384: ----------------------------------- Assignee: Rastislav Wagner > archives.prcheck needs to be fixed or disabled; annoying AF > ----------------------------------------------------------- > > Key: JBIDE-24384 > URL: https://issues.jboss.org/browse/JBIDE-24384 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rastislav Wagner > Fix For: 4.5.0.AM1 > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/archives... > This job keeps trying to pull http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.pro... > It fails every time. It is annoying. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 May 2017