March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-295) utilize the tycho testing support for test bundles on JBTIS

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-295?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-295. ----------------------------------- Set a long time ago, so I will close this issue. > utilize the tycho testing support for test bundles on JBTIS > ----------------------------------------------------------- > > Key: JBTIS-295 > URL: https://issues.jboss.org/browse/JBTIS-295 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: testing > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Fix For: 9.0.1.GA, 10.0.0.GA > > > Talking with [~rcernich] he was interested in doing testing of already packaged bundles on a packaged eclipse. > [~mickael_istria] did this feature for tycho 0.19 documented at http://wiki.eclipse.org/Tycho/Release_Notes/0.19#Test_Execution > [~rcernich] would this cover you intended use case ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-910) SwitchYard publish job does not promote to the correct directory

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-910?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-910. ----------------------------------- Fixed a long time ago, so I will close this issue > SwitchYard publish job does not promote to the correct directory > ---------------------------------------------------------------- > > Key: JBTIS-910 > URL: https://issues.jboss.org/browse/JBTIS-910 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: switchyard > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.2.GA > > > The SY build Jenkins job correctly creates 2.1.0.CR1 but the publish job promotes it to 2.1.0 > ref: > http://download.jboss.org/jbosstools/mars/integration/updates/integration... > should be > http://download.jboss.org/jbosstools/mars/integration/updates/integration... > https://10.8.63.16/job/SwitchYard-Tools-2.1.x-Update-Site/34/ > https://10.8.63.16/job/SwitchYard-Tools-2.1.x-Update-Site-Publish/22/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1002) Progress bar still indicates that the installation is in progress even if it is done

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1002?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1002. ------------------------------------ Neither I'm able to reproduce this issue, so I will close this issue. > Progress bar still indicates that the installation is in progress even if it is done > ------------------------------------------------------------------------------------ > > Key: JBTIS-1002 > URL: https://issues.jboss.org/browse/JBTIS-1002 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Environment: devstudio-is-fuse-runtime-installer-10.1.1-SNAPSHOT.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: inst-proc2.png, installer_progress.png > > > Progress bar still indicates that the installation is in progress even if it is done. Please see the attached screenshot and notice that the button 'Next' is enabled (the installation is done). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23427) Broken icon in hibernate properties editor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23427?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-23427: ----------------------------------- This is weird, I guess I'll need to find a Fedora machine to try and reproduce it. > Broken icon in hibernate properties editor > ------------------------------------------ > > Key: JBIDE-23427 > URL: https://issues.jboss.org/browse/JBIDE-23427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.2.AM2 > Environment: Fedora 24 w/ JDK 8u65: > {code} > $➔ uname -a; java -version > Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > {code} > Reporter: Nick Boldt > Assignee: Koen Aers > Fix For: 4.5.0.AM1 > > Attachments: Schermafbeelding 2017-03-20 om 17.31.45.png, hib-missing-icon-more.png, hib-missing-icon.log.txt, hib-missing-icon.png, hibernate-menu-missing-icon-property-editor.png > > > There appears to be a missing icon in the properties editor for the Hibernate config file. > Steps to repro: > 0. install devstudio from installer jar, devstudio-10.2.0.AM2-v20161014-1657-B6205-installer-standalone.jar > 1. create a project from File > New > Other > General > Project > 2. select the project then create a hibernate.cfg.xml file using the File > New > Other > Hibernate > Hibernate Configuration File (cfg.xml). > Note the error in the view. > !hibernate-menu-missing-icon-property-editor.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4296) Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ] Lukáš Valach edited comment on JBDS-4296 at 3/24/17 4:41 AM: ------------------------------------------------------------- I managed to implement all requirements but I am not sure if is devstudio really started in strict mode and with -clean. I don't know how to verify if these parameters are taking into account. Both will be verified in JBDS-4295 I guess. Post-install smoke test is started only if both INCLUDED_CONNECTORS and EXCLUDED_CONNECTORS parameters are empty. Jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Devstudi... PR (not merged yet): https://github.com/jbdevstudio/jbdevstudio-qa/pull/132 Test is failing on Fedora 24 + OpenJDK 8 probably because of [this bug.|https://bugzilla.redhat.com/show_bug.cgi?id=1415137] I will create request to update OpenJDK. CC: [~nickboldt] was (Author: lvalach): I managed to implement all requirements but I am not sure if is devstudio really started in strict mode and with -clean. I don't know how to verify if these parameters are taking into account. Both will be verified in JBDS-4295 I guess. Post-install smoke test is started only if both INCLUDED_CONNECTORS and EXCLUDED_CONNECTORS parameters are empty. Jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Devstudi... PR (not merged yet): https://github.com/jbdevstudio/jbdevstudio-qa/pull/132 > Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4296 > URL: https://issues.jboss.org/browse/JBDS-4296 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: integration-tests, rpm > Affects Versions: 10.4.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.AM2 > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar [0], on all three supported OS platforms (RHEL7/Fedora24, Win10, MacOS 10). > This job should be configurable, we want to be able to pass in a different parameters as URLs and then use the same job to test both snapshot and staging. > The job should: > # Install devstudio from installer jar > # Clean and start eclipse in strict mode and in clean work space > # Install all stuff from Red Hat Central *using graphical interface* > ** Install everything at once - this is the fastest approach but also makes diagnosing errors more difficult. > ** So, when problems occur, could re-run the job (manually or with naginator plugin?) using parameter connectorIDsToInstall = "net.sourceforge.pmd.eclipse" for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * installer jar URL (snapshot/staging/stable) [0] > * jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (eg., https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... or https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1... or https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/) > * ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has) > * TESTS_FORK = jbosstools ? > * TEST_BRANCH = master or jbosstools-4.4.x or jbosstools-4.4.4.x ? > * connectorIDsToInstall = "" (install everything found) or specific value [1] for re-running if something fails > [0] https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon... or https://devstudio.jboss.com/static/10.0/stable/builds/devstudio-10.3.0.GA... > [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1064) Remove ModeShape from JBoss Tools website features

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1064?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1064: ------------------------------------- Description: Remove ModeShape from JBoss Tools website features since the ModeShape tooling was removed in Devstudio IS 10.x. http://tools.jboss.org/features/modeshape.html was:Remove ModeShape from JBoss Tools website features since the ModeShape tooling was removed in Devstudio IS 10.x. > Remove ModeShape from JBoss Tools website features > -------------------------------------------------- > > Key: JBTIS-1064 > URL: https://issues.jboss.org/browse/JBTIS-1064 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.1.0.GA > Reporter: Andrej Podhradsky > Fix For: 10.2.0.GA > > > Remove ModeShape from JBoss Tools website features since the ModeShape tooling was removed in Devstudio IS 10.x. > http://tools.jboss.org/features/modeshape.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1064) Remove ModeShape from JBoss Tools website features

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1064: ---------------------------------------- Summary: Remove ModeShape from JBoss Tools website features Key: JBTIS-1064 URL: https://issues.jboss.org/browse/JBTIS-1064 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 10.1.0.GA Reporter: Andrej Podhradsky Fix For: 10.2.0.GA Remove ModeShape from JBoss Tools website features since the ModeShape tooling was removed in Devstudio IS 10.x. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4296) Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4296: ------------------------------------ I managed to implement all requirements but I am not sure if is devstudio really started in strict mode and with -clean. I don't know how to verify if these parameters are taking into account. Both will be verified in JBDS-4295 I guess. Post-install smoke test is started only if both INCLUDED_CONNECTORS and EXCLUDED_CONNECTORS parameters are empty. Jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Devstudi... PR (not merged yet): https://github.com/jbdevstudio/jbdevstudio-qa/pull/132 > Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4296 > URL: https://issues.jboss.org/browse/JBDS-4296 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: integration-tests, rpm > Affects Versions: 10.4.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.AM2 > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar [0], on all three supported OS platforms (RHEL7/Fedora24, Win10, MacOS 10). > This job should be configurable, we want to be able to pass in a different parameters as URLs and then use the same job to test both snapshot and staging. > The job should: > # Install devstudio from installer jar > # Clean and start eclipse in strict mode and in clean work space > # Install all stuff from Red Hat Central *using graphical interface* > ** Install everything at once - this is the fastest approach but also makes diagnosing errors more difficult. > ** So, when problems occur, could re-run the job (manually or with naginator plugin?) using parameter connectorIDsToInstall = "net.sourceforge.pmd.eclipse" for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * installer jar URL (snapshot/staging/stable) [0] > * jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (eg., https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... or https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1... or https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/) > * ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has) > * TESTS_FORK = jbosstools ? > * TEST_BRANCH = master or jbosstools-4.4.x or jbosstools-4.4.4.x ? > * connectorIDsToInstall = "" (install everything found) or specific value [1] for re-running if something fails > [0] https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon... or https://devstudio.jboss.com/static/10.0/stable/builds/devstudio-10.3.0.GA... > [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-839) Please update JBoss Tools website features desc - Fuse Tooling/SY/Fabric8

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-839?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-839. ----------------------------------- Fixed a long time ago, so I will close this issue. > Please update JBoss Tools website features desc - Fuse Tooling/SY/Fabric8 > ------------------------------------------------------------------------- > > Key: JBTIS-839 > URL: https://issues.jboss.org/browse/JBTIS-839 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE > Reporter: Paul Leacu > Assignee: Lars Heinemann > > http://tools.jboss.org/features/apachecamel.html > http://tools.jboss.org/features/fabric8.html > http://tools.jboss.org/features/switchyard.html > The git source repo for the content can be found here: > https://github.com/jbosstools/jbosstools-website/tree/master/features > I'm happy to coordinate updating the repo if you'd like. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1063) Fuse: Fix DebuggerTest

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1063?page=com.atlassian.jira.plugin... ] Tomáš Sedmík updated JBTIS-1063: -------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Fuse: Fix DebuggerTest > ---------------------- > > Key: JBTIS-1063 > URL: https://issues.jboss.org/browse/JBTIS-1063 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE, QE > Affects Versions: 4.4.1.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.2.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > DebuggerTest is failing, if the test is run with RHDS > {code} > DebuggerTest.testConditionalBreakpoints:254 » WaitTimeoutExpired Timeout after... > DebuggerTest.testDebugger:177 » WaitTimeoutExpired Timeout after: 10 s.: Debug... > {code} > The reason is that _Secure Storage Password_ window appeared. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017