December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23622) Cannot get log of completed build pod

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23622?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23622: ---------------------------------- Labels: openshift_v3 (was: ) > Cannot get log of completed build pod > ------------------------------------- > > Key: JBIDE-23622 > URL: https://issues.jboss.org/browse/JBIDE-23622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: log_build.png > > > When I am trying to get a log of completed build, either via context menu of a pod in tabbed property Pods or via context menu of a build in tabbed property Builds, I get following error dialog > !log_build.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23580) Integration tests global refactoring: org.jboss.tools.eclipsecs.ui.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23580?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23580: ---------------------------------- Assignee: Jeff MAURY > Integration tests global refactoring: org.jboss.tools.eclipsecs.ui.test > ----------------------------------------------------------------------- > > Key: JBIDE-23580 > URL: https://issues.jboss.org/browse/JBIDE-23580 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: checkstyle, integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.eclipsecs.ui.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23578) Integration tests global refactoring: org.jboss.tools.dummy.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23578?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23578: ------------------------------------ Is the request here to remove this bundle? Or change it somehow? Issue title/description are unclear. > Integration tests global refactoring: org.jboss.tools.dummy.ui.bot.test > ----------------------------------------------------------------------- > > Key: JBIDE-23578 > URL: https://issues.jboss.org/browse/JBIDE-23578 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.dummy.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23578) Integration tests global refactoring: org.jboss.tools.dummy.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23578?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23578: ---------------------------------- Assignee: Jeff MAURY > Integration tests global refactoring: org.jboss.tools.dummy.ui.bot.test > ----------------------------------------------------------------------- > > Key: JBIDE-23578 > URL: https://issues.jboss.org/browse/JBIDE-23578 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.dummy.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23580) Integration tests global refactoring: org.jboss.tools.eclipsecs.ui.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23580?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23580: ------------------------------------ Is the request here to remove this bundle? Or change it somehow? Issue title/description are unclear. > Integration tests global refactoring: org.jboss.tools.eclipsecs.ui.test > ----------------------------------------------------------------------- > > Key: JBIDE-23580 > URL: https://issues.jboss.org/browse/JBIDE-23580 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: checkstyle, integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.eclipsecs.ui.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23593) Integration tests global refactoring: remove bundle org.jboss.tools.ui.bot.ext.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23593?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23593: ---------------------------------- Assignee: Martin Malina > Integration tests global refactoring: remove bundle org.jboss.tools.ui.bot.ext.test > ----------------------------------------------------------------------------------- > > Key: JBIDE-23593 > URL: https://issues.jboss.org/browse/JBIDE-23593 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Martin Malina > Labels: integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.ui.bot.ext.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23593) Integration tests global refactoring: remove bundle org.jboss.tools.ui.bot.ext.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23593?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23593: ------------------------------- Summary: Integration tests global refactoring: remove bundle org.jboss.tools.ui.bot.ext.test (was: Integration tests global refactoring: org.jboss.tools.ui.bot.ext.test) > Integration tests global refactoring: remove bundle org.jboss.tools.ui.bot.ext.test > ----------------------------------------------------------------------------------- > > Key: JBIDE-23593 > URL: https://issues.jboss.org/browse/JBIDE-23593 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: integration, integration_tests > Fix For: 4.4.3.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.ui.bot.ext.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21857 at 12/1/16 9:39 AM: ------------------------------------------------------------------- [~mlabuda] Please look into https://issues.jboss.org/secure/attachment/12413672/12413672_hot-code-rep... how JMX gets automatically connected for me. For me the only issue(s) that are left are (as you pointed out, too): * The "Hot Code Replace Failed" dialog always shows up: once you did a structutral change to a class, the "Hot Code Replace Failed" dialog will always show up, prompting you to restart the module. It even shows up if you do non-structural changes. * Non-Structural changes are not applied: Non-structural changes are not applied once you did a structural change, had the module restarted but choose to "Continue" instead of "Restart Module" in further changes. I believe that this 2nd issue is thightly coupled to the 1st one. [~rob.stryker] Comments please? I would therefore resolve this issue and create a new onea for the remaining issues. was (Author: adietish): [~mlabuda] Please look into https://issues.jboss.org/secure/attachment/12413672/12413672_hot-code-rep... how JMX gets automatically connected for me. For me the only issue(s) that are left are (as you pointed out, too): * The "Hot Code Replace Failed" dialog always shows up: once you did a structutral change to a class, the "Hot Code Replace Failed" dialog will always show up, prompting you to restart the module. It even shows up if you do non-structural changes. * Non-Structural changes are not applied: Non-structural changes are not applied once you did a structural change, had the module restarted but choose to "Continue" instead of "Restart Module" in further changes. I believe that this 2nd issue is thightly coupled to the 1st one. [~rob.stryker] Comments please? I would therefore resolve this issue and create a new one for this issue. > Hot code replacement doesn't work on OpenShift > ---------------------------------------------- > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1 > > Attachments: HCRFailure.zip, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21857: ------------------------------------------ [~mlabuda] Please look into https://issues.jboss.org/secure/attachment/12413672/12413672_hot-code-rep... how JMX gets automatically connected for me. For me the only issue(s) that are left are (as you pointed out, too): * The "Hot Code Replace Failed" dialog always shows up: once you did a structutral change to a class, the "Hot Code Replace Failed" dialog will always show up, prompting you to restart the module. It even shows up if you do non-structural changes. * Non-Structural changes are not applied: Non-structural changes are not applied once you did a structural change, had the module restarted but choose to "Continue" instead of "Restart Module" in further changes. I believe that this 2nd issue is thightly coupled to the 1st one. [~rob.stryker] Comments please? I would therefore resolve this issue and create a new one for this issue. > Hot code replacement doesn't work on OpenShift > ---------------------------------------------- > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1 > > Attachments: HCRFailure.zip, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23621) RedDeer build not working - cannot load its own repo

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23621?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23621: --------------------------------------- I temporarily changed the job to skip the archetype deploy maven step (I changed deploy to clean), then ran a new build. It passed and fixed the composite update site - now the child definitions are correct including all/repo/. Now I enabled deploy again and started a new build - I expect it to work. So the question is: What happened? How come the composite site xml was broken? Will it happen again? > RedDeer build not working - cannot load its own repo > ---------------------------------------------------- > > Key: JBIDE-23621 > URL: https://issues.jboss.org/browse/JBIDE-23621 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > The main problem is that the repo is broken: > http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ > compositeArtifacts.xml contains: > child location="2016-11-30_16-31-45-B851/" > But that directory does not contain the repo directly - for it to work, it would need to point to 2016-11-30_16-31-45-B851/all/repo/. > And here are the consequences - broken build of RedDeer: > Today, a build of RedDeer failed: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/reddeer_master/852/ > {code} > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master > [INFO] Fetching compositeContent.xml from http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ (0B of 472B at 0B/s) > [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'RedDeer' from location http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/: Unable to read repository at http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master. No repository found at http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master.... -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'RedDeer' from location http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: java.lang.RuntimeException: Failed to load p2 repository with ID 'RedDeer' from location http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.loadMetadataRepository(TargetPlatformFactoryImpl.java:301) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.gatherExternalInstallableUnits(TargetPlatformFactoryImpl.java:269) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:174) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:126) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:1) > at org.eclipse.tycho.p2.manager.ReactorRepositoryManagerImpl.computePreliminaryTargetPlatform(ReactorRepositoryManagerImpl.java:82) > at org.eclipse.tycho.p2.resolver.P2DependencyResolver.computePreliminaryTargetPlatform(P2DependencyResolver.java:215) > at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:99) > at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > ... 11 more > Caused by: org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master. > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:185) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:59) > at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:52) > at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.loadMetadataRepository(TargetPlatformFactoryImpl.java:297) > ... 21 more > Caused by: org.eclipse.equinox.p2.core.ProvisionException: No repository found at http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master.... > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:59) > at org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:52) > at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166) > ... 30 more > {code} > This was during the maven step which calls deploy on archetype/pom.xml: > https://github.com/jboss-reddeer/reddeer/blob/master/archetype/pom.xml > Inside the archetype test, we add the nightly RedDeer repo: > https://github.com/jboss-reddeer/reddeer/blob/master/archetype/src/main/r... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016