[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 commented on JBIDE-15291:
------------------------------------------------
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 commented on JBIDE-15205:
------------------------------------------
I watched OpenShift UI plugin getting started and found out that it gets awaken via the OpenShift Server adapter. Chatting to Rob and Rob chatting to Paul Webster we found out that bundle started-states may be persisted if specific osgi API's are used. Apparently these are used in ASTools:
{quote}
5:07:23 PM] … <paulweb515> rawbdor: yes (but no :-)
<paulweb515> rawbdor: if a bundle is started due to classloading (something caused a class to load) then it won't automatically start during the next sessions until another class gets loaded
<paulweb515> rawbdor: if someone starts a bundle using org.osgi.framework.Bundle and doesn't use org.osgi.framework.Bundle.START_TRANSIENT that bundle *will* be started on the next session startup
{quote}
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> 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-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:26 AM:
--------------------------------------------------------------------------
[~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!
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.
> 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 commented on JBIDE-15291:
------------------------------------------------
[~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.
> 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 updated JBIDE-15291:
-------------------------------------------
Attachment: 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-15205) OpenShift menu contribution issue
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15205 at 7/31/13 9:54 AM:
-------------------------------------------------------------------
Thanks for the lengthy explanation and steps. I did not manage to reproduce it in JBDS immediately, it took several tries and I had to use a fresh workspace and clear the .settings directory. I could not reproduce it with a fresh Eclipse and JBT 4.1.GA out-of-the-box. ere, too, I had to clear my existing workspace and remove the .settings.
The erroneous *OpenShift* entry in the context menu of a non-openshift project also disappears as soon as you activate the OpenShift UI plugin (by opening the OpenShift Explorer or launching the OpenShift application wizard)
was (Author: adietish):
Thanks for the lengthy explanation and steps. I did not manage to reproduce it in JBDS immediately, it took several tries and I had to use a fresh workspace and clear the .settings directory. I could not reproduce it with a fresh Eclipse and JBT 4.1.GA out-of-the-box. ere, too, I had to clear my existing workspace and remove the .settings.
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> 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 edited comment on JBIDE-15205 at 7/31/13 9:46 AM:
-------------------------------------------------------------------
Thanks for the lengthy explanation and steps. I did not manage to reproduce it in JBDS immediately, it took several tries and I had to use a fresh workspace and clear the .settings directory. I could not reproduce it with a fresh Eclipse and JBT 4.1.GA out-of-the-box. ere, too, I had to clear my existing workspace and remove the .settings.
was (Author: adietish):
Thanks for the lengthy explanation and steps. I did not manage to reproduce it immediately, it took several tries. I could not reproduce it with a fresh Eclipse and JBT 4.1.GA installed to it out-of-the-box. In both cases, I had to use a fresh workspace and clear the .settings file.
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> 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 commented on JBIDE-15205:
------------------------------------------
Thanks for the lengthy explanation and steps. I did not manage to reproduce it immediately, it took several tries. I could not reproduce it with a fresh Eclipse and JBT 4.1.GA installed to it out-of-the-box. In both cases, I had to use a fresh workspace and clear the .settings file.
> OpenShift menu contribution issue
> ---------------------------------
>
> Key: JBIDE-15205
> URL: https://issues.jboss.org/browse/JBIDE-15205
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> 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-15313) Investigate how to handle Wildfly port multiplexing
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15313?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15313:
--------------------------------
Summary: Investigate how to handle Wildfly port multiplexing (was: Handle Wildfly multi-plexing possibility)
> Investigate how to handle Wildfly port multiplexing
> ----------------------------------------------------
>
> Key: JBIDE-15313
> URL: https://issues.jboss.org/browse/JBIDE-15313
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.1.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
>
> While JBIDE-14979 and JBIDE-14402 assist in getting wildfly to work out-of-the-box, it does not assist in the possibility of turning multi-plexing on and off. This jira may include additions to UI and API, though it may NOT require both. It remains to be seen.
> This jira will investigate what's necessary and what may need to change.
--
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