March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3669: ------------------------------------- It's possible to read _version_ from application's _package.json_ at run time, it contains all the necessary information. > Inject version, timestamp and Jenkins build number into installer to show in installer window > --------------------------------------------------------------------------------------------- > > Key: JBDS-3669 > URL: https://issues.jboss.org/browse/JBDS-3669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3668) Add version, timestamp and build number to PDK installer exe file name

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3668?page=com.atlassian.jira.plugin.... ] Pavol Pitonak resolved JBDS-3668. --------------------------------- Resolution: Done > Add version, timestamp and build number to PDK installer exe file name > ---------------------------------------------------------------------- > > Key: JBDS-3668 > URL: https://issues.jboss.org/browse/JBDS-3668 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: havoc > Fix For: 9.1.0.CR1 > > > Insatller file name should contain: > * version > * timestamp > * build number > To let report issues with reference to specific version/build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21744) cdk-created docker connection can have wrong name if you have multiple cdk server adapters

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21744?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21744: --------------------------------------- Yesterday in chat I had another idea how to make this better: {quote} [07.03.16 19:09:29] Martin Malina: another option would be to rename the connection after server start [07.03.16 19:09:45] Martin Malina: when cdk is started, you check if the connection is there and create it if not [07.03.16 19:10:08] Martin Malina: so you could add one more thing - check if the name is the same as server adapter and if not, change it [07.03.16 19:10:39] Martin Malina: maybe it's currently not possible to change a docker connection's name. but that could be fixed [07.03.16 19:11:13] Martin Malina: or do you think that could be confusing as well? we can open a BZ for that and mark the jira for later in the meantime {quote} > cdk-created docker connection can have wrong name if you have multiple cdk server adapters > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21744 > URL: https://issues.jboss.org/browse/JBIDE-21744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > I noticed that if I have two cdk server adapters, start the first one, stop it, start the second, then docker explorer will only show a connection of the first server name, not the second. > This is probably because the connection will stay there after the first server start and on second server start, the tooling only checks if the docker host url matches. If it does, it will just reuse it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3615) virtual box cannot be installed reliably on windows

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3615?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3615: ----------------------------------- In fact the difference is they use the /qn switch instead of /qb, we use /norestart as well. Apparently what /qn does is, it completely hides the UI (great!) and it looks like the install gets through every time (awesome!). The only catch is it has to be run with elevated privileges to even start. So if we could make node ask for elevated privileges it should work. > virtual box cannot be installed reliably on windows > --------------------------------------------------- > > Key: JBDS-3615 > URL: https://issues.jboss.org/browse/JBDS-3615 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > > look at docker-toolbox what they do that is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3664) Do we still need/want custom build of vagrant ?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3664?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3664: ------------------------------------- It is all depends on legal department approval, is't it? The only problem I am aware of is original installer requests reboot, but we can suppres it with /norestart parameter and see if vagrant still works fine without installation. > Do we still need/want custom build of vagrant ? > ----------------------------------------------- > > Key: JBDS-3664 > URL: https://issues.jboss.org/browse/JBDS-3664 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > we seem to install use our custom vagrant build. > Is that still relevant ? > With that we need to test much more since our build could be different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3670) Build self executable bundled installer on Jenkins

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3670?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3670: -------------------------------- Labels: havoc (was: ) > Build self executable bundled installer on Jenkins > -------------------------------------------------- > > Key: JBDS-3670 > URL: https://issues.jboss.org/browse/JBDS-3670 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > Latest version of electron-packager-squirrel-windows cannot handle big installer with size more than 600Mb approximately. This forces us to use alternative approach for bundled installer that includes: > * CDK; > * SSH/rsync > * openjdk8 > * JBDS > To create bundled installer, build should download all required binaries and put them along with installer exe file with with the same name that installer uses in online version. For example CDK binaries would go to cdk.zip, JBDS installer to jbds.jar and so on. Names are configured in browser/model/*.js files for every downloaded binary. > Then 7zip extra package should be downloaded and used t produce self extracting archive from generated electron installer (gulp generate) and downloaded binaries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3669: -------------------------------- Labels: havoc (was: ) > Inject version, timestamp and Jenkins build number into installer to show in installer window > --------------------------------------------------------------------------------------------- > > Key: JBDS-3669 > URL: https://issues.jboss.org/browse/JBDS-3669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3668) Add version, timestamp and build number to PDK installer exe file name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3668?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3668: ------------------------------------- Just date should be enough, because we also have build number. Together date and build number gives us unique id for the build. > Add version, timestamp and build number to PDK installer exe file name > ---------------------------------------------------------------------- > > Key: JBDS-3668 > URL: https://issues.jboss.org/browse/JBDS-3668 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: havoc > Fix For: 9.1.0.CR1 > > > Insatller file name should contain: > * version > * timestamp > * build number > To let report issues with reference to specific version/build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3668) Add version, timestamp and build number to PDK installer exe file name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3668?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3668: -------------------------------- Labels: havoc (was: ) > Add version, timestamp and build number to PDK installer exe file name > ---------------------------------------------------------------------- > > Key: JBDS-3668 > URL: https://issues.jboss.org/browse/JBDS-3668 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: havoc > Fix For: 9.1.0.CR1 > > > Insatller file name should contain: > * version > * timestamp > * build number > To let report issues with reference to specific version/build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3660) Unable to download ssh-rsync from the provided URL

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3660?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3660: ----------------------------- > Unable to download ssh-rsync from the provided URL > -------------------------------------------------- > > Key: JBDS-3660 > URL: https://issues.jboss.org/browse/JBDS-3660 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > The URL ssh-rsync should be downloaded from points to google drive, which won't let anyone download it without about two more confirmations. The installer just cant cope with this. > As a result of the installs now being chained, it now blocks vagrant and cdk installs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016