November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25111) Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25111?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25111: ---------------------------------------- Assignee: Andre Dietisheim > Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?) > -------------------------------------------------------------------------------- > > Key: JBIDE-25111 > URL: https://issues.jboss.org/browse/JBIDE-25111 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.2.AM2 > > > OpenShift only allows you only 1 project. Thus the usual approach to create a project per application and kill the project to remove all resources cannot be used in OpenShift online. We thus need a way to delete all resources that are related to an application. Ex. with a mor powerful delete action that pops up a window with a filter-/query-parameter that would filter the list of available resources and then allow to delete all the visible (or selected ones) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25111) Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25111?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25111: ------------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.x) > Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?) > -------------------------------------------------------------------------------- > > Key: JBIDE-25111 > URL: https://issues.jboss.org/browse/JBIDE-25111 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.2.AM2 > > > OpenShift only allows you only 1 project. Thus the usual approach to create a project per application and kill the project to remove all resources cannot be used in OpenShift online. We thus need a way to delete all resources that are related to an application. Ex. with a mor powerful delete action that pops up a window with a filter-/query-parameter that would filter the list of available resources and then allow to delete all the visible (or selected ones) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25109: ------------------------------------- Sprint: devex #141 December 2017 > Server adapter editor: provide ability to only change debug port (and not the debug port key) > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25109 > URL: https://issues.jboss.org/browse/JBIDE-25109 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor > Fix For: 4.5.2.AM2 > > > Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4588) update installer to be able to use JDK 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4588?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4588: ----------------------------- Sprint: devex #139 October 2017, devex #141 December 2017 (was: devex #139 October 2017) > update installer to be able to use JDK 9 > ---------------------------------------- > > Key: JBDS-4588 > URL: https://issues.jboss.org/browse/JBDS-4588 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.1.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.2.0.AM2 > > Attachments: jdk9-ea.png, jdk9.0.1.png > > > Investigate what's needed to support running the installer w/ JDK 9. > May also need to add this to the devstudio.ini, after *-vmargs*: > {code}-Dosgi.requiredJavaVersion=1.8 > --add-modules=ALL-SYSTEM{code} -- https://wiki.eclipse.org/Configure_Eclipse_for_Java_9#Configure_Eclipse_f... > cc: [~mmalina] [~jeffmaury] [~dgolovin] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25228: ------------------------------- Fix Version/s: (was: 4.5.2.AM2) > target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25228 > URL: https://issues.jboss.org/browse/JBIDE-25228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.5.x > > > With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. > We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. > Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? > Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. > [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... > [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... > [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25228: ------------------------------- Sprint: devex #139 October 2017 (was: devex #139 October 2017, devex #141 December 2017) > target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25228 > URL: https://issues.jboss.org/browse/JBIDE-25228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.5.x > > > With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. > We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. > Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? > Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. > [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... > [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... > [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4597) Work to remove all upstream 3rd party deps in the devstudio rpm

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4597?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4597: ----------------------------- Fix Version/s: 11.x (was: 11.2.0.AM2) > Work to remove all upstream 3rd party deps in the devstudio rpm > --------------------------------------------------------------- > > Key: JBDS-4597 > URL: https://issues.jboss.org/browse/JBDS-4597 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: 3rd-party-dependencies, rpm, target-platform, upstream > Affects Versions: 11.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.x > > > This is a wrapper issue for a number of subtasks and linked issues related to eliminating the 3rd party plugins in the devstudio copr rpm, so that it can ultimately be built w/ brew. > Tasks include: > * create new rpms in Fedora/Koji (buildship, sapphire, tern.java), then DevTools/Brew -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25303: ------------------------------------- Sprint: devex #141 December 2017 (was: devex #140 November 2017) > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM2 > > Attachments: spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25303: ------------------------------------- Story Points: 24 (was: 20) > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM2 > > Attachments: spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25387) Missing coretests bundles on stable update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25387?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-25387. -------------------------------- Resolution: Done This worked (after a couple tweaks) for publishing the dev milestone 4.5.2.AM1, so resolving. Adding of tests and checks will be done in JBIDE-18743 > Missing coretests bundles on stable update site > ----------------------------------------------- > > Key: JBIDE-25387 > URL: https://issues.jboss.org/browse/JBIDE-25387 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.5.1.Final > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.5.2.AM1 > > Attachments: coretests.png > > > The following update site > http://download.jboss.org/jbosstools/oxygen/stable/updates/coretests/ > is missing all coretests bundles. Note that the composite files define folder '4.5.1.Final' but no such folder exists. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017