December 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3497) Installer randomly failing to report download statistics

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-3497?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-3497: ----------------------------- Fix Version/s: 10.x (was: 9.x) > Installer randomly failing to report download statistics > -------------------------------------------------------- > > Key: JBDS-3497 > URL: https://issues.jboss.org/browse/JBDS-3497 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: usage > Affects Versions: 9.0.0.Beta2 > Environment: jboss-devstudio-9.0.0.Beta2-installer-standalone.jar > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.x > > > In about every third attempt to install JBDS (or maybe more frequently) a p2 error log appears saying this: > {noformat}!ENTRY org.eclipse.equinox.p2.artifact.repository 2 0 2015-08-04 08:14:33.521 > !MESSAGE Failure reporting download statistics to URL: https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.... > !STACK 1 > org.eclipse.core.runtime.CoreException: HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.getLastModified(RepositoryTransport.java:235) > at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.collectStats(MirrorRequest.java:268) > at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:235) > at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:153) > at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707) > at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1 > at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131) > at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69) > ... 1 more > !SUBENTRY 1 org.eclipse.equinox.p2.transport.ecf 4 1002 2015-08-04 08:14:33.522 > !MESSAGE HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt > !STACK 1 > org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1 > at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131) > at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !SUBENTRY 2 org.eclipse.ecf.identity 4 0 2015-08-04 08:14:33.522 > !MESSAGE General connection error with response code=-1 {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20426) JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20426?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20426: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-20426 > URL: https://issues.jboss.org/browse/JBIDE-20426 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: The Alchemist > Assignee: Rob Stryker > Fix For: 4.4.3.AM1 > > > This usually happens when I have a few big EARs attached, so I think the "checker" doesn't wait long enough to see if WF actually restarted. > The result is this weird situation where the "Servers" view says that it's "Stopped", but the Console view has the red square to terminate the process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20441) Explorer: As a user, I want to retrieve pod logs from the connection or project level

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20441?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20441: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Explorer: As a user, I want to retrieve pod logs from the connection or project level > ------------------------------------------------------------------------------------- > > Key: JBIDE-20441 > URL: https://issues.jboss.org/browse/JBIDE-20441 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Priority: Minor > Labels: explorer, help_wanted, openshift_v3 > Fix For: 4.5.0.AM1 > > Original Estimate: 8 minutes > Remaining Estimate: 8 minutes > > Allow users to right-click on a project or connection and be presented with a wizard that allows them to select their pod or build to get logs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20447) 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20447?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20447: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component > ------------------------------------------------------------------ > > Key: JBIDE-20447 > URL: https://issues.jboss.org/browse/JBIDE-20447 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Labels: testfailure > Fix For: 4.5.0.AM1 > > > *2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_mast... > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.0.CR1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowserOrLink{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowserOrLink} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.268</duration> > <errorStackTrace>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.foundation.ui.test.BrowserUtilTest.testCreateBrowserOrLink(BrowserUtilTest.java:51) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowserOrLink</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowser{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowser} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.0030</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowser</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20408) Explorer: Display port-forward wizard from the connection or project level

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20408?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20408: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Explorer: Display port-forward wizard from the connection or project level > -------------------------------------------------------------------------- > > Key: JBIDE-20408 > URL: https://issues.jboss.org/browse/JBIDE-20408 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Reporter: Jeff Cantrill > Labels: explorer, help_wanted, openshift_v3 > Fix For: 4.5.0.AM1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Allow a user to display the wizard from the connection or project level. This will require the user to choose the pod to use to port forward. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20405) Connection wizard: Improve the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20405?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20405: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Connection wizard: Improve the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20405 > URL: https://issues.jboss.org/browse/JBIDE-20405 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Priority: Minor > Labels: connection_wizard, help_wanted, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: Screenshot-4.png, Screenshot-5.png > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > See attached screenshots - can we provide a more descriptive, and better formatted, error message? Thx! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20397: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > [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 > Priority: Minor > Labels: application_wizard, openshift_v3, port_forwarding_wizard > Fix For: 4.5.0.AM1 > > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20300) As a user I would like to hot deploy my application to shorten the development cycle

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20300?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-20300. -------------------------------------- Resolution: Duplicate Issue > As a user I would like to hot deploy my application to shorten the development cycle > ------------------------------------------------------------------------------------ > > Key: JBIDE-20300 > URL: https://issues.jboss.org/browse/JBIDE-20300 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Fix For: 4.4.2.Final > > > As a developer, it would be nice to compile locally and sync the changes with an existing deployment of my application to shorten my code/test/deploy cycle. I'm not sure how feasible this is in v3. > * There may be a way to copy changed files to a running pod, but these changes would be lost if the pod is bounced unless there is persistent storage > * Where do the files get copied to? How do find this information out? An agreed location based on an annotation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20300) As a user I would like to hot deploy my application to shorten the development cycle

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20300?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20300: ------------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.x) > As a user I would like to hot deploy my application to shorten the development cycle > ------------------------------------------------------------------------------------ > > Key: JBIDE-20300 > URL: https://issues.jboss.org/browse/JBIDE-20300 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Fix For: 4.4.2.Final > > > As a developer, it would be nice to compile locally and sync the changes with an existing deployment of my application to shorten my code/test/deploy cycle. I'm not sure how feasible this is in v3. > * There may be a way to copy changed files to a running pod, but these changes would be lost if the pod is bounced unless there is persistent storage > * Where do the files get copied to? How do find this information out? An agreed location based on an annotation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by fede pia (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] fede pia edited comment on JBIDE-23641 at 12/14/16 11:00 AM: ------------------------------------------------------------- [~mmalina], I could solve this by installing an older version of the full JBoss Web bundle: {noformat} JBossAS Tools 3.0.3.Final-v20150325-0035-B129 org.jboss.ide.eclipse.as.feature.feature.group JBoss by Red Hat {noformat} However, I can't risk to bork my environment for the moment again since have multiple projects going on. was (Author: fedepia): [~mmalina], I could solve this by installing an older version of the full JBoss Web bundle: {{ JBossAS Tools 3.0.3.Final-v20150325-0035-B129 org.jboss.ide.eclipse.as.feature.feature.group JBoss by Red Hat}} However, I can't risk to bork my environment for the moment again since have multiple projects going on. > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.3.AM1 > > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 December 2016