April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-648) Improve the tracking of BPMN2 issues

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-648?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-648: ------------------------------------------- You cannot move the BPMN project to jboss tools - it is an eclipse.org project. We've done various approaches: a) have duplicate jira with link to the relevant bugzilla(s) b) grant QE access to triage bugs in bugzilla (see https://wiki.eclipse.org/Bug_Reporting_FAQ#Bug_Editing_and_Triage) c) latest we've created the ERT project that import eclipse issues with the rht keyword and allow us to triage on our side as well as have the bugzilla alive. Sounds to me that B would work for BPMN and that you should make sure your issues in bugzilla are cleared marked what version they are fixed in ? I personally avoid any use of red hat bugzilla since dealing with one jira and one bugzilla is enough :) > Improve the tracking of BPMN2 issues > ------------------------------------ > > Key: JBTIS-648 > URL: https://issues.jboss.org/browse/JBTIS-648 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2 > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Priority: Critical > > Currently, BPMN2 issues are reported at Eclipse Bugzilla or Red Hat Bugzilla. Our problem is that we are no able to directly query all resolved issues related a specific build (for this purpose we use https://www.eclipse.org/bpmn2-modeler/whatsnew/). > Unfortunately, in Eclipse bugzilla QE doesn't have permissions to change a status of issues which were not created by QE (it seems that only commiters have such permissions). This is very important in testing cycles. > In Red Hat bugzilla all BPMN2 issues are a part of the BxMS products. I'm not sure whether this is the right place for all BPMN2 issues (it would also mean to clone existing issues from Eclipse bugzilla). > Other solutions could be > * Jira will be our primary tracker for BPMN2 issues (and all issues be cloned from Eclipse BZ) > * or move the whole project to the Jira JBoss Tools > What do you think? Do you have any ideas how to improve the process? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3766: --------------------------------- Fix Version/s: 9.1.0.GA > Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log? > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3766 > URL: https://issues.jboss.org/browse/JBDS-3766 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: install.log, Is_Restart_Needed.png, vagrant.log, vbox.log > > > See attached log files. > After some install attempts, Vagrant fails to start. The vagrant install log reports the following: > {code} > MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully. > MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Installation success or error status: 0. > MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Type of System Restart: 2. Reason for Restart: 2. > MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time. > {code} > Is a system restart needed to ensure that the vagrant installation is successful on Windows? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3766: --------------------------------- Priority: Critical (was: Blocker) > Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log? > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3766 > URL: https://issues.jboss.org/browse/JBDS-3766 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: install.log, Is_Restart_Needed.png, vagrant.log, vbox.log > > > See attached log files. > After some install attempts, Vagrant fails to start. The vagrant install log reports the following: > {code} > MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully. > MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Installation success or error status: 0. > MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Type of System Restart: 2. Reason for Restart: 2. > MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time. > {code} > Is a system restart needed to ensure that the vagrant installation is successful on Windows? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3765) Installer - Component Detection - Fails to recognize VirtualBox 5.0.8

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3765?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3765: -------------------------------------- Not 100% reproducible. > Installer - Component Detection - Fails to recognize VirtualBox 5.0.8 > --------------------------------------------------------------------- > > Key: JBDS-3765 > URL: https://issues.jboss.org/browse/JBDS-3765 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Fix For: 9.1.0.GA > > > See attached screenshot. > Steps to recreate: > * Install VirtualBox 5.0.8, add c:\Hashicorp\Vagrant\bin to the PATH > * Attempt to install using installer Setup-bundled-0.0.2-20160401-33, select to not install a new VirtualBox -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3765) Installer - Component Detection - Fails to recognize VirtualBox 5.0.8

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3765?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3765: --------------------------------- Priority: Critical (was: Blocker) > Installer - Component Detection - Fails to recognize VirtualBox 5.0.8 > --------------------------------------------------------------------- > > Key: JBDS-3765 > URL: https://issues.jboss.org/browse/JBDS-3765 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.1.0.GA > > > See attached screenshot. > Steps to recreate: > * Install VirtualBox 5.0.8, add c:\Hashicorp\Vagrant\bin to the PATH > * Attempt to install using installer Setup-bundled-0.0.2-20160401-33, select to not install a new VirtualBox -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3765) Installer - Component Detection - Fails to recognize VirtualBox 5.0.8

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3765?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3765: --------------------------------- Fix Version/s: 9.1.0.GA > Installer - Component Detection - Fails to recognize VirtualBox 5.0.8 > --------------------------------------------------------------------- > > Key: JBDS-3765 > URL: https://issues.jboss.org/browse/JBDS-3765 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.1.0.GA > > > See attached screenshot. > Steps to recreate: > * Install VirtualBox 5.0.8, add c:\Hashicorp\Vagrant\bin to the PATH > * Attempt to install using installer Setup-bundled-0.0.2-20160401-33, select to not install a new VirtualBox -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3726) Installer - Installer fails to overwrite/move an existing JDK

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3726?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3726: -------------------------------- Labels: Havoc (was: ) > Installer - Installer fails to overwrite/move an existing JDK > ------------------------------------------------------------- > > Key: JBDS-3726 > URL: https://issues.jboss.org/browse/JBDS-3726 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Windows 10 > Build: 0.0.2-20160324-14 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Critical > Labels: Havoc > Fix For: 9.1.0.GA > > > Attempting to overwrite a JDK that was installed by a previous installer run fails with this (permissions) error: > Mon, 28 Mar 2016 18:39:41 GMT-INFO: jdk - Extract C:\Users\jbossqa\AppData\Local\Temp\7zS1C02.tmp\jdk.zip to c:\DeveloperPlatform SUCCESS > Mon, 28 Mar 2016 18:39:41 GMT-INFO: jdk - Rename c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64to c:\DeveloperPlatform\jdk8 > Mon, 28 Mar 2016 18:39:41 GMT-ERROR: jdk - Error: EPERM: operation not permitted, rename 'c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64' -> 'c:\DeveloperPlatform\jdk8' > Mon, 28 Mar 2016 18:39:41 GMT-ERROR: jdk failed to install: Error: EPERM: operation not permitted, rename 'c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64' -> 'c:\DeveloperPlatform\jdk8' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3726) Installer - Installer fails to overwrite/move an existing JDK

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3726?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3726: -------------------------------- Fix Version/s: 9.1.0.GA > Installer - Installer fails to overwrite/move an existing JDK > ------------------------------------------------------------- > > Key: JBDS-3726 > URL: https://issues.jboss.org/browse/JBDS-3726 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Windows 10 > Build: 0.0.2-20160324-14 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Critical > Labels: Havoc > Fix For: 9.1.0.GA > > > Attempting to overwrite a JDK that was installed by a previous installer run fails with this (permissions) error: > Mon, 28 Mar 2016 18:39:41 GMT-INFO: jdk - Extract C:\Users\jbossqa\AppData\Local\Temp\7zS1C02.tmp\jdk.zip to c:\DeveloperPlatform SUCCESS > Mon, 28 Mar 2016 18:39:41 GMT-INFO: jdk - Rename c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64to c:\DeveloperPlatform\jdk8 > Mon, 28 Mar 2016 18:39:41 GMT-ERROR: jdk - Error: EPERM: operation not permitted, rename 'c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64' -> 'c:\DeveloperPlatform\jdk8' > Mon, 28 Mar 2016 18:39:41 GMT-ERROR: jdk failed to install: Error: EPERM: operation not permitted, rename 'c:\DeveloperPlatform\zulu8.13.0.5-jdk8.0.72-win_x64' -> 'c:\DeveloperPlatform\jdk8' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3764) Installer - Component Detection - Fails to recognize JDK as previously installed by the same installer

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3764?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3764: ------------------------------- Labels: havoc (was: ) > Installer - Component Detection - Fails to recognize JDK as previously installed by the same installer > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3764 > URL: https://issues.jboss.org/browse/JBDS-3764 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: JDK_detection.png > > > See attached screenshot. > To recreate this issue: > * Install using installer: Setup-bundled-0.0.2-20160401-33, accept all defaults > * Attempt to install "over" the installation just completed by running the installer a 2nd time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3764) Installer - Component Detection - Fails to recognize JDK as previously installed by the same installer

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3764?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3764: ------------------------------- Fix Version/s: 9.1.0.GA > Installer - Component Detection - Fails to recognize JDK as previously installed by the same installer > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3764 > URL: https://issues.jboss.org/browse/JBDS-3764 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Installer: Setup-bundled-0.0.2-20160401-33 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Fix For: 9.1.0.GA > > Attachments: JDK_detection.png > > > See attached screenshot. > To recreate this issue: > * Install using installer: Setup-bundled-0.0.2-20160401-33, accept all defaults > * Attempt to install "over" the installation just completed by running the installer a 2nd time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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