[JBoss JIRA] (JBIDE-14849) Exceptions when working with font-family in CSS Dialog
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14849?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-14849:
---------------------------------------
Upstream issue is fixed in webtools source editing master branch.
> Exceptions when working with font-family in CSS Dialog
> ------------------------------------------------------
>
> Key: JBIDE-14849
> URL: https://issues.jboss.org/browse/JBIDE-14849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.1.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Fix For: 4.1.x
>
>
> I have a copy of jquery.mobile-1.3.0.css in one of my projects.
> I opened it with the default editor and then opened CSS Dialog.
> The I got the following exceptions it the log:
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.NullPointerException
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocumentRegion.getText(BasicStructuredDocumentRegion.java:304)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.getText(CSSDeclarationItemParser.java:1073)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.createPrimitiveValue(CSSDeclarationItemParser.java:364)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:1014)
> at org.eclipse.wst.css.core.internal.document.CSSDeclarationItemParser.setupValues(CSSDeclarationItemParser.java:964)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueTextCore(CSSStyleDeclItemImpl.java:260)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueText(CSSStyleDeclItemImpl.java:234)
> at org.eclipse.wst.css.core.internal.document.CSSStyleDeclarationImpl.setProperty(CSSStyleDeclarationImpl.java:267)
> at org.jboss.tools.jst.css.dialog.common.CSSModel.updateCSSStyle(CSSModel.java:297)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.handleSelectorSwitched(CSSClassDialog.java:250)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog$1.modifyText(CSSClassDialog.java:152)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Combo.select(Combo.java:1726)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.updateControlPane(CSSClassDialog.java:377)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.createContents(CSSClassDialog.java:99)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.jst.css.dialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:70)
> at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> ... 37 more
> {code}
> Dialog is not opened.
> If you try to open it again you will get an empty error message in the log:
> {code}
> !ENTRY org.jboss.tools.jst.css 4 0 2013-06-12 14:27:10.147
> !MESSAGE
> {code}
> The dialog is opened.
> Click on OK and get another exception:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.jst.css.dialog.common.CSSModel.save(CSSModel.java:260)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.save(CSSClassDialog.java:295)
> at org.jboss.tools.jst.css.dialog.CSSClassDialog.close(CSSClassDialog.java:315)
> at org.eclipse.jface.dialogs.Dialog.okPressed(Dialog.java:955)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.jboss.tools.jst.css.dialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:70)
> at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> The dialog is not closed.
> Didn't try another CSS file.
--
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, 8 months
[JBoss JIRA] (JBIDE-13242) Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13242?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-13242:
----------------------------------------
Yes, that's correct.
> Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13242
> URL: https://issues.jboss.org/browse/JBIDE-13242
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2, upstream
> Affects Versions: 4.0.0.Beta2
> Environment: Seam.2.3.0, JBDS 5.0.1.GA or JBDS 6.0.0.Beta2a
> Reporter: Marek Novotny
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Beta1
>
>
> After importing and building a Seam 2.3 seam-gen generated project in JBDS, it reports missing files referenced from view-id in pages.xml and in somEntity.page.xml files.
> This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS.
> How reproducible:
> Import a seam-gen generated EAR project, check pages.xml.
> Steps to Reproduce:
> 1. Create a seam-gen EAR project.
> 2. Import into JBDS.
> 3. Open pages.xml, make a change (to trigger build).
>
> Actual results:
> On lines referencing a view-id, like
> <redirect view-id="/home.xhtml"/>
> JBDS shows an error saying:
> Cannot find target resource: "/home.xhtml"
--
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, 8 months
[JBoss JIRA] (JBIDE-15311) Error in validation of jboss-deployment-structure.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15311?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-15311.
------------------------------------
Assignee: Alexey Kazakov
Fix Version/s: 4.2.0.Alpha1
Resolution: Duplicate Issue
Duplicates JBIDE-14629
> Error in validation of jboss-deployment-structure.xml
> -----------------------------------------------------
>
> Key: JBIDE-15311
> URL: https://issues.jboss.org/browse/JBIDE-15311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Environment: Version: 7.0.0.GA
> Build id: GA-v20130720-0044-B364
> Build date: 20130720-0044
> WFK 2.3.0.GA, Seam 2.3.1.Final-redhat-2
> Reporter: Marek Novotny
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha1
>
>
> Wrong validation error on jboss-deployment-structure.xml file:
> {code:XML}
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
> <deployment>
> <dependencies>
> <module name="org.hibernate" export="true"/>
> <module name="javax.faces.api" export="true" />
> <module name="com.sun.jsf-impl" export="true"/>
> <module name="org.dom4j" export="true"/>
> <module name="org.hibernate.validator" export="true"/>
> </dependencies>
> </deployment>
> </jboss-deployment-structure>
> {code}
> Validation error:
> {noformat}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml
> {noformat}
> The error says exactly what is in jboss-deployment-structure.xml - we have there deployment, so this is valid and not invalid content.
--
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, 8 months
[JBoss JIRA] (JBIDE-15311) Error in validation of jboss-deployment-structure.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15311?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15311:
-----------------------------------
Component/s: upstream
> Error in validation of jboss-deployment-structure.xml
> -----------------------------------------------------
>
> Key: JBIDE-15311
> URL: https://issues.jboss.org/browse/JBIDE-15311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Environment: Version: 7.0.0.GA
> Build id: GA-v20130720-0044-B364
> Build date: 20130720-0044
> WFK 2.3.0.GA, Seam 2.3.1.Final-redhat-2
> Reporter: Marek Novotny
>
> Wrong validation error on jboss-deployment-structure.xml file:
> {code:XML}
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
> <deployment>
> <dependencies>
> <module name="org.hibernate" export="true"/>
> <module name="javax.faces.api" export="true" />
> <module name="com.sun.jsf-impl" export="true"/>
> <module name="org.dom4j" export="true"/>
> <module name="org.hibernate.validator" export="true"/>
> </dependencies>
> </deployment>
> </jboss-deployment-structure>
> {code}
> Validation error:
> {noformat}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml
> {noformat}
> The error says exactly what is in jboss-deployment-structure.xml - we have there deployment, so this is valid and not invalid content.
--
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, 8 months
[JBoss JIRA] (JBIDE-15291) xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15291?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov edited comment on JBIDE-15291 at 7/31/13 12:00 PM:
--------------------------------------------------------------------------
[~bookwood], after two days of fighting I've install gentoo to virtualbox(I use [this|http://mirrors.us.kernel.org/gentoo//releases/amd64/20121221/] liveDVD), install IcedTea JDK 7.2.3.3 and try to reproduce your steps. I am able to visit marketplace.
!gentoo.png!
was (Author: kmarmaliykov):
[~bookwood], after two days of fighting I've install gentoo to virtualbox, install IcedTea JDK 7.2.3.3 and try to reproduce your steps. I am able to visit marketplace.
!gentoo.png!
> xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15291
> URL: https://issues.jboss.org/browse/JBIDE-15291
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core, XULRunner
> Affects Versions: 4.1.0.Final
> Environment: Linux 3.8.13-gentoo #1 SMP Sun Jun 23 23:34:36 CEST 2013 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux
> IcedTea JDK 7.2.4.1
> eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz
> Reporter: Jochen Buchholz
> Assignee: Yahor Radtsevich
> Priority: Critical
> Fix For: 4.1.x
>
> Attachments: .log, click-on-jbosscentral-button.png, frozen-marketplace.png, gentoo.png, m2e-connectors.png
>
>
> I installed the eclipse standard kepler and go to market place. I choose JBoss developer studio 7.0.0 GA and install it via marketplace. After the restart I choose File->Import->Maven->"checkout Maven Projects from SCM" and click on the "Find out more SCM connectors in the m2e Marketplace. I got the error: "Failed to discover all connectors."
> I cant Use the Marketplace anymore, because he is frozen while load the content.
> In the error log I found this line:
> Caused by: java.io.IOException: /mnt/usb/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so)
> like in the old issue JBIDE-10628 reported also by me
> Developer Studio is unusable under 64bit Linux.
--
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, 8 months
[JBoss JIRA] (JBIDE-15291) xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15291?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov edited comment on JBIDE-15291 at 7/31/13 11:58 AM:
--------------------------------------------------------------------------
Jochen, as you can see from screenshot I was doing everything from empty workspace. Do I need some projects there?
UPD: Visual Page Editor works for me.
was (Author: kmarmaliykov):
Jochen, as you can see from screenshot I was doing everything from empty workspace. Do I need some projects there?
> xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15291
> URL: https://issues.jboss.org/browse/JBIDE-15291
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core, XULRunner
> Affects Versions: 4.1.0.Final
> Environment: Linux 3.8.13-gentoo #1 SMP Sun Jun 23 23:34:36 CEST 2013 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux
> IcedTea JDK 7.2.4.1
> eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz
> Reporter: Jochen Buchholz
> Assignee: Yahor Radtsevich
> Priority: Critical
> Fix For: 4.1.x
>
> Attachments: .log, click-on-jbosscentral-button.png, frozen-marketplace.png, gentoo.png, m2e-connectors.png
>
>
> I installed the eclipse standard kepler and go to market place. I choose JBoss developer studio 7.0.0 GA and install it via marketplace. After the restart I choose File->Import->Maven->"checkout Maven Projects from SCM" and click on the "Find out more SCM connectors in the m2e Marketplace. I got the error: "Failed to discover all connectors."
> I cant Use the Marketplace anymore, because he is frozen while load the content.
> In the error log I found this line:
> Caused by: java.io.IOException: /mnt/usb/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so)
> like in the old issue JBIDE-10628 reported also by me
> Developer Studio is unusable under 64bit Linux.
--
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, 8 months
[JBoss JIRA] (JBIDE-15205) OpenShift menu contribution issue
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15205:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have a clean workspace (eventually remove and recreate it)
# ASSERT: make sure that you dont have OpenShift Explorer opened, dont have any OpenShift server adapter
# EXEC: restart Eclipse
# ASSERT: verify in the OSGI console that the OpenShift UI plugin is *NOT ACTIVE*
# EXEC: create a new java project
# EXEC: in Package Explorer: select your new project and invoke the context menu and verify that there's no *OpenShift* entry in it
Result:
There's an *OpenShift* entry in the context menu even though the project is not an OpenShift project
was:
# ASSERT: make sure you have a clean workspace (eventually remove and recreate it)
# ASSERT: make sure that you dont have OpenShift Explorer opened, dont have any OpenShift server adapter
# EXEC: restart Eclipse
# ASSERT: verify in the OSGI console that the OpenShift UI plugin is NOT *ACTIVE*
# EXEC: create a new java project
# EXEC: in Package Explorer: select your new project and invoke the context menu and verify that there's no *OpenShift* entry in it
Result:
There's an *OpenShift* entry in the context menu even though the project is not an OpenShift project
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
> Attachments: package-explorer-nonopenshift.png, package-explorer-openshift.png, project-explorer-nonopenshift.png, project-explorer-openshift.png
>
>
> The OpenShift menu contribution is visible when right-clicking any Eclipse project (not only an OpenShift project).
> The issue happens because the org.jboss.tools.openshift.express.ui.openshiftProjectPropertyTester property tester isn't declared correctly.
> Also, its icon (marker.png) is too large for a context menu action.
--
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, 8 months
[JBoss JIRA] (JBIDE-15205) OpenShift menu contribution issue
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15205:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have a clean workspace (eventually remove and recreate it)
# ASSERT: make sure that you dont have OpenShift Explorer opened, dont have any OpenShift server adapter
# EXEC: restart Eclipse
# EXEC: create a new java project
# EXEC: in Package Explorer: select your new project and invoke the context menu and verify that there's no *OpenShift* entry in it
Result:
There's an *OpenShift* entry in the context menu even though the project is not an OpenShift project
Workaround Description: open the OpenShift Explorer, make sure you have an OpenShift server adapter or launch the OpenShift wizard just to make sure the openshift.ui plugin is active.
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
> Attachments: package-explorer-nonopenshift.png, package-explorer-openshift.png, project-explorer-nonopenshift.png, project-explorer-openshift.png
>
>
> The OpenShift menu contribution is visible when right-clicking any Eclipse project (not only an OpenShift project).
> The issue happens because the org.jboss.tools.openshift.express.ui.openshiftProjectPropertyTester property tester isn't declared correctly.
> Also, its icon (marker.png) is too large for a context menu action.
--
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, 8 months
[JBoss JIRA] (JBIDE-15205) OpenShift menu contribution issue
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15205:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have a clean workspace (eventually remove and recreate it)
# ASSERT: make sure that you dont have OpenShift Explorer opened, dont have any OpenShift server adapter
# EXEC: restart Eclipse
# ASSERT: verify in the OSGI console that the OpenShift UI plugin is NOT *ACTIVE*
# EXEC: create a new java project
# EXEC: in Package Explorer: select your new project and invoke the context menu and verify that there's no *OpenShift* entry in it
Result:
There's an *OpenShift* entry in the context menu even though the project is not an OpenShift project
was:
# ASSERT: make sure you have a clean workspace (eventually remove and recreate it)
# ASSERT: make sure that you dont have OpenShift Explorer opened, dont have any OpenShift server adapter
# EXEC: restart Eclipse
# EXEC: create a new java project
# EXEC: in Package Explorer: select your new project and invoke the context menu and verify that there's no *OpenShift* entry in it
Result:
There's an *OpenShift* entry in the context menu even though the project is not an OpenShift project
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
> Attachments: package-explorer-nonopenshift.png, package-explorer-openshift.png, project-explorer-nonopenshift.png, project-explorer-openshift.png
>
>
> The OpenShift menu contribution is visible when right-clicking any Eclipse project (not only an OpenShift project).
> The issue happens because the org.jboss.tools.openshift.express.ui.openshiftProjectPropertyTester property tester isn't declared correctly.
> Also, its icon (marker.png) is too large for a context menu action.
--
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, 8 months
[JBoss JIRA] (JBIDE-15205) OpenShift menu contribution issue
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15205:
-------------------------------------
Issue Type: Bug (was: Feature Request)
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
> Attachments: package-explorer-nonopenshift.png, package-explorer-openshift.png, project-explorer-nonopenshift.png, project-explorer-openshift.png
>
>
> The OpenShift menu contribution is visible when right-clicking any Eclipse project (not only an OpenShift project).
> The issue happens because the org.jboss.tools.openshift.express.ui.openshiftProjectPropertyTester property tester isn't declared correctly.
> Also, its icon (marker.png) is too large for a context menu action.
--
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, 8 months