March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3632) Using a pre packaged version of Cygwin that doesn't require the installer to download packages

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3632?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3632: -------------------------------- Sprint: (was: devex #129 March 2017) > Using a pre packaged version of Cygwin that doesn't require the installer to download packages > ---------------------------------------------------------------------------------------------- > > Key: JBDS-3632 > URL: https://issues.jboss.org/browse/JBDS-3632 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.4.0.AM2 > > > It should be possible to install Cygwin, and then package that install in such a way that we can do a more silent install that doesn't require packages to be downloaded. > Some clues can be found here: https://cygwin.com/ml/cygwin/2010-03/msg00877.html > The fix should modify the bundle build to download packages into temp folder and then zip them. This zip then included into bundle installer. > {code}c:\DevelopmentSuite\cygwin\setup-x86_64.exe -D --no-admin --quiet-mode --only-site -l c:\DevelopmentSuite\cygwin\packages --site http://mirrors.xmission.com/cygwin --categories Base --packages openssh,rsync --root c:\DevelopmentSuite{code} > Another modification should be done to cygwin installer to check for included zip with packages, unpack it and do installation from local folder instead > {code}c:\DevelopmentSuite\cygwin\setup-x86_64.exe --no-admin --quiet-mode -L -l c:\DevelopmentSuite\cygwin\packages --categories Base --packages openssh,rsync --root c:\DevelopmentSuite\cygwin{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24153) Forge New and Noteworthy for 4.4.4.AM2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24153?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-24153. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.4.4.AM2 > --------------------------------------------------- > > Key: JBIDE-24153 > URL: https://issues.jboss.org/browse/JBIDE-24153 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Critical > > 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-24148 #comment Create N&N for Forge 4.4.4.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.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24148) Create New and Noteworthy for 4.4.4.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24148?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24148: ------------------------------------ Whoops, didn't see we already had N&N JIRAs created a couple weeks ago. > Create New and Noteworthy for 4.4.4.AM2 > --------------------------------------- > > Key: JBIDE-24148 > URL: https://issues.jboss.org/browse/JBIDE-24148 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.4.4.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24151) Docker New and Noteworthy for 4.4.4.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24151?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24151. ------------------------------ Fix Version/s: 4.4.4.AM2 Resolution: Duplicate Issue > Docker New and Noteworthy for 4.4.4.AM2 > --------------------------------------------------- > > Key: JBIDE-24151 > URL: https://issues.jboss.org/browse/JBIDE-24151 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Nick Boldt > Assignee: Jeff Johnston > Priority: Critical > Fix For: 4.4.4.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-24148 #comment Create N&N for Docker 4.4.4.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.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24151) Docker New and Noteworthy for 4.4.4.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24151?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24151: ------------------------------------ It is however a duplicate of JBIDE-24089... so yeah, I guess I can close this one. > Docker New and Noteworthy for 4.4.4.AM2 > --------------------------------------------------- > > Key: JBIDE-24151 > URL: https://issues.jboss.org/browse/JBIDE-24151 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Nick Boldt > Assignee: Jeff Johnston > Priority: Critical > Fix For: 4.4.4.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-24148 #comment Create N&N for Docker 4.4.4.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.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24173) rename docker tooling N&N files so they appear in JBoss Tools N&N pages

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24173: ---------------------------------- Summary: rename docker tooling N&N files so they appear in JBoss Tools N&N pages Key: JBIDE-24173 URL: https://issues.jboss.org/browse/JBIDE-24173 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker, website Affects Versions: 4.4.4.AM2 Reporter: Nick Boldt Noticed today thanks to [~jjohnstn] that there is no Docker Tooling N&N after JBoss Tools 4.3.1. I suspect this is due to the fact that the filenames are named thus: {code} docker-news-1.0.0.Mars0.adoc docker-news-1.1.0-jbt-4.3.0.Final.adoc docker-news-1.1.0.Mars1.adoc docker-news-1.2.0.Mars2.adoc docker-news-2.0.0.Neon0.adoc docker-news-2.0.0.NeonM7.adoc docker-news-2.1.0.Neon1.sprint118.adoc docker-news-2.1.0.Neon1.sprint119.adoc {code} And the latest N&N for Docker is this page: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html... Whereas for Forge, which DOES have N&N showing up, we see filenames like this: {code} forge-news-4.4.2.AM2.adoc forge-news-4.4.2.AM3.adoc forge-news-4.4.2.Final.adoc forge-news-4.4.3.Final.adoc forge-news-4.4.4.AM1.adoc {code} And therefore we see Forge N&N: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.AM1.html#f... http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.3.Final.html... http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.2.Final.html... [~xcoulon] Is this a correct interpretation? I can rename the files is so. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

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

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4341: ----------------------------------- Summary: 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 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.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24173) rename docker tooling N&N files so they appear in JBoss Tools N&N pages

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24173?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24173: ------------------------------- Fix Version/s: 4.4.4.AM2 > rename docker tooling N&N files so they appear in JBoss Tools N&N pages > ----------------------------------------------------------------------- > > Key: JBIDE-24173 > URL: https://issues.jboss.org/browse/JBIDE-24173 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, website > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > > Noticed today thanks to [~jjohnstn] that there is no Docker Tooling N&N after JBoss Tools 4.3.1. > I suspect this is due to the fact that the filenames are named thus: > {code} > docker-news-1.0.0.Mars0.adoc > docker-news-1.1.0-jbt-4.3.0.Final.adoc > docker-news-1.1.0.Mars1.adoc > docker-news-1.2.0.Mars2.adoc > docker-news-2.0.0.Neon0.adoc > docker-news-2.0.0.NeonM7.adoc > docker-news-2.1.0.Neon1.sprint118.adoc > docker-news-2.1.0.Neon1.sprint119.adoc > {code} > And the latest N&N for Docker is this page: > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html... > Whereas for Forge, which DOES have N&N showing up, we see filenames like this: > {code} > forge-news-4.4.2.AM2.adoc > forge-news-4.4.2.AM3.adoc > forge-news-4.4.2.Final.adoc > forge-news-4.4.3.Final.adoc > forge-news-4.4.4.AM1.adoc > {code} > And therefore we see Forge N&N: > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.AM1.html#f... > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.3.Final.html... > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.2.Final.html... > [~xcoulon] Is this a correct interpretation? I can rename the files is so. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24173) rename docker tooling N&N files so they appear in JBoss Tools N&N pages

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24173?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24173: ---------------------------------- Assignee: Nick Boldt > rename docker tooling N&N files so they appear in JBoss Tools N&N pages > ----------------------------------------------------------------------- > > Key: JBIDE-24173 > URL: https://issues.jboss.org/browse/JBIDE-24173 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, website > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > > Noticed today thanks to [~jjohnstn] that there is no Docker Tooling N&N after JBoss Tools 4.3.1. > I suspect this is due to the fact that the filenames are named thus: > {code} > docker-news-1.0.0.Mars0.adoc > docker-news-1.1.0-jbt-4.3.0.Final.adoc > docker-news-1.1.0.Mars1.adoc > docker-news-1.2.0.Mars2.adoc > docker-news-2.0.0.Neon0.adoc > docker-news-2.0.0.NeonM7.adoc > docker-news-2.1.0.Neon1.sprint118.adoc > docker-news-2.1.0.Neon1.sprint119.adoc > {code} > And the latest N&N for Docker is this page: > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html... > Whereas for Forge, which DOES have N&N showing up, we see filenames like this: > {code} > forge-news-4.4.2.AM2.adoc > forge-news-4.4.2.AM3.adoc > forge-news-4.4.2.Final.adoc > forge-news-4.4.3.Final.adoc > forge-news-4.4.4.AM1.adoc > {code} > And therefore we see Forge N&N: > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.AM1.html#f... > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.3.Final.html... > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.2.Final.html... > [~xcoulon] Is this a correct interpretation? I can rename the files is so. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4318) Detect Hyper-V version

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4318?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4318: ------------------------------------- If it is not installed then version should be marked as 'Unknown'. There is no Hyper-v for windows 10 home edition > Detect Hyper-V version > ---------------------- > > Key: JBDS-4318 > URL: https://issues.jboss.org/browse/JBDS-4318 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.3.0.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 10.4.0.AM2 > > > {code} > powershell -ExecutionPolicy ByPass -command "(get-item c:\\windows\\system32\\vmms.exe).VersionInfo.ProductVersion" > {code} > The output would be the version -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2017