December 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4209) Request for Administrator credentials should be shown once

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4209?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4209: -------------------------------- Fix Version/s: 11.2.0.AM2 (was: 11.x) > Request for Administrator credentials should be shown once > ---------------------------------------------------------- > > Key: JBDS-4209 > URL: https://issues.jboss.org/browse/JBDS-4209 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Environment: macOS > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.2.0.AM2 > > > Current implementation asks for administrator credentials for both vagrant and virtualbox installation. The request should be shown only once per installation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3962) Blog post about DevSuite installer on developers.redhat.com

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3962?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3962. ------------------------------- Resolution: Won't Fix > Blog post about DevSuite installer on developers.redhat.com > ----------------------------------------------------------- > > Key: JBDS-3962 > URL: https://issues.jboss.org/browse/JBDS-3962 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: marketing > Fix For: 11.x > > > We should draw more attention to DevSuite Installer and put more content about it on http://developers.redhat.com/blog/. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4341) Detect pending reboot and ask to reboot before continue with installation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4341?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4341. ------------------------------- Resolution: Migrated to another ITS https://github.com/redhat-developer-tooling/developer-platform-install/is... > Detect pending reboot and ask to reboot before continue with installation > ------------------------------------------------------------------------- > > Key: JBDS-4341 > URL: https://issues.jboss.org/browse/JBDS-4341 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.x > > > After something is installed it is possible to skip immediate reboot. This for example could be done for hyper-v install. If devsuite installer is running in this environment it detects hyper-v which is not available yet, because reboot was skipped. > DevSuite installer should detect pending reboots and request to reboot and restart installation. > Here is quite complex shell script that does this detection https://gallery.technet.microsoft.com/scriptcenter/Get-PendingReboot-Quer... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3732) Installer - A summary of what was installed should be displayed after a successful install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3732?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3732. ------------------------------- Resolution: Migrated to another ITS Migrated to https://github.com/redhat-developer-tooling/developer-platform-install/is.... > Installer - A summary of what was installed should be displayed after a successful install > ------------------------------------------------------------------------------------------ > > Key: JBDS-3732 > URL: https://issues.jboss.org/browse/JBDS-3732 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: New_and_noteworthy, ui > Fix For: 11.x > > Attachments: Add_an_inventory.png > > > See the attached screenshot - it would be helpful/informative to the user to see a summary/inventory of the components that were installed/updated successfully or failed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4556) Deselecting components will always deselect items they depend on

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4556?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4556. ------------------------------- Resolution: Migrated to another ITS MIgrated to https://github.com/redhat-developer-tooling/developer-platform-install/is.... > Deselecting components will always deselect items they depend on > ---------------------------------------------------------------- > > Key: JBDS-4556 > URL: https://issues.jboss.org/browse/JBDS-4556 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 11.x > > > To put this into some understandable language: > - say I select devstudio > - then I select fuse tools, which depends on devstudio > - then I deselect fuse tools and suddenly devstudio is deselected > This principle works nicely when you select & deselect items when the dependencies have not been selected beforehand. But it is a bit of pain when they have. > Is there a way to differentiate between the case when the user actively selects the dependency, and when it is selected automatically? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 closed JBDS-4307. ------------------------------- Resolution: Migrated to another ITS Moved to https://github.com/redhat-developer-tooling/developer-platform-install/is.... > 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.2.0.AM2 > > > 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.5.0#75005)

8 years, 3 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: -------------------------------- Fix Version/s: 11.2.0.AM2 (was: 11.x) > 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.2.0.AM2 > > > 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.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25403) Docker New and Noteworthy for 4.5.2.AM2

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25403?page=com.atlassian.jira.plugi... ] Jeff Johnston closed JBIDE-25403. --------------------------------- Resolution: Rejected > Docker New and Noteworthy for 4.5.2.AM2 > --------------------------------------------------- > > Key: JBIDE-25403 > URL: https://issues.jboss.org/browse/JBIDE-25403 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Labels: task > Fix For: 4.5.2.AM2 > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker 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 Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker 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-25400 #comment Create N&N for Docker 4.5.2.AM2 #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 Docker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25405) Forge New and Noteworthy for 4.5.2.AM2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25405?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-25405. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.5.2.AM2 > --------------------------------------------------- > > Key: JBIDE-25405 > URL: https://issues.jboss.org/browse/JBIDE-25405 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Labels: task > Fix For: 4.5.2.AM2 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge 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 Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge 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-25400 #comment Create N&N for Forge 4.5.2.AM2 #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 Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25301: ------------------------------- Fix Version/s: 4.5.2.AM3 (was: 4.5.2.AM2) > [release] externalize common properties to parameterize jobs > ------------------------------------------------------------ > > Key: JBIDE-25301 > URL: https://issues.jboss.org/browse/JBIDE-25301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized. > for example we could set these params in the jbosstools-jenkins.properties files: > {code}TARGET_PLATFORM_VERSION_MIN= > TARGET_PLATFORM_VERSION_MAX= > TARGET_PLATFORM_CENTRAL_MAX= > {code} > Or we could simply remove them and source them from the parent pom. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017