[JBoss JIRA] (JBIDE-13674) provide a way for wizards on central to show up even if their plugin are not available
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13674?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-13674 at 5/4/13 4:36 AM:
-------------------------------------------------------------
Closing as dupe of JBIDE-13987
was (Author: fbricon):
Clsing as dupe of JBIDE-13987
> provide a way for wizards on central to show up even if their plugin are not available
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-13674
> URL: https://issues.jboss.org/browse/JBIDE-13674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
>
> Provide a mechanism in Central to declare a wizard with icon, description etc. that can show up even without the required plugin is available.
> If the plugin is available the wizard just start/works as expected.
> If the plugin is not available user should be explained what needs to be installed and ask if they want it. Then attempt to install via the provided IU's and/or central connector id, ask for restart and once restart is completed and central is started again and the plugin is available - open dialog saying "You started XYZ Wizard - it is now installed. Want to start it ?"
> If the plugin still is not available that is an error situation and should be told to the user.
--
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, 11 months
[JBoss JIRA] (JBIDE-13674) provide a way for wizards on central to show up even if their plugin are not available
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13674?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-13674.
---------------------------------
Fix Version/s: (was: 4.1.0.Beta1)
Resolution: Duplicate Issue
Clsing as dupe of JBIDE-13987
> provide a way for wizards on central to show up even if their plugin are not available
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-13674
> URL: https://issues.jboss.org/browse/JBIDE-13674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
>
> Provide a mechanism in Central to declare a wizard with icon, description etc. that can show up even without the required plugin is available.
> If the plugin is available the wizard just start/works as expected.
> If the plugin is not available user should be explained what needs to be installed and ask if they want it. Then attempt to install via the provided IU's and/or central connector id, ask for restart and once restart is completed and central is started again and the plugin is available - open dialog saying "You started XYZ Wizard - it is now installed. Want to start it ?"
> If the plugin still is not available that is an error situation and should be told to the user.
--
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, 11 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Denis Golovin commented on JBIDE-2720:
--------------------------------------
What Windows versions have you tested?
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Yahor Radtsevich
> Fix For: 4.0.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for windows 64 bit.
--
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, 11 months
[JBoss JIRA] (JBDS-1659) If set as default, java 1.5 is used even if 1.6 is chosen during installation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-1659?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-1659.
---------------------------------
Release Notes Docs Status: Not Required
Fix Version/s: 7.0.0.Beta1
(was: 7.0.x)
Resolution: Out of Date
> If set as default, java 1.5 is used even if 1.6 is chosen during installation
> -----------------------------------------------------------------------------
>
> Key: JBDS-1659
> URL: https://issues.jboss.org/browse/JBDS-1659
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 4.1.0.M1, 5.0.0.GA
> Environment: jbdevstudio-product-macosx-cocoa-x86_64-4.1.0.v201105091943R-H400-M1.jar
> Mac OS X 10.5 Leopard
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 7.0.0.Beta1
>
> Attachments: screenshot69.png, screenshot70.png
>
>
> If java 1.5 is set as default in the Java Preferences utility and you select java 1.6 during JBDS installation, it is still started with 1.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, 11 months
[JBoss JIRA] (JBDS-1659) If set as default, java 1.5 is used even if 1.6 is chosen during installation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-1659?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-1659.
-------------------------------
Closing
> If set as default, java 1.5 is used even if 1.6 is chosen during installation
> -----------------------------------------------------------------------------
>
> Key: JBDS-1659
> URL: https://issues.jboss.org/browse/JBDS-1659
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 4.1.0.M1, 5.0.0.GA
> Environment: jbdevstudio-product-macosx-cocoa-x86_64-4.1.0.v201105091943R-H400-M1.jar
> Mac OS X 10.5 Leopard
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 7.0.0.Beta1
>
> Attachments: screenshot69.png, screenshot70.png
>
>
> If java 1.5 is set as default in the Java Preferences utility and you select java 1.6 during JBDS installation, it is still started with 1.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, 11 months
[JBoss JIRA] (JBIDE-14379) Seam Web project datasource settings
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14379?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14379:
-----------------------------------
Fix Version/s: 4.1.0.Beta2
> Seam Web project datasource settings
> ------------------------------------
>
> Key: JBIDE-14379
> URL: https://issues.jboss.org/browse/JBIDE-14379
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Seam 2
> Environment: JBDS 7.0.0.Alpha2, Seam2.3
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Beta2
>
>
> I consider default Seam Project wizard and its default datasource settings (especially running on EAP 6) as confusing. I would suggest to have the H2 datasource (there is no hsqldb) as default option at last wizard's dialog. I understand that this is question about Seam and EAP versions. EAP 5 & Seam2.2 is ok with hsqldb, but this is not true when using Seam2.3 & EAP 6.
> Next thing is when I don't specify any other datasource settings, I'll get datasource containing exactly the name of the driver (e.g h2-1.3.168-redhat-1.jar), which is not deployable. Why the default h2 driver (included in standalone.xml config) is not use?
--
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, 11 months
[JBoss JIRA] (JBIDE-14325) Remove UI dependencies from o.j.t.common.core
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14325?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-14325:
-----------------------------------
Priority: Major (was: Critical)
> Remove UI dependencies from o.j.t.common.core
> ---------------------------------------------
>
> Key: JBIDE-14325
> URL: https://issues.jboss.org/browse/JBIDE-14325
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.1.0.Alpha2
> Reporter: Rob Stryker
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Beta1
>
>
> One class is polluting o.j.t.common.core with a guaranteed UI class reference. The class in question is org.jboss.tools.common.text.TextProposal. This class should not be in a core plugin at all.
> This class USED to live in org.jboss.tools.common, but was mistakenly moved to org.jboss.tools.common.core. The package name was NOT changed, so consumers of this class almost 100% did not change their dependencies or depend on teh new LOCATION at all.
> Moving this class *BACK* to where it was before, while technically an API change, is almost assuredly very very low risk. There is a danger that *NEW* consumers have appeared, and that risk should be considered, but not exaggerated.
> One other class depends on two jeetools packages which are very large and have a sprawling dependency list. I can not say with certainty whether any UI is pulled in via this reference, but, i feel it is safest to remove it if it can be done in a safe manner.
--
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, 11 months
[JBoss JIRA] (JBIDE-13890) OpenOn for <div data-role="page">: "Open With BrowserSim" and "Open With Browser"
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13890?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13890:
----------------------------------
Description:
This feature may be useful for multi-page documents.
1. Open any jQueryMobile html page with HTML Editor.
2. Ctrl+Click on <div data-role="page">
3. There should be "Open With BrowserSim" and "Open With Browser" options available which opens this page with BrowserSim and Default Browser.
http://www.screenr.com/B697
was:
This feature may be useful for multi-page documents.
1. Open any jQueryMobile html page with HTML Editor.
2. Ctrl+Click on <div data-role="page">
3. There should be "Open With BrowserSim" option available which opens this page with BrowserSim.
http://www.screenr.com/B697
> OpenOn for <div data-role="page">: "Open With BrowserSim" and "Open With Browser"
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-13890
> URL: https://issues.jboss.org/browse/JBIDE-13890
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim, jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
>
> This feature may be useful for multi-page documents.
> 1. Open any jQueryMobile html page with HTML Editor.
> 2. Ctrl+Click on <div data-role="page">
> 3. There should be "Open With BrowserSim" and "Open With Browser" options available which opens this page with BrowserSim and Default Browser.
> http://www.screenr.com/B697
--
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, 11 months