December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21298: ---------------------------------------- If this is the only issue we have for jbosstools-base respin consideration then we can move it to Beta2. Not critical at all. > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component > ---------------------------------------------------------------------- > > Key: JBIDE-21298 > URL: https://issues.jboss.org/browse/JBIDE-21298 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a, testfailure > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:* > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m... > # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds) > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths} > <case> > <age>5</age> > <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className> > <duration>0.0050</duration> > <errorDetails>/qa/services/hudson/jboss-runtimes > expected:<0> but was:<1></errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes > expected:<0> but was:<1> > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.failNotEquals(Assert.java:329) > at junit.framework.Assert.assertEquals(Assert.java:78) > at junit.framework.Assert.assertEquals(Assert.java:234) > at junit.framework.TestCase.assertEquals(TestCase.java:401) > at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73) > </errorStackTrace> > <failedSince>58</failedSince> > <name>testLoadSaveRuntimePaths</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18575) Unable to generate entities for JPA 2.0 project when moving project from JPA 2.1 to JPA 2.0

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18575?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18575: ----------------------------------- Labels: (was: respin-a) > Unable to generate entities for JPA 2.0 project when moving project from JPA 2.1 to JPA 2.0 > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18575 > URL: https://issues.jboss.org/browse/JBIDE-18575 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.CR2 > Environment: JBDS 8.0.0.CR2 > Reporter: Jiri Peterka > Fix For: 4.2.x, 4.3.x > > > org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.tool.Version > Could not initialize class org.hibernate.tool.Version -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18575) Unable to generate entities for JPA 2.0 project when moving project from JPA 2.1 to JPA 2.0

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18575?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18575: -------------------------------------- Assignee: Koen Aers > Unable to generate entities for JPA 2.0 project when moving project from JPA 2.1 to JPA 2.0 > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18575 > URL: https://issues.jboss.org/browse/JBIDE-18575 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.CR2 > Environment: JBDS 8.0.0.CR2 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.2.x, 4.3.x > > > org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > org.hibernate.console.HibernateConsoleRuntimeException: Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > Received a NoClassDefFoundError, probably the console configuration classpath is incomplete or contains conflicting versions of the same class > java.lang.NoClassDefFoundError: Could not initialize class org.hibernate.tool.Version > Could not initialize class org.hibernate.tool.Version -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21321) Refresh does nothing on watch updates for deployment version of explorer view

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-21321: ------------------------------------- Summary: Refresh does nothing on watch updates for deployment version of explorer view Key: JBIDE-21321 URL: https://issues.jboss.org/browse/JBIDE-21321 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Jeff Cantrill Watch and update is broken for new deployment view -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19178: --------------------------------------- !Initial deployment view.png! [~fbricon] Per our conversation, this adds a very simplified deployment view. Refresh does not work in conjunction with watch, more tabs need to be flushed out, lots of work here. > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Initial deployment view.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19178: ---------------------------------- Attachment: Initial deployment view.png > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Initial deployment view.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-3549: ------------------------------ Labels: new_and_noteworthy (was: ) > Developer - start and stop the CDK easily from within the IDE > ------------------------------------------------------------- > > Key: JBDS-3549 > URL: https://issues.jboss.org/browse/JBDS-3549 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > User Story: > As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly. > Acceptance Criteria: > * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse > * If CDK is running, clicking stop should halt the CDK and docker > * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21043) Create a credentialing framework

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21043?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21043: -------------------------------- Labels: new_and_noteworthy (was: ) > Create a credentialing framework > -------------------------------- > > Key: JBIDE-21043 > URL: https://issues.jboss.org/browse/JBIDE-21043 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: JBIDE-21043.png, JBIDE-21043a.png > > > There should be a unified framework for storing credentials to various domains. As of now, download runtimes (in astools) requires redhat or jboss credentials, and I've heard that others are also storing the credentials for some of those domains as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21043) Create a credentialing framework

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21043?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-21043. ------------------------------- Resolution: Done > Create a credentialing framework > -------------------------------- > > Key: JBIDE-21043 > URL: https://issues.jboss.org/browse/JBIDE-21043 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: JBIDE-21043.png, JBIDE-21043a.png > > > There should be a unified framework for storing credentials to various domains. As of now, download runtimes (in astools) requires redhat or jboss credentials, and I've heard that others are also storing the credentials for some of those domains as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21309) install tests should perform installs on minimum and maximum TPs, and report on which there are failures

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21309?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21309: ------------------------------------ p2director jobs can't do remediation so fail to install latest JBT 4.3.1 (requires Mars.1) onto a Mars.0 (aka Mars.R) Eclipse install. {code} 13:25:30 [p2.dir] Only one of the following can be installed at once: 13:25:30 [p2.dir] Equinox Security Default UI 1.1.200.v20130626-2037 (org.eclipse.equinox.security.ui 1.1.200.v20130626-2037) 13:25:30 [p2.dir] Equinox Security Default UI 1.1.201.v20150803-1228 (org.eclipse.equinox.security.ui 1.1.201.v20150803-1228) {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Similar problem for latest JBT 4.4 (Neon.M3) install onto a Neon.M2 Eclipse: {code}14:18:16 [p2.dir] Only one of the following can be installed at once: 14:18:16 [p2.dir] Core Runtime 3.12.0.v20151014-1537 (org.eclipse.core.runtime 3.12.0.v20151014-1537) 14:18:16 [p2.dir] Core Runtime 3.12.0.v20150912-0621 (org.eclipse.core.runtime 3.12.0.v20150912-0621) {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... HOWEVER... install-grinder CAN perform remediation, so we now have tests installing on both Mars.0 + Mars1 and Neon.M2 + Neon.M3: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=143 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=3738 > install tests should perform installs on minimum and maximum TPs, and report on which there are failures > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21309 > URL: https://issues.jboss.org/browse/JBIDE-21309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > Currently, we run the install tests on the maximum TP using the latest Eclipse JEE or Platform Binary. > If we can't do an install against Mars.0 (only Mars.1) due to the fact that the Mars.0 install requires remediation, we should have those tests to show the failure, and log that in the N&N. > Also, if install-grinder can support p2 remediation, that would be awesome too as we could verify that use case too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2015