[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
11 years, 4 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
11 years, 4 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
11 years, 4 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
11 years, 4 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
11 years, 4 months
[JBoss JIRA] (JBIDE-15313) Handle Wildfly multi-plexing possibility
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-15313:
-----------------------------------
Summary: Handle Wildfly multi-plexing possibility
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
11 years, 4 months
[JBoss JIRA] (JBIDE-13242) Seam 2.3: seam-gen generated project, JBDS reports missing files referenced from view-id in pages.xml
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13242?page=com.atlassian.jira.plugi... ]
Marek Novotny commented on JBIDE-13242:
---------------------------------------
OK, so I understand it like we need to have Project Facet type for seam-gen generated project, is that 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
11 years, 4 months
[JBoss JIRA] (JBIDE-12915) Kitchensink quickstart is missing .cheatsheet.xml
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12915?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-12915:
---------------------------------------
I have updated the PR. Now, it uses the commands introduced by https://issues.jboss.org/browse/JBIDE-14333
This cheatsheet will work with a project example based on an archetype if you copy a project to the workspace and import it or rename the project.
The following are the main changes:
1) At the beginning of the cheatsheet, you will see the following command:
<command
required="true"
returns="currentProject"
serialization="org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet"/>
The command is obliged because it sets the currentProject variable.
After that, the currentProject variable is used instead of the hard-coded project name.
For instance:
<command
required="true" serialization="org.jboss.tools.project.examples.cheatsheet.openFileInEditor(path=/${currentProject}/src/main/webapp/WEB-INF/templates/default.xhtml,fromLine=22,toLine=26
or
<action
pluginId="org.jboss.tools.project.examples.cheatsheet"
class="org.jboss.tools.project.examples.cheatsheet.actions.RunOnServer"
param1="${currentProject}"/>
Within the action, it is possible to use a variable like
param1="${currentProject}"
but is not possible to use a variable as
paramN="/${currentProject}/src/main/webapp/WEB-INF/templates/default.xhtml"
The currentProject variable in the paramN attribute won't be translated which means the openFileInEditor command must be used instead of the org.jboss.tools.project.examples.cheatsheet.actions.OpenFileInEditor action.
We also need to add the runOnServer and launchJUnitTest command.
> Kitchensink quickstart is missing .cheatsheet.xml
> -------------------------------------------------
>
> Key: JBIDE-12915
> URL: https://issues.jboss.org/browse/JBIDE-12915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.0.0.Beta1
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.0.0.CR1
>
>
> After importing Kitchensink example from section "JBoss Developer Framework Quickstarts" in JBoss Central, user is prompted to
> {noformat}Show '/jboss-as-kitchensink/.cheatsheet.xml' for further instructions{noformat}
> but /jboss-as-kitchensink/.cheatsheet.xml does not exist.
> Imported quickstart is named "kitchensink" instead of jboss-as-kitchensink and it has README.md instead of .cheatsheet.xml
--
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
11 years, 4 months