[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-15622:
----------------------------------
Description:
Step 1:
!ReportError1.png!
Step 2:
!ReportBugStep2.png!
Step 3:
!ReportBugStep3.png!
!ReportBugStep3SourceView.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
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.
was:
Step 1:
!ReportError1.png!
Step 2:
!ReportBugStep2.png!
Step 3:
!ReportBugStep3.png! !ReportBugStep3SourceView.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, by 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
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.
> 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/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep2.png!
> Step 3:
> !ReportBugStep3.png!
> !ReportBugStep3SourceView.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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16136) Reorganize jst.test plugins
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-16136:
--------------------------------------
Summary: Reorganize jst.test plugins
Key: JBIDE-16136
URL: https://issues.jboss.org/browse/JBIDE-16136
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common/jst/core
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.2.x
We should merge jst.text.ext.test, css.test, jst.jsp.test to web.ui.test plugin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16101) Broken layout of feature description with "Technology Preview" text on Fedora
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16101?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16101:
------------------------------------
Attachment: Central_techprev.png
> Broken layout of feature description with "Technology Preview" text on Fedora
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16101
> URL: https://issues.jboss.org/browse/JBIDE-16101
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.1.CR1
> Environment: Fedora 18 64bit KDE, JBDS7.1.0.CR1 CR1-v20131124-0717-B560
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/devstudio-directory.xml
> -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/
> Reporter: Vlado Pakan
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: Central_techprev.png, jbide16101-not-sure-if-better.png, technologypreview.png
>
>
> Instead of link with text "Technology Preview" only link with text "Technology" is displayed within Central as patr of JBoss Hybrid Mobile Mobile Tools + CordovaSim item in JBoss Central.
> !technologypreview.png!
> It's displayed correctly on OSX.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16101) Broken layout of feature description with "Technology Preview" text on Fedora
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16101?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-16101:
-----------------------------------------
IMHO I don't think 'Preview' is sufficient. It should have some form of both words.
FYI, displays fine on my Fedora19 Gnome. My JBoss Central tab was extra small but 'technology preview' was displayed in full while category name got cut.
!Central_techprev.png!
> Broken layout of feature description with "Technology Preview" text on Fedora
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16101
> URL: https://issues.jboss.org/browse/JBIDE-16101
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.1.CR1
> Environment: Fedora 18 64bit KDE, JBDS7.1.0.CR1 CR1-v20131124-0717-B560
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/devstudio-directory.xml
> -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/
> Reporter: Vlado Pakan
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: Central_techprev.png, jbide16101-not-sure-if-better.png, technologypreview.png
>
>
> Instead of link with text "Technology Preview" only link with text "Technology" is displayed within Central as patr of JBoss Hybrid Mobile Mobile Tools + CordovaSim item in JBoss Central.
> !technologypreview.png!
> It's displayed correctly on OSX.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16132) XCode library search path is not set properly
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16132?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-16132:
------------------------------------
Assignee: Gorkem Ercan
> XCode library search path is not set properly
> ---------------------------------------------
>
> Key: JBIDE-16132
> URL: https://issues.jboss.org/browse/JBIDE-16132
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.1.CR1
>
>
> If a Cordova plugin adds a custom framework as a dependency for iOS the project fails to run and the exported XCode project does not compile.
> This is because the iOS project generator does not set the library search paths properly for custom frameworks.
> Aerogear Push Plugin now uses such a framework.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16132) XCode library search path is not set properly
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16132?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-16132:
---------------------------------
Labels: respin-b (was: )
> XCode library search path is not set properly
> ---------------------------------------------
>
> Key: JBIDE-16132
> URL: https://issues.jboss.org/browse/JBIDE-16132
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.CR1
>
>
> If a Cordova plugin adds a custom framework as a dependency for iOS the project fails to run and the exported XCode project does not compile.
> This is because the iOS project generator does not set the library search paths properly for custom frameworks.
> Aerogear Push Plugin now uses such a framework.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16120) jsf.ui test failure
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16120?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-16120:
-----------------------------------------
Unit Test Case is fixed: org.jboss.tools.jsf.jsp.ca.test.CAJsfAddInfoInELMessagesTest.testCAJsfAddInfoInELMessages
JUnit Test org.jboss.tools.jsf.jsp.ca.test.CAForELJavaAndJSTCompareTest is temporary excluded from the Test Suite because of difference in CA of
Java Editor and XHTML Editor. Should be fixed and included back after JBIDE-16135 is fixed.
> jsf.ui test failure
> -------------------
>
> Key: JBIDE-16120
> URL: https://issues.jboss.org/browse/JBIDE-16120
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Alpha1
>
>
> {code}
> testCAForELJavaAndJSTCompare(org.jboss.tools.jsf.jsp.ca.test.CAForELJavaAndJSTCompareTest) Time elapsed: 3.391 sec <<< FAILURE!
> junit.framework.ComparisonFailure: Additional Info Strings must be equal expected:<<html><[head><style CHARSET="ISO-8859-1" TYPE="text/css">/* Font definitions */ html { font-family: 'Ubuntu',sans-serif; font-size: 11pt; font-style: normal; font-weight: normal; } body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt { font-size: 1em; } pre { font-family: monospace; } /* Margins */ body { overflow: auto; margin-top: 0px; margin-bottom: 0.5em; margin-left: 0.3em; margin-right: 0px; } h1 { margin-top: 0.3em; margin-bottom: 0.04em; } h2 { margin-top: 2em; margin-bottom: 0.25em; } h3 { margin-top: 1.7em; margin-bottom: 0.25em; } h4 { margin-top: 2em; margin-bottom: 0.3em; } h5 { margin-top: 0px; margin-bottom: 0px; } p { margin-top: 1em; margin-bottom: 1em; } pre { margin-left: 0.6em; } ul { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em;} li { margin-top: 0px; margin-bottom: 0px; } li p { margin-top: 0px; margin-bottom: 0px; } ol { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em; } dl { margin-top: 0px; margin-bottom: 1em; } dt { margin-top: 0px; margin-bottom: 0px; font-weight: bold; } dd { margin-top: 0px; margin-bottom: 0px; } /* Styles and colors */ a:link { color: #0000FF; } a:hover { color: #000080; } a:visited { text-decoration: underline; } a.header:link { text-decoration: none; color: #ffffff } a.header:visited { text-decoration: none; color: #ffffff } a.header:hover { text-decoration: underline; color: #000080; } h4 { font-style: italic; } strong { font-weight: bold; } em { font-style: italic; } var { font-style: italic; } th { font-weight: bold; } </style></head><body text="#ffffff" bgcolor="#000000"><h5><div style='word-wrap: break-word; position: relative; margin-left: 20px; padding-top: 2px; '><a href='eclipse-open:%E2%98%82=JSF2KickStartWithoutLibs/JavaSource%3Cdemo%7BUser.java%E2%98%83User'><!--[if lte IE 6]><![if gte IE 5.5]> <span alt='Open Declaration' style="border:none; position: absolute; width: 16px; height: 16px; left: -21px; filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='file:/home/igels/Projects/jbt-4.0/requests/jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.ui.test/target/work/data/.metadata/.plugins/org.eclipse.jdt.ui/jdt-images/1.png')"></span> <![endif]><![endif]--> <!--[if !IE]>--> <img alt='Open Declaration' style='border:none; position: absolute; width: 16px; height: 16px; left: -21px; ' src='file:/home/igels/Projects/jbt-4.0/requests/jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.ui.test/target/work/data/.metadata/.plugins/org.eclipse.jdt.ui/jdt-images/1.png'/> <!--<![endif]--> <!--[if gte IE 7]> <img alt='Open Declaration' style='border:none; position: absolute; width: 16px; height: 16px; left: -21px; ' src='file:/home/igels/Projects/jbt-4.0/requests/jbosstools-javaee/jsf/tests/org.jboss.tools.jsf.ui.test/target/work/data/.metadata/.plugins/org.eclipse.jdt.ui/jdt-images/1.png'/> <![endif]--> </a><a class='header' href='eclipse-javadoc:%E2%98%82=JSF2KickStartWithoutLibs/JavaSource%3Cdemo'>demo</a>.<a class='header' href='eclipse-javadoc:%E2%98%82=JSF2KickStartWithoutLibs/JavaSource%3Cdemo%7BUser.java%E2%98%83User'>User</a></div>]</h5><br/>Created by...> but was:<<html><[body text="#ffffff" bgcolor="#000000"><h5><a class='header' href='eclipse-javadoc:%E2%98%82=JSF2KickStartWithoutLibs/JavaSource%3Cdemo'>demo</a>.User]</h5><br/>Created by...>
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.TestCase.assertEquals(TestCase.java:261)
> at org.jboss.tools.jsf.jsp.ca.test.CAForELJavaAndJSTCompareTest.compareJavaAndJSTProposals(CAForELJavaAndJSTCompareTest.java:179)
> at org.jboss.tools.jsf.jsp.ca.test.CAForELJavaAndJSTCompareTest.testCAForELJavaAndJSTCompare(CAForELJavaAndJSTCompareTest.java:74)
> {code}
> {code}
> testELApplyMethodProposal(org.jboss.tools.jsf.jsp.ca.test.CAELApplyMethodProposalTest) Time elapsed: 3.772 sectestCAJsfAddInfoInELMessages(org.jboss.tools.jsf.jsp.ca.test.CAJsfAddInfoInELMessagesTest) Time elapsed: 1.989 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Additional Info exists but its value is not expected:
> Add. Info: [/* Font definitions */ html { font-family: 'Ubuntu',sans-serif; font-size: 11pt; font-style: normal; font-weight: normal; } body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt { font-size: 1em; } pre { font-family: monospace; } /* Margins */ body { overflow: auto; margin-top: 0px; margin-bottom: 0.5em; margin-left: 0.3em; margin-right: 0px; } h1 { margin-top: 0.3em; margin-bottom: 0.04em; } h2 { margin-top: 2em; margin-bottom: 0.25em; } h3 { margin-top: 1.7em; margin-bottom: 0.25em; } h4 { margin-top: 2em; margin-bottom: 0.3em; } h5 { margin-top: 0px; margin-bottom: 0px; } p { margin-top: 1em; margin-bottom: 1em; } pre { margin-left: 0.6em; } ul { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em;} li { margin-top: 0px; margin-bottom: 0px; } li p { margin-top: 0px; margin-bottom: 0px; } ol { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em; } dl { margin-top: 0px; margin-bottom: 1em; } dt { margin-top: 0px; margin-bottom: 0px; font-weight: bold; } dd { margin-top: 0px; margin-bottom: 0px; } /* Styles and colors */ a:link { color: #0000FF; } a:hover { color: #000080; } a:visited { text-decoration: underline; } a.header:link { text-decoration: none; color: #ffffff } a.header:visited { text-decoration: none; color: #ffffff } a.header:hover { text-decoration: underline; color: #000080; } h4 { font-style: italic; } strong { font-weight: bold; } em { font-style: italic; } var { font-style: italic; } th { font-weight: bold; } Base Name: resourcesResource Bundle: /JSF2KickStartWithoutLibs/JavaSource/resources.properties]
> Expected Value: [Base Name: resourcesResource Bundle: /JSF2KickStartWithoutLibs/JavaSource/resources.properties]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.jsf.jsp.ca.test.CAJsfAddInfoInELMessagesTest.testCAJsfAddInfoInELMessages(CAJsfAddInfoInELMessagesTest.java:62)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months