September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24916) Aerogear New and Noteworthy for 4.5.1.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24916?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24916: ------------------------------------ [~gercan] Can you process it ? > Aerogear New and Noteworthy for 4.5.1.AM2 > --------------------------------------------------- > > Key: JBIDE-24916 > URL: https://issues.jboss.org/browse/JBIDE-24916 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Jeff MAURY > Assignee: Gorkem Ercan > Priority: Critical > Labels: task > Fix For: 4.5.1.AM2 > > > Gorkem Ercan, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Aerogear 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 Aerogear, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Aerogear 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-24908 #comment Create N&N for Aerogear 4.5.1.AM2 #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 Aerogear for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM (headless)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23882: --------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > Automate test of installation of software from Red Hat Central into devstudio RPM (headless) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM3 > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25010) Fix some issues in CDI tests

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25010?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25010. -------------------------------- > Fix some issues in CDI tests > ---------------------------- > > Key: JBIDE-25010 > URL: https://issues.jboss.org/browse/JBIDE-25010 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > CDI test should run arains AS 7.1 not against EAP 7. Some tests have to be fixed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24900) Configure cdi.it.smoke to have cdi10/cdi11 axis

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24900?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24900: --------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > Configure cdi.it.smoke to have cdi10/cdi11 axis > ----------------------------------------------- > > Key: JBIDE-24900 > URL: https://issues.jboss.org/browse/JBIDE-24900 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM3 > > > CDI.it.smoke \[1\] takes a long (about 4 hours). We can add cdi10/cdi11 axis to run tests parallely. > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24978) easymport.it.smoke tests result in yellow balls on multiple OSes

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24978?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24978: --------------------------------- Fix Version/s: 4.5.1.AM3 > easymport.it.smoke tests result in yellow balls on multiple OSes > ---------------------------------------------------------------- > > Key: JBIDE-24978 > URL: https://issues.jboss.org/browse/JBIDE-24978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Lukáš Valach > Fix For: 4.5.1.AM3 > > Attachments: easyimport.it.smoke.png > > > easymport.it.smoke tests have yellow balls on many OS/JDK combinations. Either we shouldn't run on all these variations, or we should fix the tests :) > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !easyimport.it.smoke.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4499) Multiple versions of org.eclipse.linuxtools.jdt.docker.launcher

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4499?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4499. ------------------------------ > Multiple versions of org.eclipse.linuxtools.jdt.docker.launcher > --------------------------------------------------------------- > > Key: JBDS-4499 > URL: https://issues.jboss.org/browse/JBDS-4499 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 11.0.0.GA > Environment: DevTools repository: http://brewweb.engineering.redhat.com/brewroot/repos/devtools-1.0-rh-ecli... > Devstudio repository: https://devstudio.redhat.com/11/staging/builds/devstudio-11.0.0.GA-build-... > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Fix For: 11.1.0.AM2 > > > I have installed last staged build \[1\] and now I have this error message in the log after start: > {code} > !ENTRY org.eclipse.linuxtools.jdt.docker.launcher 4 0 2017-08-07 12:04:20.933 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.jdt.docker.launcher [1118] > Another singleton bundle selected: osgi.identity; osgi.identity="org.eclipse.linuxtools.jdt.docker.launcher"; type="osgi.bundle"; version:Version="1.0.0.201708031854"; singleton:="true" > at org.eclipse.osgi.container.Module.start(Module.java:444) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > {code} > \[1\] https://devstudio.redhat.com/11/staging/builds/devstudio-11.0.0.GA-build-... > Content of /opt/rh/rh-eclipse47 > {code} > find /opt/rh/rh-eclipse47/ -iname "*org.eclipse.linuxtools.jdt.docker.launcher*" > /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher.source_1.0.0.201708031854.jar > /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher_1.0.0.201708031854.jar > /opt/rh/rh-eclipse47/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.linuxtools.jdt.docker.launcher_1.0.0.201708010032.jar > {code} > I don't see any impact to the user. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24890) hibernate itest org.jboss.tools.hibernate.ui.bot.test can't find mvn-hibernate35-ent/.settings/org.eclipse.wst.common.component (No such file or directory)

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24890?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-24890: ------------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > hibernate itest org.jboss.tools.hibernate.ui.bot.test can't find mvn-hibernate35-ent/.settings/org.eclipse.wst.common.component (No such file or directory) > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24890 > URL: https://issues.jboss.org/browse/JBIDE-24890 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, integration-tests > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.5.1.AM3 > > > {code} > *** ERROR ***: Wed Aug 23 10:55:13 EDT 2017 > org.eclipse.core.internal.resources.ResourceException(/mvn-hibernate35-ent/.settings/org.eclipse.wst.common.component)[368]: > java.io.FileNotFoundException: /mnt/hudson_workspace/workspace/hibernatetools-itests.download-devstudio/ > hibernatetools/itests/org.jboss.tools.hibernate.ui.bot.test/target/mvn-hibernate35-ent/.settings/org.eclipse.wst.common.component > (No such file or directory) > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/hibernat... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4551) 'Select * components to install' message visible when detection started on window activation event

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4551: ----------------------------------- Summary: 'Select * components to install' message visible when detection started on window activation event Key: JBDS-4551 URL: https://issues.jboss.org/browse/JBDS-4551 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 11.1.0.AM2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 11.1.0.AM2 When detection runs after confirmation page shown first time, everything works as expected. Spinner for detection is visible with message under it. After windows loses focus and then gets it back, spinner and message shown again, but message 'We found N installed components..." also stays visible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4550) Detection spinner is not activated after window lost focus and got it back

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4550?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4550: -------------------------------- Summary: Detection spinner is not activated after window lost focus and got it back (was: Detection spinner is not activated after window lost and get focus back) > Detection spinner is not activated after window lost focus and got it back > -------------------------------------------------------------------------- > > Key: JBDS-4550 > URL: https://issues.jboss.org/browse/JBDS-4550 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.1.0.AM2 > > > When windows loses focus and activated back, detection starts again, but there is no spinner this time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24923) Webservices / Rest New and Noteworthy for 4.5.1.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24923?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24923. ------------------------------ Resolution: Rejected > Webservices / Rest New and Noteworthy for 4.5.1.AM2 > --------------------------------------------------- > > Key: JBIDE-24923 > URL: https://issues.jboss.org/browse/JBIDE-24923 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.1.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Webservices / Rest 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 Webservices / Rest, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Webservices / Rest 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-24908 #comment Create N&N for Webservices / Rest 4.5.1.AM2 #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 Webservices / Rest for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017