July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26110) Fuse Tools New and Noteworthy for 4.6.0.Final

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26110?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-26110. -------------------------------- verified with master branch > Fuse Tools New and Noteworthy for 4.6.0.Final > ----------------------------------------------------- > > Key: JBIDE-26110 > URL: https://issues.jboss.org/browse/JBIDE-26110 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Critical > Labels: task > Fix For: 4.6.0.Final > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools 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 Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools 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... {code}JBIDE-26102 #comment Create N&N for Fuse Tools 4.6.0.Final #close{code}... 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 Fuse Tools for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.6.0.Final since the AM3 release of Fuse Tools, 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.6.0.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.6.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26125) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [fusetools-extras]

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26125?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-26125. -------------------------------- verified with master branch > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [fusetools-extras] > ----------------------------------------------------------------------------- > > Key: JBIDE-26125 > URL: https://issues.jboss.org/browse/JBIDE-26125 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [fusetools-extras]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {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 fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26124) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [fusetools]

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26124?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-26124. -------------------------------- verified with master branch > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [fusetools] > ---------------------------------------------------------------------- > > Key: JBIDE-26124 > URL: https://issues.jboss.org/browse/JBIDE-26124 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [fusetools]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {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 fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26084) Explorer: pods are show twice if they're controlled by an rc (no dc, no service)

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26084?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26084. --------------------------------- Closing. Works as expected. Verified in: Red Hat Developer Studio Version: 12.0.0.GA Build id: GA-v20180704-0113-B2949 Build date: 20180704-0113 > Explorer: pods are show twice if they're controlled by an rc (no dc, no service) > -------------------------------------------------------------------------------- > > Key: JBIDE-26084 > URL: https://issues.jboss.org/browse/JBIDE-26084 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: explorer > Fix For: 4.6.0.Final > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2018-06-06-10-33-55-241.png > > > steps: > # EXEC: Create a new application via the following custom template [^eap-without-service-nor-deploymentconfig.json] > # EXEC: look into OpenShift explorer and see where the pods for the application are shown > Result: > They're listed twice, once as pods on their own and a 2nd time as children for the replication controller (that the template creates) > !image-2018-06-06-10-33-55-241.png! > Also see the discussion in the PR Also see discussion for the corresponding [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1748] for JBIDE-24979 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20704) Restore Defaults button in OpenShift 3 preferences does not clear oc location

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20704?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-20704. --------------------------------- Closing. Works as expected. Verified in: Red Hat Developer Studio Version: 12.0.0.GA Build id: GA-v20180704-0113-B2949 Build date: 20180704-0113 > Restore Defaults button in OpenShift 3 preferences does not clear oc location > ----------------------------------------------------------------------------- > > Key: JBIDE-20704 > URL: https://issues.jboss.org/browse/JBIDE-20704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.6.0.Final > > Attachments: restore-defaults.gif > > > In Workbench preference dialog on OpenShift 3 preference page the Restore Defaults button should set default values for a property page but if there is an input in text widget for oc location, the value is not cleared. Upon click on Restore Defaults button the text field still contains the same value as before clicking on the button. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26161) Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26161?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26161: ------------------------------------ Context is that the javaee integration tests were failing on the *mek machines for several months, so we moved it to run on mac_xhyve slaves only and now it's green: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... So there's clearly something missing on the *mek boxes. > Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26161 > URL: https://issues.jboss.org/browse/JBIDE-26161 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Fix For: 4.9.x > > > Take a look and update/repair Mac os machines used in our infra, especially zamek and check out the others: > * domek > * bigmek > * dev-platform-mac1 > * dev-platform-mac2 > cc: [~nickboldt] [~mmalina] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26161) Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26161?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26161: ---------------------------------- Assignee: Ondrej Dockal > Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26161 > URL: https://issues.jboss.org/browse/JBIDE-26161 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.x > > > Take a look and update/repair Mac os machines used in our infra, especially zamek and check out the others: > * domek > * bigmek > * dev-platform-mac1 > * dev-platform-mac2 > cc: [~nickboldt] [~mmalina] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26161) Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26161?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26161: ------------------------------- Fix Version/s: 4.9.x > Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26161 > URL: https://issues.jboss.org/browse/JBIDE-26161 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.x > > > Take a look and update/repair Mac os machines used in our infra, especially zamek and check out the others: > * domek > * bigmek > * dev-platform-mac1 > * dev-platform-mac2 > cc: [~nickboldt] [~mmalina] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26157) Support for JEE8 projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26157?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26157: ------------------------------- Component/s: common server > Support for JEE8 projects > ------------------------- > > Key: JBIDE-26157 > URL: https://issues.jboss.org/browse/JBIDE-26157 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common, server > Reporter: Dawid Olejnik > Assignee: Jeff MAURY > Fix For: 4.9.x > > > Need support for EARs version 8 and WARs with servlets 4.0 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25276: ------------------------------- Sprint: devex #139 October 2017, devex #143 January 2018, devex #146 March 2018, devex #151 June 2018 (was: devex #139 October 2017, devex #143 January 2018, devex #146 March 2018) > intermittent test failures in webservices > ----------------------------------------- > > Key: JBIDE-25276 > URL: https://issues.jboss.org/browse/JBIDE-25276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.6.0.Final > > Attachments: ws-intermittent-apr10.png, ws-intermittent-test-failures.png, ws-intermittent-tests.png, ws-intermittent.png > > > Various tests are failing intermittently. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2 > Can these be fixed or if not, disabled, so that we can consistently get green builds? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 July 2018