September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-3879. ------------------------------ Resolution: Done Closing as verified in: Version: 10.2.0.AM1 Build id: AM1-v20160923-1714-B6096 Build date: 20160923-1714 > AERI - Closing the 'configure projects' dialog disables enabled projects > ------------------------------------------------------------------------ > > Key: JBDS-3879 > URL: https://issues.jboss.org/browse/JBDS-3879 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: aeri, target-platform > Affects Versions: 10.0.0.Alpha1 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160430-1625-B5264 > Build date: 20160430-1625 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 10.2.0.AM1 > > Attachments: after.png, before.png > > > To recreate: > * Navigate to: Preferences->General->Error Reporting > * Open 'configure projects' dialog > * Enable one or more projects, click on "Enable" > * Open 'configure projects' dialog > * Close the dialog (select the 'x' at upper right) > * Open 'configure projects' dialog > * Observe that the selections are now disabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23189) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23189?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23189: --------------------------------------- [~ldimaggio], this JIRA was generated by a script, along with many others (see subtasks of JBIDE-23185 ). None of them has the Affects Versions set. If you think it should (I don't have a strong opinion on this, but I would say that it's not really necessary), you can create a JIRA for Nick to add it to the script. > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests] > --------------------------------------------------------------------------- > > Key: JBIDE-23189 > URL: https://issues.jboss.org/browse/JBIDE-23189 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Friendly Jira Robot > Assignee: Len DiMaggio > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Integration Tests]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-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} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23189) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests]

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23189?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-23189: --------------------------------- Affects Version/s: 4.4.2.AM1 > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests] > --------------------------------------------------------------------------- > > Key: JBIDE-23189 > URL: https://issues.jboss.org/browse/JBIDE-23189 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Friendly Jira Robot > Assignee: Len DiMaggio > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Integration Tests]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-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} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23189) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests]

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23189?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-23189. -------------------------------- Resolution: Done > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests] > --------------------------------------------------------------------------- > > Key: JBIDE-23189 > URL: https://issues.jboss.org/browse/JBIDE-23189 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Friendly Jira Robot > Assignee: Len DiMaggio > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Integration Tests]: 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 branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-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} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23062) Update arquillian bot tests to run on Central CI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23062?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-23062: --------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Update arquillian bot tests to run on Central CI > ------------------------------------------------ > > Key: JBIDE-23062 > URL: https://issues.jboss.org/browse/JBIDE-23062 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.4.1.AM3 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23036. -------------------------------- Resolution: Rejected Rejected in favour of JBIDE-19911. If you want this instead of JBIDE-19911, state your case and convince Alexey and Mickael. > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.GA > > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3978) Getting started page shows guide for Devstudio 9.x

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-3978?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-3978: ------------------------------------- After-installation link at the Get started section called "Learn how to create your first CDK project" (just making sure that we are talking about correct getting started link) leads to http://developers.redhat.com/products/cdk/get-started/, link is valid but isn't it strange that we are referring user to the page where he learns what he has just done (Steps to install devsuite)? > Getting started page shows guide for Devstudio 9.x > -------------------------------------------------- > > Key: JBDS-3978 > URL: https://issues.jboss.org/browse/JBDS-3978 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.GA > > > The getting started link in devsuite leads to http://developers.redhat.com/devstudio-preview which redirects to https://access.redhat.com/articles/2255401 > The very fact that it is named > {noformat}Using JBoss Developer Studio 9.x's Container Development Kit Tooling {noformat} - refers to CDK 2.0 and JBoss Developer Studio 9.0 - looks suspicious. There might not be much difference to the current workflow, but it definitely is worth updating, especially since the devsuite installer is no longer a Technology Preview. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-914) Integration Stack features have incorrect versions

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-914?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-914. ------------------------------ Fix Version/s: 9.0.2.CR2 Resolution: Done the generated version needs .qualifier in the meta-data which needs -SNAPSHOT in the version. This is then overwritten in the build command line. https://github.com/jbosstools/jbosstools-integration-stack/commit/410026d... > Integration Stack features have incorrect versions > -------------------------------------------------- > > Key: JBTIS-914 > URL: https://issues.jboss.org/browse/JBTIS-914 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.2.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.2.CR2 > > > |com.jboss.devstudio.integration-stack.bpr.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.ds.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.fuse.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.soa.feature|9.0.2.CR1| > The version should be something like *9.0.1.GA-v20160808-1454-B27* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-23036: --------------------------------------- [~nickboldt] you marked this issue a 'done' but is it done or abandoned ? > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.GA > > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-903) Update Dynamic VDB test script

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-903?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-903. ------------------------------ PR was pushed to master > Update Dynamic VDB test script > ------------------------------ > > Key: JBTIS-903 > URL: https://issues.jboss.org/browse/JBTIS-903 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.1.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.2.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016