[JBoss JIRA] (JBDS-2877) Upgrade to use izpack 5
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2877?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2877:
--------------------------------------
Description:
Over the years we have done various hacks to izpack 3 and 4 panels to make it behave well/as we wanted.
izpack 5 is rumored to have many of these fixes properly integrated thus it make sense to try and investigate if we should upgrade to izpack 5.
> Upgrade to use izpack 5
> -----------------------
>
> Key: JBDS-2877
> URL: https://issues.jboss.org/browse/JBDS-2877
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Reporter: Max Rydahl Andersen
>
> Over the years we have done various hacks to izpack 3 and 4 panels to make it behave well/as we wanted.
> izpack 5 is rumored to have many of these fixes properly integrated thus it make sense to try and investigate if we should upgrade to izpack 5.
--
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, 5 months
[JBoss JIRA] (JBIDE-16387) jst.web.ui.test fails
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16387?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16387:
-----------------------------------
Fix Version/s: 4.2.0.Alpha2
> jst.web.ui.test fails
> ---------------------
>
> Key: JBIDE-16387
> URL: https://issues.jboss.org/browse/JBIDE-16387
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha2
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Alpha2
>
> Attachments: org.jboss.tools.jst.web.ui.test.JstWebUiAllTests.txt
>
>
> Tests in error:
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
--
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, 5 months
[JBoss JIRA] (JBIDE-16387) jst.web.ui.test fails
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16387?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-16387:
----------------------------------
Attachment: org.jboss.tools.jst.web.ui.test.JstWebUiAllTests.txt
> jst.web.ui.test fails
> ---------------------
>
> Key: JBIDE-16387
> URL: https://issues.jboss.org/browse/JBIDE-16387
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha2
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Attachments: org.jboss.tools.jst.web.ui.test.JstWebUiAllTests.txt
>
>
> Tests in error:
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
--
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, 5 months
[JBoss JIRA] (JBIDE-16387) jst.web.ui.test fails
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16387?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-16387:
----------------------------------
Issue Type: Bug (was: Feature Request)
> jst.web.ui.test fails
> ---------------------
>
> Key: JBIDE-16387
> URL: https://issues.jboss.org/browse/JBIDE-16387
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha2
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Attachments: org.jboss.tools.jst.web.ui.test.JstWebUiAllTests.txt
>
>
> Tests in error:
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
> org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
--
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, 5 months
[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 edited comment on JBIDE-16345 at 1/20/14 7:53 PM:
-----------------------------------------------------------------
[~dazarov] please fix the following issues:
1. We should allow to insert tags in any place within the text node (not just in the beginning and end of the node)
2. If tags inserted in the end or in the beginning of the line we should insert the tag in a new line
was (Author: akazakov):
1. We should allow to insert tags in any place within the text node (not just in the beginning and end of the node)
2. If tags inserted in the end or in the beginning of the line we should insert the tag in a new line
> 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, 5 months
[JBoss JIRA] (JBIDE-16387) jst.web.ui.test fails
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-16387:
-------------------------------------
Summary: jst.web.ui.test fails
Key: JBIDE-16387
URL: https://issues.jboss.org/browse/JBIDE-16387
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.2.0.Alpha2
Reporter: Daniel Azarov
Assignee: Daniel Azarov
Tests in error:
org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
org.jboss.tools.jst.web.ui.openon.test.TaglibOpenOnTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
org.jboss.tools.jst.web.ui.openon.test.CreateNewFileHyperlinkTest(org.jboss.tools.test.util.ProjectImportTestSetup): Failed to execute runnable (java.lang.NullPointerException)
--
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, 5 months
[JBoss JIRA] (JBIDE-16386) Quick fix which offers to disable Facelet HTML Validator
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16386?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16386:
-----------------------------------
Fix Version/s: 4.2.x
> Quick fix which offers to disable Facelet HTML Validator
> --------------------------------------------------------
>
> Key: JBIDE-16386
> URL: https://issues.jboss.org/browse/JBIDE-16386
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsf
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.2.x
>
>
> Facelet HTML Validator causes many false errors and we disabled it for projects with KB nature. Lets make a quick fix which offers to disable Facelet HTML Validator for any project.
> Actually we already have such a quick fix - DisableFaceletHTMLValidatorMarkerResolution
> we just need to make it visible for all kind of problems with validator_id - org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator
--
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, 5 months
[JBoss JIRA] (JBIDE-16386) Quick fix which offers to disable Facelet HTML Validator
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-16386:
-------------------------------------
Summary: Quick fix which offers to disable Facelet HTML Validator
Key: JBIDE-16386
URL: https://issues.jboss.org/browse/JBIDE-16386
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsf
Reporter: Daniel Azarov
Assignee: Daniel Azarov
Facelet HTML Validator causes many false errors and we disabled it for projects with KB nature. Lets make a quick fix which offers to disable Facelet HTML Validator for any project.
Actually we already have such a quick fix - DisableFaceletHTMLValidatorMarkerResolution
we just need to make it visible for all kind of problems with validator_id - org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator
--
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, 5 months
[JBoss JIRA] (JBIDE-16375) Allow to extend Central extensions catalog with "Beta" stuff
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16375?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16375:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> Allow to extend Central extensions catalog with "Beta" stuff
> ------------------------------------------------------------
>
> Key: JBIDE-16375
> URL: https://issues.jboss.org/browse/JBIDE-16375
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central, discovery
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
>
> In order to make it easier for people to consume some "Beta" extensions from JBT or JBDS release (such as installing a Beta of JBT-IS on top of a JBT release), it would make sense to have Central allow users to select some catalogs in a UI entry such as "Include Experimental stuff" to show additional catalog entries.
> Either this could be a single catalog with the experimental content being annotated, or it could be 2 (or more catalogs) which have different quality levels.
> The Central UI will need to give feedback on the quality level for a given entry ("supported" or "experimental" or ...).
--
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, 5 months