October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-502) Include Drools tooling 6.3 to JBDS-IS 9.x

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-502?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-502. ------------------------------ Fix Version/s: 9.0.1.Beta1 4.3.1.Beta1 Resolution: Done Updated drools https://github.com/jbosstools/jbosstools-integration-stack/commit/c6254f5... > Include Drools tooling 6.3 to JBDS-IS 9.x > ----------------------------------------- > > Key: JBTIS-502 > URL: https://issues.jboss.org/browse/JBTIS-502 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.1.Beta1, 4.3.1.Beta1 > > > There is a new version of Drools tooling which is available at http://drools.org/download/download.html > Please include the new Drools tooling to the next build of JBDS-IS 9.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-514) Unknown category 'org.jboss.tools.discovery.certification.supported' when installing from Central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-514?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-514. ------------------------------ Fix Version/s: 4.3.1.Beta1 Resolution: Done Removed erroneous category setting https://github.com/jbosstools/jbosstools-integration-stack/commit/c6254f5... > Unknown category 'org.jboss.tools.discovery.certification.supported' when installing from Central > ------------------------------------------------------------------------------------------------- > > Key: JBTIS-514 > URL: https://issues.jboss.org/browse/JBTIS-514 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Environment: jee-mars-1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 4.3.1.Beta1 > > > After installing BYOE into Eclipse Mars JEE and installing integration tools I got the following error in Error Log > Unknown category 'org.jboss.tools.discovery.certification.supported' referenced by connector 'org.jboss.runtime.drools.detector.feature' declared in org.jboss.tools.central.discovery.integration_stack_4.3.0.Alpha2_v20151006_1928_B438.jar_7070743946524519340.jar > The eclipse instance was run as follows > {code} > ./eclipse -vmargs \ > -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/4.3.0.Alpha2/jbosstools-directory.xml \ > -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery \ > -Djboss.discovery.earlyaccess.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/development/updates/integration-stack/discovery/earlyaccess > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20530) Add docker image lookup to deploy image wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20530?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-20530: ------------------------------------- Assignee: Jeff Cantrill > Add docker image lookup to deploy image wizard > ---------------------------------------------- > > Key: JBIDE-20530 > URL: https://issues.jboss.org/browse/JBIDE-20530 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.Beta1 > > > Add a way to lookup a docker image from deploy an image wizard instead of just freeform text -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20951. --------------------------------- Resolution: Done PR merged -> version bumped to 4.3.1-SNAPSHOT. And repo can be built with the new TP. All the rest is done, too. Closing. > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20951. --------------------------------- Release Notes Text: PR merged -> version bumped to 4.3.1-SNAPSHOT. And repo can be built with the new TP. All the rest is done, too. Closing. Resolution: Done > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-20951: ---------------------------------- Release Notes Text: (was: PR merged -> version bumped to 4.3.1-SNAPSHOT. And repo can be built with the new TP. All the rest is done, too. Closing.) > For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests] > ------------------------------------------------------------------- > > Key: JBIDE-20951 > URL: https://issues.jboss.org/browse/JBIDE-20951 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1 [Integration Tests]: Please perform the following tasks: > If you expect to be doing 4.3.x maintenance work in your component: > 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.) > 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above. > 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds. > [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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-490) Use the extras plugins update site 'extras' for SAP.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-490?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-490. ----------------------------------- Verified with JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR2 (also works with JBDS-IS 8.0.3.GA). > Use the extras plugins update site 'extras' for SAP. > ---------------------------------------------------- > > Key: JBTIS-490 > URL: https://issues.jboss.org/browse/JBTIS-490 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.3.GA, 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.3.GA > > > We currently have this: > https://devstudio.redhat.com/updates/8.0/integration-stack/jboss-fuse-sap... > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > what we want is this: > https://devstudio.redhat.com/updates/8.0/integration-stack/extras > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-524) Update SAP tooling to 7.3.2

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-524: --------------------------------------- Summary: Update SAP tooling to 7.3.2 Key: JBTIS-524 URL: https://issues.jboss.org/browse/JBTIS-524 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 8.0.4.CR2 Reporter: Andrej Podhradsky Priority: Blocker JBDS-IS 8.0.4.CR2 contains Fuse tooling 7.3.2.v20151008-1250-H108-CR2 but SAP tooling is in version 7.3.0.v20150622-1535-H9-Final. Please create a new build of SAP tooling and add it to https://devstudio.redhat.com/updates/8.0/integration-stack/extras -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20978) Connection wizard: switching to <New Connection> resets token but form is still valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20978?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20978: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you have at least 1 (existing) connection listed in the explorer # ASSERT: have a freshly launched Eclipse # EXEC: launch app wizard via link in central (or File->New->OpenShift) # ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values # EXEC: Switch connection combobox to <New Connection> Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. !form-erroneously-valid.png! Expected result: authentication details are blank but marked as required, "Next" is disabled. was: # ASSERT: make sure you have at least 1 (existing) connection listed in the explorer # EXEC: launch app wizard via link in central (or File->New->OpenShift) # ASSERT: your existing connection is preselected and username/pw (or token for a OpenShift v3 connection) are filled with values # EXEC: Switch connection combobox to <New Connection> Result: In case of OpenShift v2 username and password are blank, but not decorated with a "*" marking it as required. The "Next" button is therefore enabled. In case of OpenShift v3 the server url is now blank and decorated with a "*" marking it as required. Username/Password or Token are blank but not marked as required. !form-erroneously-valid.png! Expected result: authentication details are blank but marked as required, "Next" is disabled. > Connection wizard: switching to <New Connection> resets token but form is still valid > ------------------------------------------------------------------------------------- > > Key: JBIDE-20978 > URL: https://issues.jboss.org/browse/JBIDE-20978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, central, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: form-erroneously-valid.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20997) Should not be able to create duplicative labels

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20997?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-20997: ---------------------------------- Description: User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. (was: User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name. But as a result only the last one is created (it looks like others are either ignored or overwrite). It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label.) > Should not be able to create duplicative labels > ----------------------------------------------- > > Key: JBIDE-20997 > URL: https://issues.jboss.org/browse/JBIDE-20997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > > User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 October 2015