June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3929) Tweaks to content.xml / artifacts.xml lost (regression)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3929?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3929: ----------------------------- Fix Version/s: 10.0.0.GA > Tweaks to content.xml / artifacts.xml lost (regression) > ------------------------------------------------------- > > Key: JBDS-3929 > URL: https://issues.jboss.org/browse/JBDS-3929 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 10.0.0.GA > > Attachments: jbt-uncat.png, uncategorized_20160614.png > > > The category 'Uncategorized' is on the following update site > https://devstudio.redhat.com/10.0/staging/updates/ > Note that this category contains source features which should not be in any category. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22601) "Unable to choose a subsystem" error when trying to start a remote server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22601?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22601: ---------------------------------- Labels: respin-b (was: ) > "Unable to choose a subsystem" error when trying to start a remote server > ------------------------------------------------------------------------- > > Key: JBIDE-22601 > URL: https://issues.jboss.org/browse/JBIDE-22601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-b > Fix For: 4.4.0.Final > > > When you set up a remote EAP 6 or 7 server and then try to run it, you get this error: > Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.eap.61 and system type deploymentOptions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22601) "Unable to choose a subsystem" error when trying to start a remote server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22601?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22601: ---------------------------------- Priority: Blocker (was: Major) > "Unable to choose a subsystem" error when trying to start a remote server > ------------------------------------------------------------------------- > > Key: JBIDE-22601 > URL: https://issues.jboss.org/browse/JBIDE-22601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.4.0.Final > > > When you set up a remote EAP 6 or 7 server and then try to run it, you get this error: > Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.eap.61 and system type deploymentOptions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22601) "Unable to choose a subsystem" error when trying to start a remote server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22601?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22601: --------------------------------------- I can replicate this in devstudio-10.0.0.GA-v20160613-1243-B18-installer-standalone.jar and a nightly build of JBoss Tools. > "Unable to choose a subsystem" error when trying to start a remote server > ------------------------------------------------------------------------- > > Key: JBIDE-22601 > URL: https://issues.jboss.org/browse/JBIDE-22601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Final > > > When you set up a remote EAP 6 or 7 server and then try to run it, you get this error: > Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.eap.61 and system type deploymentOptions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22601) "Unable to choose a subsystem" error when trying to start a remote server

by Martin Malina (JIRA)

Martin Malina created JBIDE-22601: ------------------------------------- Summary: "Unable to choose a subsystem" error when trying to start a remote server Key: JBIDE-22601 URL: https://issues.jboss.org/browse/JBIDE-22601 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.0.Final Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.4.0.Final When you set up a remote EAP 6 or 7 server and then try to run it, you get this error: Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.eap.61 and system type deploymentOptions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22562) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22562?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22562: ------------------------------------ If it's not going to be used in future, then please update all the various .py scripts [1, 2] that generate jiras so they exclude playground in future, plus remove the playground_master job. [1] https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... [2] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... [3] https://github.com/jbdevstudio/jbdevstudio-ci/tree/master/cache/https/jen... Then you can resolve this issue. > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground] > ------------------------------------------------------------- > > Key: JBIDE-22562 > URL: https://issues.jboss.org/browse/JBIDE-22562 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Playground]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22557) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22557?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22557: ------------------------------- Story Points: 7 (was: 1) > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22557 > URL: https://issues.jboss.org/browse/JBIDE-22557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-784) Include New SAP Tooling and SAP Data Layer for Mars branch

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-784?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-784: ---------------------------------- The ide-config.properties entry is correct - it doesn't want to point to a versioned composite. Looks like the parent pom is set to pick up the Fuse SAP data layer correctly. Use https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-fuse-sap-... to build/ push to staging. You can then test by overriding the jboss.discovery.site.integration-stack-sap.url ide-config.properties variable - i.e. ./jbdevstudio -Djboss.discovery.site.integration-stack-sap.url=http://download.jboss.org/jbosstools/builds/staging/jbosstools-fuse-sap-tooling/all/ Once this works we can look at the Jenkins job - it's still using thje old publish script. > Include New SAP Tooling and SAP Data Layer for Mars branch > ---------------------------------------------------------- > > Key: JBTIS-784 > URL: https://issues.jboss.org/browse/JBTIS-784 > Project: JBoss Tools Integration Stack > Issue Type: Component Upgrade > Components: distribution, Fuse IDE > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > I don't know how to process exactly. > Do I modify the URl here? https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > There is currently no new Tag. > We need to pick the 6.3.0-SNAPSHOT for SAP Data Layer from this update site: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... > The SAP Tooling should be retrieved from http://download.jboss.org/jbosstools/mars/integration/updates/integration... > Where do I need to modify something to be able to test it? > When teher will be a release, I will need to update again the file? or there some automatic mechanism possible? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-784) Include New SAP Tooling and SAP Data Layer for Mars branch

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-784?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBTIS-784: --------------------------------------- Decision to stick with Mars or Neon is not on my own for now. i don't really take part to the discussions and decisions. Te target is first Mars because the project quite abandoned since several months and still based on Luna. I'm trying to upgrade step by step. For the Alpha instead of Beta, there was no releasable work at that time so we stayed with Alpha. If I understand well we absolutely need a tagged version to provide new URL? > Include New SAP Tooling and SAP Data Layer for Mars branch > ---------------------------------------------------------- > > Key: JBTIS-784 > URL: https://issues.jboss.org/browse/JBTIS-784 > Project: JBoss Tools Integration Stack > Issue Type: Component Upgrade > Components: distribution, Fuse IDE > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > I don't know how to process exactly. > Do I modify the URl here? https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > There is currently no new Tag. > We need to pick the 6.3.0-SNAPSHOT for SAP Data Layer from this update site: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... > The SAP Tooling should be retrieved from http://download.jboss.org/jbosstools/mars/integration/updates/integration... > Where do I need to modify something to be able to test it? > When teher will be a release, I will need to update again the file? or there some automatic mechanism possible? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-746) Rework test suites for Teiid Designer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-746?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky resolved JBTIS-746. ------------------------------------- Resolution: Done > Rework test suites for Teiid Designer > ------------------------------------- > > Key: JBTIS-746 > URL: https://issues.jboss.org/browse/JBTIS-746 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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