[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac
by Xia Zhao (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ]
Xia Zhao updated JBIDE-22133:
-----------------------------
Steps to Reproduce:
1. Login openshift from JBDS installed on Mac OS
2. Create a new project
3. Create a new application from local template
Actual Result:
2. Operation failed, get error msg:
Could not create project "xiazhao-jbt": the body of the request was in an unknown format - accepted media types include: application/json, application/yaml
Could not create resource xiazhao-jbt in namespace '': {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the body of the request was in an unknown format - accepted media types include: application/json, application/yaml","reason":"UnsupportedMediaType","code":415}
3. Operation failed, get error msg:
the body of the request was in an unknown format - accepted media types include: application/json, application/yaml
Could not create resource ruby-helloworld-sample in namespace 'xiazhao-jbt': {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the body of the request was in an unknown format - accepted media types include: application/json, application/yaml","reason":"UnsupportedMediaType","code":415}
Expected Result:
step 2,3 should be successful
Additional info:
Issue did not repro on Fedora 22 and Windows 10 OS
was:
Steps to Reproduce:
1. Login online with JBT
2. Go to your project, populate the property panel of your service
3. choose a bc, right click on it, look at the context-menu name of Start build
Actual Result:
context-menu name is "Start Build ()"
Expected Result:
The "()" from context-menu name of Start build should be removed
> Get error "UnsupportedMediaType' when create project/applications from JBT on Mac
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22133
> URL: https://issues.jboss.org/browse/JBIDE-22133
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262
> Mac OS
> Reporter: Xia Zhao
> Priority: Minor
> Labels: openshift_v3
>
> The "()" from context-menu name of Start Build should be removed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3779) Consider changing the installation order
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3779?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3779:
------------------------------
Description:
Right now there are the following installation 'streams':
1. JDK -> JBDS - looks fine to me
2. Virtualbox -> Cygwin -> Vagrant -> CDK - this is the one I have an issue with.
The second stream starts with Virtualbox which first needs to be downloaded. Maybe some other component could do something productive while Virtualbox is downloading so it might save some time. In other words - could something other than a download start the installation?
was:
Right now there are the following installation 'streams':
1. JDK -> JBDS - looks fine to me
2. Virtualbox -> Cygwin -> Vagrant -> CDK - this is the one I have an issue with.
The seconds stream starts with Virtualbox which first needs to be downloaded. Maybe some other component could do something productive while Virtualbox is downloading so it might save some time. In other words - could something other than a download start the installation?
> Consider changing the installation order
> ----------------------------------------
>
> Key: JBDS-3779
> URL: https://issues.jboss.org/browse/JBDS-3779
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
>
> Right now there are the following installation 'streams':
> 1. JDK -> JBDS - looks fine to me
> 2. Virtualbox -> Cygwin -> Vagrant -> CDK - this is the one I have an issue with.
> The second stream starts with Virtualbox which first needs to be downloaded. Maybe some other component could do something productive while Virtualbox is downloading so it might save some time. In other words - could something other than a download start the installation?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3779) Consider changing the installation order
by Jan Richter (JIRA)
Jan Richter created JBDS-3779:
---------------------------------
Summary: Consider changing the installation order
Key: JBDS-3779
URL: https://issues.jboss.org/browse/JBDS-3779
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
Assignee: Denis Golovin
Right now there are the following installation 'streams':
1. JDK -> JBDS - looks fine to me
2. Virtualbox -> Cygwin -> Vagrant -> CDK - this is the one I have an issue with.
The seconds stream starts with Virtualbox which first needs to be downloaded. Maybe some other component could do something productive while Virtualbox is downloading so it might save some time. In other words - could something other than a download start the installation?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22132) Resource name is badly generated in Deploy to Openshift wizard
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-22132:
----------------------------------
Summary: Resource name is badly generated in Deploy to Openshift wizard
Key: JBIDE-22132
URL: https://issues.jboss.org/browse/JBIDE-22132
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Reporter: Jeff MAURY
Fix For: 4.4.x
When the wizard for deploying a Docker image to Openshift is displayed, the resource name is derived from the image name. But as the '_' seems to be forbidden, an error is generated each time the image name contains this character. Maybe worth replacing with '-' when the resource name is generated
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 8 or above on windows
by Tobias van den Berg (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ]
Tobias van den Berg commented on JBIDE-22078:
---------------------------------------------
Strange, I can't reproduce the difference in behaviour either right now with a simple test application. I can reproduce it only with a large complicated .ear project. But I don't think it's important, if the error is fixed it should both work for Wildfly 8 and Wildfly 10.
> Error publishing war file to wildfy 8 or above on windows
> ---------------------------------------------------------
>
> Key: JBIDE-22078
> URL: https://issues.jboss.org/browse/JBIDE-22078
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: - Windows 7 x64
> - jdk1.8.0_77 (32-bit)
> - Eclipse Mars.2 (32-bit)
> - JBoss Tools 4.3.0.FINAL
> - Wildfly 10.0.0.FINAL
> Reporter: Tobias van den Berg
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
> Attachments: Logfile.PML
>
>
> The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
> "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor."
> The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
> I've tried/tested the following:
> - Checked/updated Windows file permisions for the wildfly directory
> - Take ownership of the wildfly directory (recursively)
> - Disabled Windows User Account Control (UAC)
> - Run Eclipse as Admin
> Relates to:
> - JBIDE-18697
> - JBIDE-17545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years