July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3493) Add link to central update zip to JBDS updates page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3493?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3493: ----------------------------- Attachment: offline-zips.png I've added links to /staging/, /development/, and even /snapshots/ pages: !offline-zips.png! https://devstudio.redhat.com/9.0/development/updates/ https://devstudio.redhat.com/9.0/staging/updates/ https://devstudio.redhat.com/9.0/snapshots/updates/ > Add link to central update zip to JBDS updates page > --------------------------------------------------- > > Key: JBDS-3493 > URL: https://issues.jboss.org/browse/JBDS-3493 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Jan Richter > Assignee: Nick Boldt > Attachments: offline-zips.png > > > Looking at https://devstudio.jboss.com/9.0/staging/updates/ I can see there are links to target platform and update site zips, but I can't find any link to the central zip. > When we looked over JBDS-3491, we discovered that downloading the central zip without access to the installer sites becomes a bit tricky this way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19987) Batch diagram popup is not readable

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19987?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19987: ---------------------------------- Component/s: upstream > Batch diagram popup is not readable > ----------------------------------- > > Key: JBIDE-19987 > URL: https://issues.jboss.org/browse/JBIDE-19987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.3.0.CR1 > > Attachments: batch-editor.png > > > In Batch editor, Diagram tab, when I create a new step, select it and roll mouse over action buttons the text is not readable very well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19987) Batch diagram popup is not readable

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19987?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-19987: --------------------------------------- I gave up with workaround. Reported issue to bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=473945 > Batch diagram popup is not readable > ----------------------------------- > > Key: JBIDE-19987 > URL: https://issues.jboss.org/browse/JBIDE-19987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.3.0.CR1 > > Attachments: batch-editor.png > > > In Batch editor, Diagram tab, when I create a new step, select it and roll mouse over action buttons the text is not readable very well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20399) Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20399?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-20399. ------------------------------------ Resolution: Duplicate Issue > Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2 > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20399 > URL: https://issues.jboss.org/browse/JBIDE-20399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.3.0.CR1 > > Attachments: Screenshot-4.png, Screenshot-5.png > > > See attached screen shots - any combination of user inputs returns this error if the user attempts to create a new v3 application: > The server type, credentials, or auth scheme might be incorrect. Could not get resource ~ in namespace : <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>404 Not Found</title> > </head><body> > <h1>Not Found</h1> > <p>The requested URL /oapi was not found on this server.</p> > <p>Additionally, a 403 Forbidden > error was encountered while trying to use an ErrorDocument to handle the request.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at openshift.redhat.com Port 443</address> > </body></html> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20399) Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20399?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20399: ------------------------------------- Fix Version/s: 4.3.0.CR1 > Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2 > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20399 > URL: https://issues.jboss.org/browse/JBIDE-20399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.3.0.CR1 > > Attachments: Screenshot-4.png, Screenshot-5.png > > > See attached screen shots - any combination of user inputs returns this error if the user attempts to create a new v3 application: > The server type, credentials, or auth scheme might be incorrect. Could not get resource ~ in namespace : <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>404 Not Found</title> > </head><body> > <h1>Not Found</h1> > <p>The requested URL /oapi was not found on this server.</p> > <p>Additionally, a 403 Forbidden > error was encountered while trying to use an ErrorDocument to handle the request.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at openshift.redhat.com Port 443</address> > </body></html> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20397: ------------------------------------- Labels: application_wizard openshift_v3 port_forwarding_wizard (was: application_wizard openshift_v3) > [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20404) [origin_intservice_59]Port forwarding wizard: can not open wizard after I stopped forwarding in eclipse console

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20404?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20404: ------------------------------------- Labels: application_wizard openshift_v3 port_forwarding_wizard (was: application_wizard openshift_v3) > [origin_intservice_59]Port forwarding wizard: can not open wizard after I stopped forwarding in eclipse console > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20404 > URL: https://issues.jboss.org/browse/JBIDE-20404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150729-1035-B906 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Priority: Critical > Labels: application_wizard, openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > > 'Port Forwarding' window doesn't pop up after stop forwarding from eclipse console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20404) [origin_intservice_59]Port forwarding wizard: can not open wizard after I stopped forwarding in eclipse console

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20404?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20404: ------------------------------------- Summary: [origin_intservice_59]Port forwarding wizard: can not open wizard after I stopped forwarding in eclipse console (was: [origin_intservice_59]can not open 'Port Forwarding' window after stop forwarding from eclipse console) > [origin_intservice_59]Port forwarding wizard: can not open wizard after I stopped forwarding in eclipse console > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20404 > URL: https://issues.jboss.org/browse/JBIDE-20404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150729-1035-B906 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > 'Port Forwarding' window doesn't pop up after stop forwarding from eclipse console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-20389. ------------------------------------ > Jenkins: inconsistent, regular test failures in openshift/egit > -------------------------------------------------------------- > > Key: JBIDE-20389 > URL: https://issues.jboss.org/browse/JBIDE-20389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: jenkins-sane.png, openshift-builds.png > > > Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build. > {quote} > Build #33 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > {quote} > {quote} > Build #34: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject > {quote} > {quote} > Build #35 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite) > Failing for the past 1 build (Since Unstable#35 ) > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20389: ------------------------------------------ I now reached [30|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/...] sane builds without changing anything. This very looks to me like a hardware caused problem. !jenkins-sane.png! Closing as OUTDATED > Jenkins: inconsistent, regular test failures in openshift/egit > -------------------------------------------------------------- > > Key: JBIDE-20389 > URL: https://issues.jboss.org/browse/JBIDE-20389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: jenkins-sane.png, openshift-builds.png > > > Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build. > {quote} > Build #33 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > {quote} > {quote} > Build #34: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject > {quote} > {quote} > Build #35 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite) > Failing for the past 1 build (Since Unstable#35 ) > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 July 2015