January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-2669 at 1/29/14 8:37 PM: -------------------------------------------------------------- I verified on installer downloaded from hudson. See Steps to reproduce. was (Author: dgolovin): I verified on installed downloaded from hudson. See Steps to reproduce. > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: build1667.png, update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15622: ----------------------------------- Fix Version/s: 4.3.x > 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 > Fix For: 4.3.x > > 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 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-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16409: ----------------------------------- Priority: Blocker (was: Major) > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Priority: Blocker > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- 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-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16409: ----------------------------------- Fix Version/s: 4.1.2.CR1 > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > Fix For: 4.1.2.CR1 > > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- 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-16345) General Palette improvements

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16345?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16345: ----------------------------------- Description: Improve Palette in order not to allow insert elements from Palette to the wrong places. 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item ||Before Insertion||After Insertion|| |!PaletteBefore1.png!|!PaletteAfter1.png!| |!PaletteBefore2.png!|!PaletteAfter2.png!| |!PaletteBefore3.png!|!PaletteAfter3.png!| |!PaletteBefore4.png!|!PaletteAfter4.png!| |!PaletteBefore5.png!|!PaletteAfter5.png!| 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor !PaletteDragAndDrop1.png! !PaletteDragAndDrop2.png! A short video: http://www.screenr.com/207N was: Improve Palette in order not to allow insert elements from Palette to the wrong places. 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item ||Before Insertion||After Insertion|| |!PaletteBefore1.png!|!PaletteAfter1.png!| |!PaletteBefore2.png!|!PaletteAfter2.png!| |!PaletteBefore3.png!|!PaletteAfter3.png!| |!PaletteBefore4.png!|!PaletteAfter4.png!| |!PaletteBefore5.png!|!PaletteAfter5.png!| 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor !PaletteDragAndDrop1.png! !PaletteDragAndDrop2.png! A short video: > General Palette improvements > ---------------------------- > > Key: JBIDE-16345 > URL: https://issues.jboss.org/browse/JBIDE-16345 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > Attachments: PaletteAfter1.png, PaletteAfter2.png, PaletteAfter3.png, PaletteAfter4.png, PaletteAfter5.png, PaletteBefore1.png, PaletteBefore2.png, PaletteBefore3.png, PaletteBefore4.png, PaletteBefore5.png, PaletteDragAndDrop1.png, PaletteDragAndDrop2.png > > > Improve Palette in order not to allow insert elements from Palette to the wrong places. > 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item > ||Before Insertion||After Insertion|| > |!PaletteBefore1.png!|!PaletteAfter1.png!| > |!PaletteBefore2.png!|!PaletteAfter2.png!| > |!PaletteBefore3.png!|!PaletteAfter3.png!| > |!PaletteBefore4.png!|!PaletteAfter4.png!| > |!PaletteBefore5.png!|!PaletteAfter5.png!| > 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor > !PaletteDragAndDrop1.png! > !PaletteDragAndDrop2.png! > A short video: http://www.screenr.com/207N -- 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-16345) General Palette improvements

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16345?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16345: ---------------------------------------- [~maxandersen]: http://www.screenr.com/207N > General Palette improvements > ---------------------------- > > Key: JBIDE-16345 > URL: https://issues.jboss.org/browse/JBIDE-16345 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > Attachments: PaletteAfter1.png, PaletteAfter2.png, PaletteAfter3.png, PaletteAfter4.png, PaletteAfter5.png, PaletteBefore1.png, PaletteBefore2.png, PaletteBefore3.png, PaletteBefore4.png, PaletteBefore5.png, PaletteDragAndDrop1.png, PaletteDragAndDrop2.png > > > Improve Palette in order not to allow insert elements from Palette to the wrong places. > 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item > ||Before Insertion||After Insertion|| > |!PaletteBefore1.png!|!PaletteAfter1.png!| > |!PaletteBefore2.png!|!PaletteAfter2.png!| > |!PaletteBefore3.png!|!PaletteAfter3.png!| > |!PaletteBefore4.png!|!PaletteAfter4.png!| > |!PaletteBefore5.png!|!PaletteAfter5.png!| > 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor > !PaletteDragAndDrop1.png! > !PaletteDragAndDrop2.png! -- 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-16345) General Palette improvements

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16345?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16345: ----------------------------------- Description: Improve Palette in order not to allow insert elements from Palette to the wrong places. 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item ||Before Insertion||After Insertion|| |!PaletteBefore1.png!|!PaletteAfter1.png!| |!PaletteBefore2.png!|!PaletteAfter2.png!| |!PaletteBefore3.png!|!PaletteAfter3.png!| |!PaletteBefore4.png!|!PaletteAfter4.png!| |!PaletteBefore5.png!|!PaletteAfter5.png!| 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor !PaletteDragAndDrop1.png! !PaletteDragAndDrop2.png! A short video: was: Improve Palette in order not to allow insert elements from Palette to the wrong places. 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item ||Before Insertion||After Insertion|| |!PaletteBefore1.png!|!PaletteAfter1.png!| |!PaletteBefore2.png!|!PaletteAfter2.png!| |!PaletteBefore3.png!|!PaletteAfter3.png!| |!PaletteBefore4.png!|!PaletteAfter4.png!| |!PaletteBefore5.png!|!PaletteAfter5.png!| 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor !PaletteDragAndDrop1.png! !PaletteDragAndDrop2.png! > General Palette improvements > ---------------------------- > > Key: JBIDE-16345 > URL: https://issues.jboss.org/browse/JBIDE-16345 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha2 > > Attachments: PaletteAfter1.png, PaletteAfter2.png, PaletteAfter3.png, PaletteAfter4.png, PaletteAfter5.png, PaletteBefore1.png, PaletteBefore2.png, PaletteBefore3.png, PaletteBefore4.png, PaletteBefore5.png, PaletteDragAndDrop1.png, PaletteDragAndDrop2.png > > > Improve Palette in order not to allow insert elements from Palette to the wrong places. > 1. Insert elements from Palette to the Editor by setting text cursor or selecting text in the Editor then pressing on Palette Item > ||Before Insertion||After Insertion|| > |!PaletteBefore1.png!|!PaletteAfter1.png!| > |!PaletteBefore2.png!|!PaletteAfter2.png!| > |!PaletteBefore3.png!|!PaletteAfter3.png!| > |!PaletteBefore4.png!|!PaletteAfter4.png!| > |!PaletteBefore5.png!|!PaletteAfter5.png!| > 2. Insert elements from Palette to the Editor by dragging elements from Palette and dropping them to the Editor > !PaletteDragAndDrop1.png! > !PaletteDragAndDrop2.png! > A short video: -- 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-2884) Update major JBDS version on splash-screen form 7 to 8

by Denis Golovin (JIRA)

Denis Golovin created JBDS-2884: ----------------------------------- Summary: Update major JBDS version on splash-screen form 7 to 8 Key: JBDS-2884 URL: https://issues.jboss.org/browse/JBDS-2884 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Components: p2-product Affects Versions: 8.0.0.Alpha2 Reporter: Denis Golovin -- 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-2884) Update major JBDS version on splash-screen form 7 to 8

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2884?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2884: -------------------------------- Priority: Critical (was: Major) > Update major JBDS version on splash-screen form 7 to 8 > ------------------------------------------------------ > > Key: JBDS-2884 > URL: https://issues.jboss.org/browse/JBDS-2884 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: p2-product > Affects Versions: 8.0.0.Alpha2 > Reporter: Denis Golovin > Priority: Critical > -- 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-16409) Need to include the latest WTP 3.5.2RC2 into TP for Kepler

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16409?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-16409: ----------------------------------------- The including the next build of WTP3.5.2RC2 is required in order to fix JBIDE-14597 > Need to include the latest WTP 3.5.2RC2 into TP for Kepler > ---------------------------------------------------------- > > Key: JBIDE-16409 > URL: https://issues.jboss.org/browse/JBIDE-16409 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.1.2.CR1 > Reporter: Victor Rubezhny > > Today, 30 January, 2014 WTP 3.5.2 received an important fix that is required in order to fix JBIDE-14597. > Please make the next release of WTP 3.5.2RC1 available as a part of TP for Kepler. -- 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 January 2014