November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23566) Include integration-tests zip in staging and stable update sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23566?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23566: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > Include integration-tests zip in staging and stable update sites > ---------------------------------------------------------------- > > Key: JBIDE-23566 > URL: https://issues.jboss.org/browse/JBIDE-23566 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.3.AM1 > > > This will allow us the use case of running integration tests against the latest release of devstudio. This use case is required by EAP QE running our tests against their EAP development builds. > Currently we have this repo: > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We're referencing it from our root pom: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > And set up a repository definition for it. > This allows us to run an individual test bundle. > This is mostly useful to satisfy test dependencies - tests depend on RedDeer as a whole which is in the target platform. But most tests also have a RedDeer extension in the plugins directory: > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > With that, let's move on to why it would be useful to have a stable repo for this, e.g. http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests/ > Imagine you want to run integration tests against the latest stable build. If you just checkout the integration tests and run a test plugin (using mvn verify), it will use everything from the latest nightly repos. > So to use latest stable release (jbt 4.4.1.Final / devstudio 10.1.0.GA), you need a couple of things: > 1. Checkout the corresponding branch of the integration tests - jbosstools-4.4.1.x in this case > 2. Make sure the proper devstudio is used to test against: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > -Ddevstudio.repository=https://devstudio.redhat.com/10.0/stable/updates > This also includes the TP, so RedDeer should be the correct version > 3. Make sure the proper integration-tests repo is used for dependencies > Now this is what we currently don't have. Our root pom will set up the snapshots repo: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > So that's why I would like to have a stable repo of this which I could use. > There is a workaround - run "mvn install" on the whole integration-tests repo before you run your test. This will install the correct version in your local repo and that may be then used by your test. But maven will probably still prefer the newer versions from the snapshots repo that is set up in the pom. > To give you an example what can break when you use the newest org.jboss.ide.eclipse.as.reddeer plugin, but run the EAP tests against devstudio 10.1.0.GA: > The EAP 7 server adapter had 7.0 in the type name in 10.1.0.GA, but in current master it's 7.x (to accommodate for the upcoming EAP 7.1). So if you want to test EAP 7.0.1 CP candidate build against devstudio 10.1.0.GA it will fail on this. > Sorry for the lengthy explanation, but I hope it's now clear why I'm requesting this. > Also, I'd be happy to hear if you have some suggestions how to do it differently. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23384) Include integration-tests in staging and stable update sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23384?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23384: ------------------------------------ Let me know when you've merged the PR > Include integration-tests in staging and stable update sites > ------------------------------------------------------------ > > Key: JBIDE-23384 > URL: https://issues.jboss.org/browse/JBIDE-23384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.2.Final > > > This will allow us the use case of running integration tests against the latest release of devstudio. This use case is required by EAP QE running our tests against their EAP development builds. > Currently we have this repo: > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We're referencing it from our root pom: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > And set up a repository definition for it. > This allows us to run an individual test bundle. > This is mostly useful to satisfy test dependencies - tests depend on RedDeer as a whole which is in the target platform. But most tests also have a RedDeer extension in the plugins directory: > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > With that, let's move on to why it would be useful to have a stable repo for this, e.g. http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests/ > Imagine you want to run integration tests against the latest stable build. If you just checkout the integration tests and run a test plugin (using mvn verify), it will use everything from the latest nightly repos. > So to use latest stable release (jbt 4.4.1.Final / devstudio 10.1.0.GA), you need a couple of things: > 1. Checkout the corresponding branch of the integration tests - jbosstools-4.4.1.x in this case > 2. Make sure the proper devstudio is used to test against: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > -Ddevstudio.repository=https://devstudio.redhat.com/10.0/stable/updates > This also includes the TP, so RedDeer should be the correct version > 3. Make sure the proper integration-tests repo is used for dependencies > Now this is what we currently don't have. Our root pom will set up the snapshots repo: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > So that's why I would like to have a stable repo of this which I could use. > There is a workaround - run "mvn install" on the whole integration-tests repo before you run your test. This will install the correct version in your local repo and that may be then used by your test. But maven will probably still prefer the newer versions from the snapshots repo that is set up in the pom. > To give you an example what can break when you use the newest org.jboss.ide.eclipse.as.reddeer plugin, but run the EAP tests against devstudio 10.1.0.GA: > The EAP 7 server adapter had 7.0 in the type name in 10.1.0.GA, but in current master it's 7.x (to accommodate for the upcoming EAP 7.1). So if you want to test EAP 7.0.1 CP candidate build against devstudio 10.1.0.GA it will fail on this. > Sorry for the lengthy explanation, but I hope it's now clear why I'm requesting this. > Also, I'd be happy to hear if you have some suggestions how to do it differently. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Workaround Description: {code}export GDK_BACKEND=x11 ./eclipse{code} Workaround: Workaround Exists > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Reporter: cube 00 > Priority: Critical > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4204: ---------------------------------- Workaround when using Wayland / Fedora 25: https://coffeeorientedprogramming.com/2016/10/06/make-applications-eclips... {code}export GDK_BACKEND=x11 ./eclipse{code} > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Reporter: cube 00 > Priority: Critical > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Component/s: upstream > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Reporter: cube 00 > Priority: Critical > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22376. --------------------------------- Verified in DevStudio 10.2.0.GA Build id: GA-v20161125-1418-B55. > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx, openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Rob Stryker > Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1 > > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22320) Update Openshift EAP/Wildfly Images to Enable JMX

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22320?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22320. --------------------------------- > Update Openshift EAP/Wildfly Images to Enable JMX > ------------------------------------------------- > > Key: JBIDE-22320 > URL: https://issues.jboss.org/browse/JBIDE-22320 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > The EAP image for Openshift does not allow a connection to the jmx remoting port. We need changes to the startup scripts to allow opening the jmx connection -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23546) Base New and Noteworthy for 4.4.2.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23546?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23546. ------------------------------ > Base New and Noteworthy for 4.4.2.Final > ----------------------------------------------------- > > Key: JBIDE-23546 > URL: https://issues.jboss.org/browse/JBIDE-23546 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, foundation, usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.2.Final > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Base 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 Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Base 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 'JBIDE-56789 #comment Create N&N for Base4.4.2.Final #close', 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 Base for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of Base, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-995) Issues with installing IS 10.0.0.GA via Marketplace into Neon-1a

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-995?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-995: -------------------------------- Assignee: Paul Leacu > Issues with installing IS 10.0.0.GA via Marketplace into Neon-1a > ---------------------------------------------------------------- > > Key: JBTIS-995 > URL: https://issues.jboss.org/browse/JBTIS-995 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.GA > Environment: Eclipse Neon-1a for JavaEE Developers > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: error.txt > > > The following error occurs if I try to install Devstudio IS 10.0.0.GA via Marketplace into Eclipse Neon-1a for JavaEE Developers [^error.txt] > Note that I'm still able to continue with the installation and all features from IS are installed successfully. > Another issue here is that after completing the installation process there are BPEL bundles in version 1.1.0.Final (instead of 1.0.5.Final). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23546) Base New and Noteworthy for 4.4.2.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23546?page=com.atlassian.jira.plugi... ] Jeff MAURY resolved JBIDE-23546. -------------------------------- Fix Version/s: 4.4.2.Final Resolution: Rejected > Base New and Noteworthy for 4.4.2.Final > ----------------------------------------------------- > > Key: JBIDE-23546 > URL: https://issues.jboss.org/browse/JBIDE-23546 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, foundation, usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.2.Final > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Base 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 Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Base 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 'JBIDE-56789 #comment Create N&N for Base4.4.2.Final #close', 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 Base for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of Base, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 November 2016