December 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4213) <Reading schema error:Getting database metadata>

by kokila vishwa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4213?page=com.atlassian.jira.plugin.... ] kokila vishwa updated JBDS-4213: -------------------------------- Attachment: Screenshot > <Reading schema error:Getting database metadata> > ------------------------------------------------ > > Key: JBDS-4213 > URL: https://issues.jboss.org/browse/JBDS-4213 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Environment: <Reading schema error:Getting database metadata> > Reporter: kokila vishwa > Attachments: Screenshot > > > <Reading schema error:Getting database metadata> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4208) Detection for installed components always counts cygwin as detected on macOS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4208?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4208: -------------------------------- Story Points: 1 > Detection for installed components always counts cygwin as detected on macOS > ---------------------------------------------------------------------------- > > Key: JBDS-4208 > URL: https://issues.jboss.org/browse/JBDS-4208 > 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: 10.3.0.AM1 > > > It means confirmation page message about detected components always increase number of detected components by one. If only Java is detected it would say "We found 2 installed components" one is Java and another one is Cygwin which is not visible under macOS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4170) Remove windows uninstaller from mac distribution

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4170?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4170: -------------------------------- Story Points: 5 > Remove windows uninstaller from mac distribution > ------------------------------------------------ > > Key: JBDS-4170 > URL: https://issues.jboss.org/browse/JBDS-4170 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Environment: mac osx > Reporter: Jan Richter > Assignee: Sudhir Verma > Fix For: 10.3.0.AM1 > > > The uninstaller/uninstall.ps1 is getting generated by the mac installer. Remove it or replace with something that runs on mac (like a shell script). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov closed JBIDE-15622. ------------------------------------ Resolution: Done Closing this JIRA, because an old report system was replaced with AERI. For more info see JBIDE-22994 > Automatically open/send report when log has error > ------------------------------------------------- > > Key: JBIDE-15622 > URL: https://issues.jboss.org/browse/JBIDE-15622 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Dmitrii Bocharov > Labels: f2f2014 > Fix For: 4.5.0.AM1 > > Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.bmml, ReportError1.png, ResultPage.bmml, ResultPage.png > > > Step 1: > !ReportError1.png! > Step 2: > !ReportBugStep3.png! > !ReportBugStep3SourceView.png! > Step 3: > !ReportBugStep2.png! > Result Page: > !ResultPage.png! > *Where to:* > 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug > 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace > 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions > 1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report? > 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)? > *Feature list:* > 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously) > 2. Check Exception Stack-trace for duplicate > 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc) > 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator > 5. User should be able to see all the data he is going to send (see tab "Source View") > 6. Show communication errors > 7. Return link to created JIRA > 8. Inform user about the general/common process of bug reporting (see Work-flow) > 9. Option to attach log file > 10. Option to attach screen-shot > *Preconditions:* > 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user. > 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project. > *Work-flow:* > 1. User decides/agrees to report the problem (see list Where to) > 2. Report Problem dialog appears, user fills up the form > 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary. > 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions) > 4. User gets link to created issue and short description of what will happen next. (features 7. 8.) > 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools). > *Primary Description:* > JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error. > As it's probably not possible to send the error report without asking users, it should show the "Report problem" page. > NetBeans does that and has reported an actual quality benefit. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17209) only product for mylyn integration is JBossAS Server

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17209?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov closed JBIDE-17209. ------------------------------------ Resolution: Out of Date Closing this JIRA, because an old report system was replaced with AERI. For more info see JBIDE-22994 > only product for mylyn integration is JBossAS Server > ---------------------------------------------------- > > Key: JBIDE-17209 > URL: https://issues.jboss.org/browse/JBIDE-17209 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common > Reporter: Max Rydahl Andersen > Assignee: Dmitrii Bocharov > Priority: Minor > Fix For: 4.5.0.AM1 > > > Using "report bug or enhancement" JBoss Tools shows up but then after that a list of "products" is shown and it just list JBossAS Server. > I would have expected Developer Studio too at least, and a few more key components. > Note: this might not be something base should add, but put it into central or jbds product makes sense I think. > -- Configuration Details -- > Product: Eclipse 4.4.0.20140301-1817 (org.eclipse.epp.package.jee.product) > Installed Features: > org.jboss.ide.eclipse.as.feature 3.0.0.Beta2-v20140421-1626-B483 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install test for JBDS installer jar + all early access content in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22172: ------------------------------- Sprint: devex #124 December 2017 > create automated install test for JBDS installer jar + all early access content in Central > ------------------------------------------------------------------------------------------ > > 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 > Fix For: 4.4.3.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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install test for JBDS installer jar + all early access content in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22172: ---------------------------------- Assignee: Nick Boldt > create automated install test for JBDS installer jar + all early access content in Central > ------------------------------------------------------------------------------------------ > > 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.4.3.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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install test for JBDS installer jar + all early access content in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22172: ------------------------------- Parent: (was: JBIDE-20904) Issue Type: Feature Request (was: Sub-task) > create automated install test for JBDS installer jar + all early access content in Central > ------------------------------------------------------------------------------------------ > > 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 > Fix For: 4.4.3.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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install test for JBDS installer jar + all early access content in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22172: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > create automated install test for JBDS installer jar + all early access content in Central > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22172 > URL: https://issues.jboss.org/browse/JBIDE-22172 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Fix For: 4.4.3.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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23021: ------------------------------- Sprint: devex #119 August 2016, devex #123 November 2016, devex #124 December 2017 (was: devex #119 August 2016, devex #123 November 2016) > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 2016