[JBoss JIRA] (JBIDE-13541) Palette items and context menu of visual part of VPE are not in sync
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13541?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich edited comment on JBIDE-13541 at 6/7/13 3:04 PM:
------------------------------------------------------------------
What is the meaning of the Mobile item in the customize palette dialog if it does not affect the appearance of the Mobile elements?
!customize-palette.png|thumbnail!
If the Mobile item would not be selected, then everything would be fine.
Might we:
a) disable the Mobile item in JSF files by default?
b) show mobile elements even in JSF files if the Mobile item is selected?
was (Author: yradtsevich):
What is the meaning of the Mobile item in the customize palette dialog if it does not affect the appearance of the Mobile elements?
!customize-palette.png|thumbnail!
If the Mobile item would not be selected, then everything would be fine.
> Palette items and context menu of visual part of VPE are not in sync
> --------------------------------------------------------------------
>
> Key: JBIDE-13541
> URL: https://issues.jboss.org/browse/JBIDE-13541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, Visual Page Editor core
> Affects Versions: 4.1.0.Alpha1
> Environment: JBDS Version: 7.0.0.Alpha1 Build id: Alpha1-v20130211-0546-B6
> Reporter: Vlado Pakan
> Assignee: Viacheslav Kabanovich
> Priority: Optional
> Fix For: 4.1.0.Beta2
>
> Attachments: customize-palette.png
>
>
> 1. Create JSF 1.2 project
> 2. Open inputUserName.jsp
> 3. Context Menu of visual part of VPE contains submenu Insert Around > Mobile
> ERROR: Palette doesn't contain this item even this item is not hidden.
> 1. Create HTML5 project via central
> 2. Open index.html page
> ERROR: Palette contains only Mobile item but context menu of visual part of VPE Insert Around contains submenus JBoss, JSF and Mobile
> Palette content and context menu of visual part of VPE should offer the same tags to insert.
--
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, 10 months
[JBoss JIRA] (JBIDE-13541) Palette items and context menu of visual part of VPE are not in sync
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13541?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich commented on JBIDE-13541:
------------------------------------------
An implementation note: [InsertContributionItem.java:130|https://github.com/jbosstools/jbosstools-...] is the point where the {{hidden}} property is tested.
> Palette items and context menu of visual part of VPE are not in sync
> --------------------------------------------------------------------
>
> Key: JBIDE-13541
> URL: https://issues.jboss.org/browse/JBIDE-13541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, Visual Page Editor core
> Affects Versions: 4.1.0.Alpha1
> Environment: JBDS Version: 7.0.0.Alpha1 Build id: Alpha1-v20130211-0546-B6
> Reporter: Vlado Pakan
> Assignee: Viacheslav Kabanovich
> Priority: Optional
> Fix For: 4.1.0.Beta2
>
> Attachments: customize-palette.png
>
>
> 1. Create JSF 1.2 project
> 2. Open inputUserName.jsp
> 3. Context Menu of visual part of VPE contains submenu Insert Around > Mobile
> ERROR: Palette doesn't contain this item even this item is not hidden.
> 1. Create HTML5 project via central
> 2. Open index.html page
> ERROR: Palette contains only Mobile item but context menu of visual part of VPE Insert Around contains submenus JBoss, JSF and Mobile
> Palette content and context menu of visual part of VPE should offer the same tags to insert.
--
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, 10 months
[JBoss JIRA] (JBIDE-13541) Palette items and context menu of visual part of VPE are not in sync
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13541?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich updated JBIDE-13541:
-------------------------------------
Attachment: customize-palette.png
What is the meaning of the Mobile item in the customize palette dialog if it does not affect the appearance of the Mobile elements?
!customize-palette.png|thumbnail!
If the Mobile item would not be selected, then everything would be fine.
> Palette items and context menu of visual part of VPE are not in sync
> --------------------------------------------------------------------
>
> Key: JBIDE-13541
> URL: https://issues.jboss.org/browse/JBIDE-13541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, Visual Page Editor core
> Affects Versions: 4.1.0.Alpha1
> Environment: JBDS Version: 7.0.0.Alpha1 Build id: Alpha1-v20130211-0546-B6
> Reporter: Vlado Pakan
> Assignee: Viacheslav Kabanovich
> Priority: Optional
> Fix For: 4.1.0.Beta2
>
> Attachments: customize-palette.png
>
>
> 1. Create JSF 1.2 project
> 2. Open inputUserName.jsp
> 3. Context Menu of visual part of VPE contains submenu Insert Around > Mobile
> ERROR: Palette doesn't contain this item even this item is not hidden.
> 1. Create HTML5 project via central
> 2. Open index.html page
> ERROR: Palette contains only Mobile item but context menu of visual part of VPE Insert Around contains submenus JBoss, JSF and Mobile
> Palette content and context menu of visual part of VPE should offer the same tags to insert.
--
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, 10 months
[JBoss JIRA] (JBIDE-14073) add remote deployment feature as EAP6 CLI does to JBDS.
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14073?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-14073:
-------------------------------------
Use case scenarios:
1- deploy a binary .war, .ear or any other deployable artifact - if you have the rights to deploy on the remote server - not limited by type of artifact
2- undeploy a binary artifact (e.g. war, ear, -ds.xml, etc) - if you have the rights to undeploy on the remote server - not limited to artifacts this user previously deployed
3- start the remote server
4- stop the remote server
5- restart the remote server (restart in debug)
6- attach to the remote server via debugger (not specific to the management API but a test case)
7- view logs - the entire log from the remote server? Or the last N lines? what about clearing the logs?
Questions:
a. Support for both Domain & Standalone
b. Logs: the entire log from the remote server? Or the last N lines? what about clearing the logs?
> add remote deployment feature as EAP6 CLI does to JBDS.
> -------------------------------------------------------
>
> Key: JBIDE-14073
> URL: https://issues.jboss.org/browse/JBIDE-14073
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Reporter: Gary Hu
> Assignee: Rob Stryker
>
> EAP6 CLI provides feature to do remote deployment:
> bin/jboss-cli.sh --connect --controller="127.0.0.1:9999" --command="deploy ../tmp/sample.war" --user="User"
> Is it possible to have such feature available in JBDS?
--
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, 10 months
[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2389:
-----------------------------
Release Notes Text:
1. If you uninstall the JBDS Product Feature, and perform a warm restart when prompted, you will see the 'Application "" could not be found in the registry.'.
On subsequent cold restarts, you will be able to start Eclipse, but Help > About and Help > Welcome will be corrupt.
2. If Eclipse is still unusable after as noted above, simply copy eclipse.ini_BEFORE_JBDS to eclipse.ini and restart Eclipse.
was:
1. If you uninstall the JBDS Product Feature, and restart when prompted, you will see the 'Application "" could not be found in the registry.'. On subsequent restarts, you will be able to start Eclipse, but Help > About and Help > Welcome will be corrupt.
2. If Eclipse is unusable after uninstall, simply copy eclipse.ini_BEFORE_JBDS to eclipse.ini and restart Eclipse.
> cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2389
> URL: https://issues.jboss.org/browse/JBDS-2389
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 6.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta2
>
>
> Steps to repro:
> Unpack bare Juno JEE.
> Install JBDS BYOE feature ("Core Features"). Restart
> Install JBDS Branded Product Feature. Restart.
> Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken:
> {code}
> java.lang.RuntimeException: Application "" could not be found in the registry.
> {code}
> Addtional info:
> {quote}
> Bare Juno JEE eclipse.ini:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> org.eclipse.epp.package.jee.product
> --launcher.defaultAction
> openFile
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Dhelp.lucene.tokenizer=standard
> -XX:MaxPermSize=256m
> -Xms40m
> -Xmx512m
> {code}
> or, for Eclipse Platform Binary:
> {code}
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms40m
> -Xmx384m
> {code}
> After installing JBDS BYOE:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms512m
> -Xmx1024m
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> {code}
> After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini:
> {code}
> $➔ cat eclipse/jbdevstudio.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> -Dosgi.instance.area.default=(a)user.home/workspace
> {code}
> After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> {code}
> {quote}
> So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines
> {code}
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> {code}
> and replace them with the following when JBDS is uninstalled:
> {code}
> -application
> org.eclipse.ui.ide.workbench
> -showsplash
> org.eclipse.platform
> {code}
> Also need to know what happens if there are two -product directives... can we just
> add (and later remove, when uninstalling) our product to the list, or must we replace
> any existing -product entries with ours?
--
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, 10 months
[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-2389.
------------------------------
Release Notes Docs Status: Not Yet Documented
Release Notes Text:
1. If you uninstall the JBDS Product Feature, and restart when prompted, you will see the 'Application "" could not be found in the registry.'. On subsequent restarts, you will be able to start Eclipse, but Help > About and Help > Welcome will be corrupt.
2. If Eclipse is unusable after uninstall, simply copy eclipse.ini_BEFORE_JBDS to eclipse.ini and restart Eclipse.
Resolution: Done
Closing for Beta2. Not entirely happy with this, but it's better than before.
Upstream issue / request reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=410231
> cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2389
> URL: https://issues.jboss.org/browse/JBDS-2389
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 6.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta2
>
>
> Steps to repro:
> Unpack bare Juno JEE.
> Install JBDS BYOE feature ("Core Features"). Restart
> Install JBDS Branded Product Feature. Restart.
> Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken:
> {code}
> java.lang.RuntimeException: Application "" could not be found in the registry.
> {code}
> Addtional info:
> {quote}
> Bare Juno JEE eclipse.ini:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> org.eclipse.epp.package.jee.product
> --launcher.defaultAction
> openFile
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Dhelp.lucene.tokenizer=standard
> -XX:MaxPermSize=256m
> -Xms40m
> -Xmx512m
> {code}
> or, for Eclipse Platform Binary:
> {code}
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms40m
> -Xmx384m
> {code}
> After installing JBDS BYOE:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms512m
> -Xmx1024m
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> {code}
> After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini:
> {code}
> $➔ cat eclipse/jbdevstudio.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> -Dosgi.instance.area.default=(a)user.home/workspace
> {code}
> After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> {code}
> {quote}
> So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines
> {code}
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> {code}
> and replace them with the following when JBDS is uninstalled:
> {code}
> -application
> org.eclipse.ui.ide.workbench
> -showsplash
> org.eclipse.platform
> {code}
> Also need to know what happens if there are two -product directives... can we just
> add (and later remove, when uninstalling) our product to the list, or must we replace
> any existing -product entries with ours?
--
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, 10 months
[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2389:
----------------------------------
Best I can do so far is in https://github.com/jbdevstudio/jbdevstudio-product/pull/3, which I've applied in master:
a) make Eclipse startable by removing -product com.jboss.jbds.product.product, and inserting -application org.eclipse.ui.ide.workbench. *See caveat below.*
b) before installation of the JBDS Product Feature, copy the eclipse.ini file to eclipse.ini_BEFORE_JBDS so users can revert by hand. *See instructions below.*
---
So, for the release notes:
1. If you uninstall the JBDS Product Feature, and restart when prompted, you will see the 'Application "" could not be found in the registry.'. On subsequent restarts, you will be able to start Eclipse, but Help > About and Help > Welcome will be corrupt.
2. If Eclipse is unusable after uninstall, simply copy eclipse.ini_BEFORE_JBDS to eclipse.ini and restart Eclipse.
> cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2389
> URL: https://issues.jboss.org/browse/JBDS-2389
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 6.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta2
>
>
> Steps to repro:
> Unpack bare Juno JEE.
> Install JBDS BYOE feature ("Core Features"). Restart
> Install JBDS Branded Product Feature. Restart.
> Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken:
> {code}
> java.lang.RuntimeException: Application "" could not be found in the registry.
> {code}
> Addtional info:
> {quote}
> Bare Juno JEE eclipse.ini:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> org.eclipse.epp.package.jee.product
> --launcher.defaultAction
> openFile
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Dhelp.lucene.tokenizer=standard
> -XX:MaxPermSize=256m
> -Xms40m
> -Xmx512m
> {code}
> or, for Eclipse Platform Binary:
> {code}
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms40m
> -Xmx384m
> {code}
> After installing JBDS BYOE:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms512m
> -Xmx1024m
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> {code}
> After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini:
> {code}
> $➔ cat eclipse/jbdevstudio.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> -Dosgi.instance.area.default=(a)user.home/workspace
> {code}
> After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> {code}
> {quote}
> So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines
> {code}
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> {code}
> and replace them with the following when JBDS is uninstalled:
> {code}
> -application
> org.eclipse.ui.ide.workbench
> -showsplash
> org.eclipse.platform
> {code}
> Also need to know what happens if there are two -product directives... can we just
> add (and later remove, when uninstalling) our product to the list, or must we replace
> any existing -product entries with ours?
--
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, 10 months
[JBoss JIRA] (JBIDE-13541) Palette items and context menu of visual part of VPE are not in sync
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13541?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13541:
-----------------------------------
Priority: Optional (was: Major)
> Palette items and context menu of visual part of VPE are not in sync
> --------------------------------------------------------------------
>
> Key: JBIDE-13541
> URL: https://issues.jboss.org/browse/JBIDE-13541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, Visual Page Editor core
> Affects Versions: 4.1.0.Alpha1
> Environment: JBDS Version: 7.0.0.Alpha1 Build id: Alpha1-v20130211-0546-B6
> Reporter: Vlado Pakan
> Assignee: Viacheslav Kabanovich
> Priority: Optional
> Fix For: 4.1.0.Beta2
>
>
> 1. Create JSF 1.2 project
> 2. Open inputUserName.jsp
> 3. Context Menu of visual part of VPE contains submenu Insert Around > Mobile
> ERROR: Palette doesn't contain this item even this item is not hidden.
> 1. Create HTML5 project via central
> 2. Open index.html page
> ERROR: Palette contains only Mobile item but context menu of visual part of VPE Insert Around contains submenus JBoss, JSF and Mobile
> Palette content and context menu of visual part of VPE should offer the same tags to insert.
--
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, 10 months
[JBoss JIRA] (JBIDE-13541) Palette items and context menu of visual part of VPE are not in sync
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13541?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-13541:
--------------------------------------
Assignee: Viacheslav Kabanovich (was: Alexey Kazakov)
Let's hide Mobile items in the context menu of the visual part. So JSF items will be always available in the context menu. Mobile items will be always hidden. It's not ideal but the visual part is useless for mobile development anyway.
> Palette items and context menu of visual part of VPE are not in sync
> --------------------------------------------------------------------
>
> Key: JBIDE-13541
> URL: https://issues.jboss.org/browse/JBIDE-13541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, Visual Page Editor core
> Affects Versions: 4.1.0.Alpha1
> Environment: JBDS Version: 7.0.0.Alpha1 Build id: Alpha1-v20130211-0546-B6
> Reporter: Vlado Pakan
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.0.Beta2
>
>
> 1. Create JSF 1.2 project
> 2. Open inputUserName.jsp
> 3. Context Menu of visual part of VPE contains submenu Insert Around > Mobile
> ERROR: Palette doesn't contain this item even this item is not hidden.
> 1. Create HTML5 project via central
> 2. Open index.html page
> ERROR: Palette contains only Mobile item but context menu of visual part of VPE Insert Around contains submenus JBoss, JSF and Mobile
> Palette content and context menu of visual part of VPE should offer the same tags to insert.
--
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, 10 months