October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15630) Have "Report Bug" dialog actually report bugs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15630?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15630: ---------------------------------------- This implementation shouldn't use Mylyn which is probably too complex. It could rely on Jira rest API or Jira Java Client for rest API. Bundle com.atlassian.jira_rest_client is already part of the target-platform. > Have "Report Bug" dialog actually report bugs > --------------------------------------------- > > Key: JBIDE-15630 > URL: https://issues.jboss.org/browse/JBIDE-15630 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Daniel Azarov > Fix For: 4.2.x > > > When Mylyn/Jira connector is installed, the "Report Error" dialog should provide the possiblity to directly push report as a Jira, just like Mylyn does for Eclipse. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-388) Update explicit 7.0 text references in docs to 7.1

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-388?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-388: ------------------------------------------ 7.0 screen caps to be updated via JBDS-2749. > Update explicit 7.0 text references in docs to 7.1 > -------------------------------------------------- > > Key: TOOLSDOC-388 > URL: https://issues.jboss.org/browse/TOOLSDOC-388 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > Original Estimate: 5 hours, 30 minutes > Time Spent: 1 hour, 55 minutes > Remaining Estimate: 0 minutes > > Section that need updating > *Installation Guide* > * 2.2. Supported Operating Systems and Architectures > * 2.3. Computer Memory > * 2.4. Compatible Java Developer Kits > * 3.2. Install JBoss Developer Studio > * 3.3. Install JBoss Developer Studio BYOE > * 5.2. Upgrade JBoss Developer Studio > * 5.3. Upgrade JBoss Developer Studio BYOE > * B.1. Build the Universal Installer from Source > *Migration Guide* (2.2 and 2.3 shared with Installation Guide) > * 2.2. Upgrade JBoss Developer Studio > * 2.3. Upgrade JBoss Developer Studio BYOE > * 3.1. Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *Getting Started Guide* (3.2 shared with Installation Guide) > * 2.1. About Getting Started > * 3.1. Installation Assumptions > * 3.2. Install JBoss Developer Studio > * 4.3. Tutorial Assumptions > *User Guide* > * None -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-388) Update explicit 7.0 text references in docs to 7.1

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-388?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-388: ------------------------------------------ [~nickboldt], thanks for the 7.x tip, have incorporated into section about update site. > Update explicit 7.0 text references in docs to 7.1 > -------------------------------------------------- > > Key: TOOLSDOC-388 > URL: https://issues.jboss.org/browse/TOOLSDOC-388 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > Original Estimate: 5 hours, 30 minutes > Time Spent: 1 hour, 55 minutes > Remaining Estimate: 0 minutes > > Section that need updating > *Installation Guide* > * 2.2. Supported Operating Systems and Architectures > * 2.3. Computer Memory > * 2.4. Compatible Java Developer Kits > * 3.2. Install JBoss Developer Studio > * 3.3. Install JBoss Developer Studio BYOE > * 5.2. Upgrade JBoss Developer Studio > * 5.3. Upgrade JBoss Developer Studio BYOE > * B.1. Build the Universal Installer from Source > *Migration Guide* (2.2 and 2.3 shared with Installation Guide) > * 2.2. Upgrade JBoss Developer Studio > * 2.3. Upgrade JBoss Developer Studio BYOE > * 3.1. Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *Getting Started Guide* (3.2 shared with Installation Guide) > * 2.1. About Getting Started > * 3.1. Installation Assumptions > * 3.2. Install JBoss Developer Studio > * 4.3. Tutorial Assumptions > *User Guide* > * None -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-388) Update explicit 7.0 text references in docs to 7.1

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-388?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-388. -------------------------------------- Resolution: Done Docs available on GitHub and internally here: http://documentation-devel.engineering.redhat.com/docs/en-US/index.html#R... > Update explicit 7.0 text references in docs to 7.1 > -------------------------------------------------- > > Key: TOOLSDOC-388 > URL: https://issues.jboss.org/browse/TOOLSDOC-388 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > Original Estimate: 5 hours, 30 minutes > Time Spent: 55 minutes > Remaining Estimate: 1 hour, 30 minutes > > Section that need updating > *Installation Guide* > * 2.2. Supported Operating Systems and Architectures > * 2.3. Computer Memory > * 2.4. Compatible Java Developer Kits > * 3.2. Install JBoss Developer Studio > * 3.3. Install JBoss Developer Studio BYOE > * 5.2. Upgrade JBoss Developer Studio > * 5.3. Upgrade JBoss Developer Studio BYOE > * B.1. Build the Universal Installer from Source > *Migration Guide* (2.2 and 2.3 shared with Installation Guide) > * 2.2. Upgrade JBoss Developer Studio > * 2.3. Upgrade JBoss Developer Studio BYOE > * 3.1. Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *Getting Started Guide* (3.2 shared with Installation Guide) > * 2.1. About Getting Started > * 3.1. Installation Assumptions > * 3.2. Install JBoss Developer Studio > * 4.3. Tutorial Assumptions > *User Guide* > * None -- 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, 6 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15622: --------------------------------------------- http://statistics.netbeans.org/exceptions/detail.do?id=67642 shows its done by having a front end to collect exceptions which then manually gets decided wether a bug report is worthy. > 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 > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2762) jbdevstudio links to nonexistant folder

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2762?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2762: -------------------------------- CDW devel_ack: + (was: ?) > jbdevstudio links to nonexistant folder > --------------------------------------- > > Key: JBDS-2762 > URL: https://issues.jboss.org/browse/JBDS-2762 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Environment: OSX > Reporter: Max Rydahl Andersen > Priority: Critical > > After install on OSX there is a symoblic link in the studio folder: > jbdevstudio@ -> jbdevstudio.app/Contents/MacOS/jbdevstudio > This shortcut is very useful when wanting to actually run eclipse/jbdevstudio with command line arguments, but the symbolic link is broken. > The actual path for the executable is: > ./JBoss Developer Studio.app/Contents/MacOS/jbdevstudio -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2762) jbdevstudio links to nonexistant folder

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2762?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2762: -------------------------------- Fix Version/s: 7.1.0.Beta1 > jbdevstudio links to nonexistant folder > --------------------------------------- > > Key: JBDS-2762 > URL: https://issues.jboss.org/browse/JBDS-2762 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Environment: OSX > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 7.1.0.Beta1 > > > After install on OSX there is a symoblic link in the studio folder: > jbdevstudio@ -> jbdevstudio.app/Contents/MacOS/jbdevstudio > This shortcut is very useful when wanting to actually run eclipse/jbdevstudio with command line arguments, but the symbolic link is broken. > The actual path for the executable is: > ./JBoss Developer Studio.app/Contents/MacOS/jbdevstudio -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2762) jbdevstudio links to nonexistant folder

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2762?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-2762: ----------------------------------- Assignee: Denis Golovin > jbdevstudio links to nonexistant folder > --------------------------------------- > > Key: JBDS-2762 > URL: https://issues.jboss.org/browse/JBDS-2762 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Environment: OSX > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 7.1.0.Beta1 > > > After install on OSX there is a symoblic link in the studio folder: > jbdevstudio@ -> jbdevstudio.app/Contents/MacOS/jbdevstudio > This shortcut is very useful when wanting to actually run eclipse/jbdevstudio with command line arguments, but the symbolic link is broken. > The actual path for the executable is: > ./JBoss Developer Studio.app/Contents/MacOS/jbdevstudio -- 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, 6 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15622: --------------------------------------------- Also http://wiki.netbeans.org/UseCases#Report_Exception_FAQs has interesting facts on how it is done. Not just done by reporting bugs directly into the issue tracker. > 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 > > 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, 6 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15622: --------------------------------------------- Reading http://wiki.netbeans.org/ReportExceptionProject i'm pretty sure they don't just looked for logged errors - that is also a very common occurrence that has no actual bug behind it but simply just info something went wrong. It should be listening to Exceptions being not-catched and then it could also provide a way to convert/select some error and report that. But showing report problem on every logged error would not be good I think. > 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 > > 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, 6 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 October 2013