[JBoss JIRA] (JBIDE-20257) Cannot create any new project via OpenShift Projects dialog
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20257:
-------------------------------------
Summary: Cannot create any new project via OpenShift Projects dialog
Key: JBIDE-20257
URL: https://issues.jboss.org/browse/JBIDE-20257
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta2
Reporter: Marián Labuda
Priority: Blocker
In OpenShift Projects dialog opened via context menu of a v3 application, it is not possible to create a new project. There is a error that project is trying to be created in cluster scope. See full error description below:
{code}
Could not create project "project01dsa": User "demo" cannot create projects at the cluster scope
com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot create projects at the cluster scope
at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:393)
at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:185)
at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:169)
at org.jboss.tools.openshift.core.connection.Connection.createResource(Connection.java:316)
at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizardModel.createProject(NewProjectWizardModel.java:55)
at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:46)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
This is happening also on locally running OpenShift v3 and also on staging v3 server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20184) Launching with Java 7 in jbdevstudio.ini results in module errors in subsequent launches with Java 8
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20184?page=com.atlassian.jira.plugi... ]
Jan Richter commented on JBIDE-20184:
-------------------------------------
Removing the log file or just changing workspace before restarting stops the error from appearing again.
> Launching with Java 7 in jbdevstudio.ini results in module errors in subsequent launches with Java 8
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20184
> URL: https://issues.jboss.org/browse/JBIDE-20184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.0.Beta1
> Reporter: Jan Richter
> Assignee: Daniel Azarov
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
> Attachments: warning.png
>
>
> When I launch JBDS with the -vm parameter in jbdevstudio.ini set to Java 7 and then try to launch it again with Java 8, I get a warning that a number of modules failed to load.
> The stated reason is they cannot be loaded with Java 8 because they require Java 8.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3450:
--------------------------------
Sprint: Sprint #6 July 2015
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta2
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months