September 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4408) DevSuite 1.4 Installer document how to clean up after a failed install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4408?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4408: -------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > DevSuite 1.4 Installer document how to clean up after a failed install > ---------------------------------------------------------------------- > > Key: JBDS-4408 > URL: https://issues.jboss.org/browse/JBDS-4408 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: doc, ui > Fix For: 11.x > > > There should be a document/faq that indicates how to clean-up / recover after a failed install. > On Windows there is the Uninstalli Dev Studio menu entry. But that doesn't clean up everything. > It prompts to delete everything in the installation directory C:\DeveloperSuite but doesn't actually delete everything. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4307) Do installation logging per component to simplify debugging in case of error

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4307?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4307: -------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > Do installation logging per component to simplify debugging in case of error > ---------------------------------------------------------------------------- > > Key: JBDS-4307 > URL: https://issues.jboss.org/browse/JBDS-4307 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.x > > > Possible logging libraries to use: > https://www.npmjs.com/package/winston > https://www.npmjs.com/package/log4js -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4331) Support configuration and custom installers loading from remote location

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4331?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4331: -------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > Support configuration and custom installers loading from remote location > ------------------------------------------------------------------------ > > Key: JBDS-4331 > URL: https://issues.jboss.org/browse/JBDS-4331 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Environment: Windows, macOS > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy > Fix For: 11.x > > > With JBDS-4330 in place installer could implement loading custom installer from remote configuration and that would decouple Installer UI from specific installer and allow for downloading and loading remote configuration (or should we call it repository?) > See https://www.npmjs.com/package/require-from-string for details. > Even crazier support RPM repositories and non-linux RPM packages (see some infor here https://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/html/RPM...) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4407) DevSuite 1.4 Installer, No Help, About, Place to Report Bugs, etc.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4407?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4407: -------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > DevSuite 1.4 Installer, No Help, About, Place to Report Bugs, etc. > ------------------------------------------------------------------ > > Key: JBDS-4407 > URL: https://issues.jboss.org/browse/JBDS-4407 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 11.x > > > The DevSuite 1.4 installer has No Help or About links. There are absolutely no clues for the user where to go for help or how to resolve problems. > Note: A version number is shown but only on the first screen. It disappears after you login and is difficult to get back to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4553) Get ready for Java9

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4553?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4553: -------------------------------- Component/s: platform-installer > Get ready for Java9 > ------------------- > > Key: JBDS-4553 > URL: https://issues.jboss.org/browse/JBDS-4553 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer, platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Jeff MAURY > Labels: installer, java9 > Fix For: 11.1.0.GA > > > When 11.1 will be out, Java9 will also be out. The installer refuses to accept Java9 JVM when JBDS is installed. Shouldn't we accept them now ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25049) Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25049?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25049: -------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.x) > Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started) > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25049 > URL: https://issues.jboss.org/browse/JBIDE-25049 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.1.AM3 > > Attachments: screenshot-1.png > > > # ASSERT: make sure that you have a minishift that does *NOT* have a docker registry. > {code} > [adietish@localhost minishift]$ ./minishift openshift registry > No information found for 'service/docker-registry' > {code} > # ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse > # ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse > # EXEC/ASSERT: make sure that your CDK/minishift server adapter is started > # EXEC: edit the OpenShift connection > # ASSERT: connection wizard shows up > # EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up > # EXEC: hit "Discover" > Result > An error dialog shows up telling you no registry provider could be found > !screenshot-1.png! > > the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25046) Can't find CDK for registry discovery when 2 connections are defined for CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25046?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25046: -------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.x) > Can't find CDK for registry discovery when 2 connections are defined for CDK > ---------------------------------------------------------------------------- > > Key: JBIDE-25046 > URL: https://issues.jboss.org/browse/JBIDE-25046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, cdk_server_adapter_, explorer, openshift, openshift_v3 > Fix For: 4.5.1.AM3 > > > EXEC: define an Openshift connection for CDK/admin > EXEC: define an Openshift connection for CDK/developer > EXEC: define a CDK3 server > EXEC: start the CDK 3 server > ASSERT: the CDK/admin OS3 connection is updated (registry not empty) > ASSERT: the CDK/developer OS3 connection is not updated (registry empty) > EXEC: on the CDK/developer OS3 connection, click the DIscover buttoon > ASSERT: the registry URL is updated, not the error dialog is displayed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24773) Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24773?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24773: ------------------------------------ That's a cool idea. If you're OK having to install XText and releng.targetplatform every time you switch Eclipse versions, then this would allow you to regen a .tpd -> .target pretty easily *locally* and then choose to republish the .target file if you choose. I was suggesting a way to have the .target file be regenerated via jenkins process, so you wouldn't have to do anything manually -- just fetch the latest from Nexus or github and point Eclipse at that file. (If it was updated in the fusetools github repo, you'd really only have to refresh the directory within Eclipse to see the new file.) > Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24773 > URL: https://issues.jboss.org/browse/JBIDE-24773 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24773) Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24773?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24773: ----------------------------------------- I think that for each Milestone it is enough. We might also use this https://github.com/mbarbero/fr.obeo.releng.targetplatform to avoid to have a linked version > Provide a Target Platform which is not requiring to have all other JBoss Tools project active in workspace > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24773 > URL: https://issues.jboss.org/browse/JBIDE-24773 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24844) fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24844?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24844: ------------------------------- Sprint: devex #138 September 2017 > fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8) > --------------------------------------------------------------------------- > > Key: JBIDE-24844 > URL: https://issues.jboss.org/browse/JBIDE-24844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: red-weekly-smoke-tests.png, redballs-16.png > > > As noted in JBIDE-24835, the it.weekly jobs try to run on macos w/ openjdk 1.8, but no such JDK exists there. Therefore need a combinationFilter to let us build with openjdk on windows and linux, and oracle jdk on macos. > {code} > combinationFilter = (label_exp == "macosx").implies(jdk == "jdk1.8") && (label_exp != "macosx").implies(jdk == "openjdk-1.8") > {code} > TODO: verify all the jobs linked from here [1] are working for all OSes > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... > * hibernatetools-itests.download-devstudio - test failures on rhel7 (not a matrix job) > * livereload.it.weekly - failing for windows 8.1 & 10 due to unresolved parent pom > * browsersim.it.weekly - failing for windows 8.1 due to unresolved parent pom > * archives.it.weekly - failed to resolve tycho-plugins:repo-utils1.0.0 (bad Nexus settings?) on win81 > * vpe.it.weekly - test failures on win81 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017