February 2017 - jbosstools-issues

[JBoss JIRA] (JBTIS-1022) Incorrect version format used in Devstudio IS 10.1.0.CR1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1022?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1022. ------------------------------------ Verified with Devstudio IS 10.1.0.CR1. |com.jboss.devstudio.integration-stack.bpr.feature | 10.1.0.CR1-v20170125-1343-B270| |com.jboss.devstudio.integration-stack.ds.feature | 10.1.0.CR1-v20170125-1343-B270| |com.jboss.devstudio.integration-stack.fuse.feature | 10.1.0.CR1-v20170125-1343-B270| |com.jboss.devstudio.integration-stack.soa.feature | 10.1.0.CR1-v20170125-1343-B270| > Incorrect version format used in Devstudio IS 10.1.0.CR1 > -------------------------------------------------------- > > Key: JBTIS-1022 > URL: https://issues.jboss.org/browse/JBTIS-1022 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.1.0.CR1 > > Attachments: new1.png > > > Incorrect version format used in Devstudio IS 10.1.0.CR1. > |com.jboss.devstudio.integration-stack.bpr.feature | 10.1.0.2017-01-20_21-45-27-v20170120-2209-B267| > |com.jboss.devstudio.integration-stack.ds.feature | 10.1.0.2017-01-20_21-45-27-v20170120-2209-B267| > |com.jboss.devstudio.integration-stack.fuse.feature | 10.1.0.2017-01-20_21-45-27-v20170120-2209-B267| > |com.jboss.devstudio.integration-stack.soa.feature | 10.1.0.2017-01-20_21-45-27-v20170120-2209-B267| > Please see JBTIS-471 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1036) Fuse - Fix SAP tests

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1036?page=com.atlassian.jira.plugin... ] Tomáš Sedmík closed JBTIS-1036. ------------------------------- Resolution: Done PR was pushed to master > Fuse - Fix SAP tests > -------------------- > > Key: JBTIS-1036 > URL: https://issues.jboss.org/browse/JBTIS-1036 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.1.CR1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > There are errors in the SAP tests. It seems that the config.xml is not correctly mapped to Java objects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1026) Extend and use Runtime annotation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1026?page=com.atlassian.jira.plugin... ] Jozef Marko updated JBTIS-1026: ------------------------------- Parent: (was: JBTIS-1021) Issue Type: Task (was: Sub-task) > Extend and use Runtime annotation > --------------------------------- > > Key: JBTIS-1026 > URL: https://issues.jboss.org/browse/JBTIS-1026 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.4.0.Final > Reporter: Jozef Marko > Assignee: Dominik Hanak > > Replace the usage of > {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} > with > {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} > * The annotation corresponding to RuntimeRequirement is used for example here [1]. > * How to run tests that uses this kind of annotation is shown here [2]. > ** Notice there is maven goal over the *server-installer* repository > ** Explore content of *server-installer* modules that are built > ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. > The annotation currently supports only downloading of brms-runtime classes. However , support for bpms-runtime classes will be pretty similar to support of brms and just few changes will be needed at these places: > * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > * https://github.com/jbosstools/jbosstools-integration-stack-tests/tree/mas... > * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > * https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jbdsis/server-installer/... > [1] > https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > [2] > https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... > [3] > -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config > [4] > https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-981) NumberFormatException if you select more features to install

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-981?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-981. ----------------------------------- Verified with devstudio-integration-stack-10.1.0.CR1-standalone-installer.jar > NumberFormatException if you select more features to install > ------------------------------------------------------------ > > Key: JBTIS-981 > URL: https://issues.jboss.org/browse/JBTIS-981 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Environment: devstudio-is-installer-10.0.0-SNAPSHOT.jar > devstudio-is-runtime-installer-10.0.0-SNAPSHOT.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.1.0.GA > > > {code} > java.lang.NumberFormatException: For input string: "null" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Long.parseLong(Long.java:589) > at java.lang.Long.parseLong(Long.java:631) > at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.calculateAggregateSize(DiskSpaceCheckPanel.java:71) > at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.getInstallationSize(DiskSpaceCheckPanel.java:94) > at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.panelActivate(DiskSpaceCheckPanel.java:36) > at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864) > at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475) > at com.izforge.izpack.installer.InstallerFrame.skipPanel(InstallerFrame.java:1401) > at com.jboss.devstudio.core.installer.UpdatePacksPanel.panelActivate(UpdatePacksPanel.java:25) > at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864) > at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475) > at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1443) > at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionPerformed(InstallerFrame.java:1585) > at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022) > at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348) > at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402) > at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259) > at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252) > at java.awt.Component.processMouseEvent(Component.java:6535) > at javax.swing.JComponent.processMouseEvent(JComponent.java:3324) > at java.awt.Component.processEvent(Component.java:6300) > at java.awt.Container.processEvent(Container.java:2236) > at java.awt.Component.dispatchEventImpl(Component.java:4891) > at java.awt.Container.dispatchEventImpl(Container.java:2294) > at java.awt.Component.dispatchEvent(Component.java:4713) > at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888) > at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525) > at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466) > at java.awt.Container.dispatchEventImpl(Container.java:2280) > at java.awt.Window.dispatchEventImpl(Window.java:2750) > at java.awt.Component.dispatchEvent(Component.java:4713) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) > at java.awt.EventQueue.access$500(EventQueue.java:97) > at java.awt.EventQueue$3.run(EventQueue.java:709) > at java.awt.EventQueue$3.run(EventQueue.java:703) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76) > at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) > at java.awt.EventQueue$4.run(EventQueue.java:731) > at java.awt.EventQueue$4.run(EventQueue.java:729) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) > at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) > at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21895: ------------------------------------- Description: 1) Create e.g. node application in a openshift project 2) Right click from project explorer -> Delete the application 3) repeat step 1) Result: !Screen Shot 2016-03-17 at 16.19.05.png! was: 1) Create e.g. node application in a openshift project 2) Right click from project explorer -> Delete the application 3) repeat step 1) > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Fix For: 4.4.3.Final > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) > Result: > !Screen Shot 2016-03-17 at 16.19.05.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21895: ------------------------------------- Summary: Application wizard: Resource name collisions after deleting and recreating the application (was: Resource name collisions after deleting and recreating the application) > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Fix For: 4.4.3.Final > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23841) Properties view: "Details" tab wont tell you what kind of resource it's showing details for

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23841?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23841: ---------------------------------------- Assignee: Andre Dietisheim > Properties view: "Details" tab wont tell you what kind of resource it's showing details for > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23841 > URL: https://issues.jboss.org/browse/JBIDE-23841 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, properties > Fix For: 4.4.3.Final > > Attachments: properties-details-resource-type-missing.png > > > steps: > # ASSERT: make sure that you have an application in your OpenShift server > # EXEC: in OpenShift explorer: select your (application-) service and > # EXEC: open the Properties view and select the "Details" tab > # EXEC: try to figure out what kind of resource you are inspecting the details of > Result: > You have no indication for the kind of resource that is selected in the explorer > !properties-details-resource-type-missing.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23859) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [openshift]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created JBIDE-23859: ------------------------------------------- Summary: For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [openshift] Key: JBIDE-23859 URL: https://issues.jboss.org/browse/JBIDE-23859 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Reporter: Friendly Jira Robot Priority: Blocker Fix For: 4.4.3.Final For JBIDE 4.4.3.Final [openshift]: 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.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.3.Final-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.26.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.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.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 openshift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23855) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [visual-page-editor-core]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created JBIDE-23855: ------------------------------------------- Summary: For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [visual-page-editor-core] Key: JBIDE-23855 URL: https://issues.jboss.org/browse/JBIDE-23855 Project: Tools (JBoss Tools) Issue Type: Task Components: visual-page-editor-core Reporter: Friendly Jira Robot Priority: Blocker Fix For: 4.4.3.Final For JBIDE 4.4.3.Final [visual-page-editor-core]: 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.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.3.Final-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.26.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.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.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 visual-page-editor-core task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23856) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [webservices]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created JBIDE-23856: ------------------------------------------- Summary: For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [webservices] Key: JBIDE-23856 URL: https://issues.jboss.org/browse/JBIDE-23856 Project: Tools (JBoss Tools) Issue Type: Task Components: webservices Reporter: Friendly Jira Robot Priority: Blocker Fix For: 4.4.3.Final For JBIDE 4.4.3.Final [webservices]: 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.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.3.Final-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.26.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.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.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 webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017