[JBoss JIRA] (JBIDE-10044) Improve way to remove one plugin from group of plugins
by Jaroslav Jankovič (Created) (JIRA)
Improve way to remove one plugin from group of plugins
-------------------------------------------------------
Key: JBIDE-10044
URL: https://issues.jboss.org/browse/JBIDE-10044
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M4
Reporter: Jaroslav Jankovič
Fix For: 3.3.0.M4
I don't like way how to remove only one plugin from all JBoss Tools. If I choose all JBoss Tools plugins and I want to remove only one plugin (in my case for example - JBoss GWT Integration), I have to expand all subfolders to find out which of them contains desired plugin. I could use Filter to find that plugin, but after I type GWT and unclick JBoss GWT Integration, not only these plugin was removed, but other plugins are removed as well. I think we should provide better way to remove only one plugin than expanding all subfolders.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] (JBDS-1918) Uninstaller shortcut launches JBDS instead of izpack uninstaller
by Nick Boldt (Created) (JIRA)
Uninstaller shortcut launches JBDS instead of izpack uninstaller
----------------------------------------------------------------
Key: JBDS-1918
URL: https://issues.jboss.org/browse/JBDS-1918
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 4.1.1.GA, 5.0.0.M4
Environment: Win7 64-bit w/ JDK 6u25 32-bit
Reporter: Nick Boldt
Priority: Critical
Fix For: 4.1.1.GA, 5.0.0.M4
Steps to repro:
1. Install JBDS 4.1.1.CR2 (GA) or JBDS 5.0.0.M4 from any of these:
{code}
jbdevstudio-product-win32-5.0.0.v201110271830R-H42-M4.jar
jbdevstudio-product-eap-win32-5.0.0.v201110271830R-H42-M4.jar
jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA.jar
jbdevstudio-product-eap-win32-4.1.1.v201110271900R-H748-GA.jar
{code}
2. Next, try to uninstall from the menu item, which tries to run this:
{code}
C:\Users\nboldt\jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA\studio\jbdevstudio.exe -Dizpack.mode=privileged -jar "C:\Users\nboldt\jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA/Uninstaller\uninstaller.jar"
{code}
3. The result is that JBDS is launched -- seems the flags are simply ignored.
4. Suggest that instead, we run "C:\Users\nboldt\jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA/Uninstaller\uninstaller.jar" directly, as double-clicking that file DOES launch the uninstaller.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9188) add system property to allow explicit disabling of the visual page in VPE
by Max Rydahl Andersen (JIRA)
add system property to allow explicit disabling of the visual page in VPE
-------------------------------------------------------------------------
Key: JBIDE-9188
URL: https://issues.jboss.org/browse/JBIDE-9188
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Reporter: Max Rydahl Andersen
Assignee: Yahor Radtsevich
Priority: Critical
Fix For: 3.3.0.M2
Since we keep having OS's where xulrunner is having problems we should inlcude a way to disable it loading even though we have xul binaries available for it.
I suggest we look for system property: org.jboss.tools.vpe.loadvisualeditor if it is true (default) then we attempt to load the VPE as usual, but if false then we skip that page just as if the binaries were not available.
that would allow you do to eclipse -Dorg.jboss.tools.vpe.loadvisualeditor=false
Things to consider: if this property is set I guess xulrunner initializer should also not do anything ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-9590) ConcurrentModificationException in KB PageContextFactory
by Alexey Kazakov (JIRA)
ConcurrentModificationException in KB PageContextFactory
--------------------------------------------------------
Key: JBIDE-9590
URL: https://issues.jboss.org/browse/JBIDE-9590
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JST
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Victor Rubezhny
Priority: Critical
Fix For: 3.3.0.M3
{code}
org.jboss.tools.common.validation.JBTValidationException
at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:99)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at org.jboss.tools.jst.web.kb.include.IncludeContextBuilder.getIncludeContextDefinition(IncludeContextBuilder.java:135)
at org.jboss.tools.jst.web.kb.include.IncludeContextBuilder.processIncludeContextElement(IncludeContextBuilder.java:117)
at org.jboss.tools.jst.web.kb.include.IncludeContextBuilder.readElement(IncludeContextBuilder.java:210)
at org.eclipse.ui.internal.registry.RegistryReader.readElements(RegistryReader.java:144)
at org.eclipse.ui.internal.registry.RegistryReader.readExtension(RegistryReader.java:155)
at org.eclipse.ui.internal.registry.RegistryReader.readRegistry(RegistryReader.java:176)
at org.jboss.tools.jst.web.kb.include.IncludeContextBuilder.readContributions(IncludeContextBuilder.java:265)
at org.jboss.tools.jst.web.kb.include.IncludeContextBuilder.initCache(IncludeContextBuilder.java:252)
at org.jboss.tools.jst.web.kb.include.IncludeContextBuilder.getIncludeContextDefinitions(IncludeContextBuilder.java:274)
at org.jboss.tools.jst.web.kb.include.IncludeContextBuilder.getContextType(IncludeContextBuilder.java:317)
at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContextInstance(PageContextFactory.java:457)
at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:421)
at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:190)
at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:179)
at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:245)
at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:230)
at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:131)
at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:83)
... 2 more
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] (JBIDE-10101) Support multiple namespaces in JSP fragments dropped from palette
by Maxim Shmidov (Created) (JIRA)
Support multiple namespaces in JSP fragments dropped from palette
-----------------------------------------------------------------
Key: JBIDE-10101
URL: https://issues.jboss.org/browse/JBIDE-10101
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M3
Reporter: Maxim Shmidov
Assignee: Alexey Kazakov
Insertion of jsp fragments from palette is managed by org.jboss.tools.jst.jsp.jspeditor.dnd.JSPPaletteInsertHelper class.
On insertion it defines a namespace for inserted tag in the root document element. Namespace and prefix are received from palette.
Sometimes it is required to define a several namespaces for one fragment from palette. For example, fragment is some jsp tag, containing a "<jsp:attribute>" child element, so "jsp" namespace should be defined in concert with those tag namespace.
Potentially i can implement this functionality myself and submit you a patch, but i'd prefer to do it in accordance with DND code owner's considerations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months