August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4516) Confirmation page scroll substantially move page elements to the left after page is opened

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4516?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4516: ----------------------------------- Assignee: Denis Golovin > Confirmation page scroll substantially move page elements to the left after page is opened > ------------------------------------------------------------------------------------------ > > Key: JBDS-4516 > URL: https://issues.jboss.org/browse/JBDS-4516 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > > when user moves between location and confirmation page all elements suddenly move left for 17px and then back when one leave the page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4334) Cygwin installer does not support installation to location with spaces in name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4334?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4334: -------------------------------- Sprint: (was: devex #136 August 2017) > Cygwin installer does not support installation to location with spaces in name > ------------------------------------------------------------------------------ > > Key: JBDS-4334 > URL: https://issues.jboss.org/browse/JBDS-4334 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.1.0.AM1 > > > cygwin installer does not let to continue installation if target folder location has spaces -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4493: -------------------------------- Story Points: 8 (was: 3) > Virtualization detection never terminates on powershell version <= 2 > --------------------------------------------------------------------- > > Key: JBDS-4493 > URL: https://issues.jboss.org/browse/JBDS-4493 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.1.0.AM1 > > > Follow up on the mail thread about detection not finishing on win 7. > Namely methods from the Platform class that call powershell commands: > - isVirtualizationEnabled > - getHypervisorVersion > - isHypervisorEnabled > For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4389) Installing DevSuite blocked by not signing CDK terms, no way to sign in installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4389?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4389: -------------------------------- Sprint: (was: devex #136 August 2017) > Installing DevSuite blocked by not signing CDK terms, no way to sign in installer > --------------------------------------------------------------------------------- > > Key: JBDS-4389 > URL: https://issues.jboss.org/browse/JBDS-4389 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.4.0.GA > Reporter: Harry Mower > Assignee: Denis Golovin > Fix For: 11.1.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.1.AM1) > Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > * https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install smoke tests for devstudio installer jar + all early access content in Central (and jbt/ds BYOE installs too)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22172. ------------------------------ Resolution: Done We do this on CI builds now, so no need to do it as a smoke test step during stage/release > create automated install smoke tests for devstudio installer jar + all early access content in Central (and jbt/ds BYOE installs too) > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22172 > URL: https://issues.jboss.org/browse/JBIDE-22172 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > To better automate staging & release, we need a way to run a smoke test of a given installer jar, then to install all the GA & EA content in Central. > Steps to script: > a. wget installer jar > b. headless install (via -console or install.xml script) > c. install grinder or p2director install all the things in Central. > Also need to smoke test the BYOE cases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3894) Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3894?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3894: ----------------------------- Sprint: devex #116 June 2016, devex #128 February 2017, devex #129 March 2017 (was: devex #116 June 2016, devex #128 February 2017, devex #129 March 2017, devex #136 August 2017) > Refactoring: discovery plugins/TPs from jbds/jbdevstudio to devstudio > --------------------------------------------------------------------- > > Key: JBDS-3894 > URL: https://issues.jboss.org/browse/JBDS-3894 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: central-update, target-platform, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM2 > > > In https://github.com/jbosstools/jbosstools-discovery/ we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio and jbds. > Affected: publishing/staging/release scripts, discovery sites, jenkins jobs, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24798) Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24798?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24798: ------------------------------- Sprint: (was: devex #136 August 2017) > Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata) > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24798 > URL: https://issues.jboss.org/browse/JBIDE-24798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, build, updatesite > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.1.AM2 > > > After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata). > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19715) Refactoring: get rid of "fullSite", stick with "repository"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19715: ------------------------------- Fix Version/s: 4.5.1.AM2 (was: 4.5.1.AM1) > Refactoring: get rid of "fullSite", stick with "repository" > ----------------------------------------------------------- > > Key: JBIDE-19715 > URL: https://issues.jboss.org/browse/JBIDE-19715 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.1.AM2 > > > Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) Refactoring: eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24772: ------------------------------- Sprint: (was: devex #136 August 2017) > Refactoring: eliminate devstudio target platform; reuse jbosstools target platform > ---------------------------------------------------------------------------------- > > Key: JBIDE-24772 > URL: https://issues.jboss.org/browse/JBIDE-24772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. > Changes: > * jbosstools-discovery repo - remove unneeded configuration / folders > * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that > * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts > * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one > * refactoring as per JBDS-3894 > * documentation as per JBIDE-23510 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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