[JBoss JIRA] (JBIDE-22992) OpenShift tools use wrong rest client bits
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22992?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22992:
------------------------------------------
The update site contains the correct, latest client plugin: http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ope...
{code}
<artifact classifier="osgi.bundle" id="org.jboss.tools.openshift.client" version="3.3.0.AM3-v20160812-0237-B1502">
{code}
Build [#1502|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1502/consoleFull] built the correct client plugin and it was subsequently published
{code}
++ /home/hudson/static_build_env/jbds/p2diff/x86_64/p2diff file:///tmp/tmp.3QOvABVoMw/ws/sources/site/target/repository/ http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ope... -vmargs -Dosgi.locking=none
++ egrep '<|>'
++ egrep -v '(<|>) (Alpha[0-9]+|AM[0-9]+|Beta[0-9]+|CR[0-9]+|Final|GA).+-B[0-9]+\.'
+ [[ -n < org.jboss.tools.openshift.cdk.feature.source.feature.jar [3.3.0.v20160812-0237]
< org.jboss.tools.openshift.feature.feature.group [3.3.0.v20160812-0237]
< org.jboss.tools.openshift.ui.source [3.3.0.v20160812-0126]
< org.jboss.tools.openshift.cdk.feature.feature.group [3.3.0.v20160812-0237]
< org.jboss.tools.openshift.feature.feature.jar [3.3.0.v20160812-0237]
< org.jboss.tools.openshift.client [3.3.0.AM3-v20160812-0237-B1502]
< org.jboss.tools.openshift.cdk.feature.source.feature.group [3.3.0.v20160812-0237]
< org.jboss.tools.openshift.cdk.feature.feature.jar [3.3.0.v20160812-0237]
< v20160812-0237.JBoss Tools OpenShift Nightly Build Update Site [1.0.0.8V8U-cKm-e1ES0z0-Wy2dO8VdI7u]
< org.jboss.tools.openshift.client.source [3.3.0.AM3-v20160812-0237-B1502]
< org.jboss.tools.openshift.core [3.3.0.v20160811-2313]
< org.jboss.tools.openshift.ui [3.3.0.v20160812-0126]
< org.jboss.tools.openshift.core.source [3.3.0.v20160811-2313]
< org.jboss.tools.openshift.feature.source.feature.jar [3.3.0.v20160812-0237]
< org.jboss.tools.openshift.feature.source.feature.group [3.3.0.v20160812-0237]
> org.jboss.tools.openshift.ui [3.3.0.v20160811-2233]
> org.jboss.tools.openshift.feature.source.feature.jar [3.3.0.v20160811-2312]
> org.jboss.tools.openshift.ui.source [3.3.0.v20160811-2233]
> org.jboss.tools.openshift.cdk.feature.feature.group [3.3.0.v20160811-2312]
> org.jboss.tools.openshift.client.source [3.3.0.AM3-v20160811-2312-B1501]
> org.jboss.tools.openshift.feature.source.feature.group [3.3.0.v20160811-2312]
> org.jboss.tools.openshift.cdk.feature.source.feature.jar [3.3.0.v20160811-2312]
> org.jboss.tools.openshift.client [3.3.0.AM3-v20160811-2312-B1501]
> v20160811-2312.JBoss Tools OpenShift Nightly Build Update Site [1.0.0._09U-cKm-e1EbNVv6a-BN12qSqJQVVz0UyavVVyT]
> org.jboss.tools.openshift.feature.feature.group [3.3.0.v20160811-2312]
> org.jboss.tools.openshift.cdk.feature.feature.jar [3.3.0.v20160811-2312]
> org.jboss.tools.openshift.core [3.3.0.v20160811-2233]
> org.jboss.tools.openshift.core.source [3.3.0.v20160811-2233]
> org.jboss.tools.openshift.cdk.feature.source.feature.group [3.3.0.v20160811-2312]
> org.jboss.tools.openshift.feature.feature.jar [3.3.0.v20160811-2312] ]]
{code}
{code}
Build was marked for publishing on https://hudson.jboss.org/hudson/
{code}
> OpenShift tools use wrong rest client bits
> ------------------------------------------
>
> Key: JBIDE-22992
> URL: https://issues.jboss.org/browse/JBIDE-22992
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.1.AM3
> Environment: eclipse.buildId=10.1.0.AM3-v20160810-0441-B5735
> java.version=1.8.0_101
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.1.AM3
>
> Attachments: IU-unchanged-not-published.png, openshift-client-IU-new-timestamp.png, openshift-client-IU.png
>
>
> An internal error occurred during: "Loading service-manager to configure additional frameworks that CDK depends on.".{code}java.lang.NoSuchMethodError: com.openshift.restclient.ClientBuilder.withMaxRequests(I)Lcom/openshift/restclient/ClientBuilder;
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:53)
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:77)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:55)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:91)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:56)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:44)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-830) JBTIS 4.3.2/ JBDSIS 9.0.2
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-830:
--------------------------------
Summary: JBTIS 4.3.2/ JBDSIS 9.0.2
Key: JBTIS-830
URL: https://issues.jboss.org/browse/JBTIS-830
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: distribution
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.3.2.CR1, 9.0.2.CR1
Generic Jira for metadata and POM changes associated with JBTIS 4.3.2/ JBDSIS 9.0.2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22817) Add Events support to Properties view
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22817?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22817.
---------------------------------
Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753.
> Add Events support to Properties view
> -------------------------------------
>
> Key: JBIDE-22817
> URL: https://issues.jboss.org/browse/JBIDE-22817
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: explorer, new_and_noteworthy, openshift_v3
> Fix For: 4.4.1.AM3
>
> Attachments: Screenshot.png
>
>
> The web console has an Events tab that lists all events for all resources. We could add the same to the Properties view.
> Later, we could add support for events per resources, but that requires more work how to layout more infos. That'll be the subject of another issue
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22433.
---------------------------------
Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753.
> Properties: Add Storage tab
> ---------------------------
>
> Key: JBIDE-22433
> URL: https://issues.jboss.org/browse/JBIDE-22433
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Dmitry Bocharov
> Labels: new_and_noteworthy, openshift_v3, properties
> Fix For: 4.4.1.AM3
>
> Attachments: storage from web console.png
>
>
> We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties.
> Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides.
> Using persistent volumes:
> # https://blog.openshift.com/experimenting-with-persistent-volumes/
> # https://docs.openshift.com/enterprise/3.0/dev_guide/persistent_volumes.html
> Briefly: to see how persistent volume claims work, add the following json as a resource to the project:
> {code:title=Persistent Volume Claim Object Definition}
> {
> "apiVersion": "v1",
> "kind": "PersistentVolumeClaim",
> "metadata": {
> "name": "claim1"
> },
> "spec": {
> "accessModes": [ "ReadWriteOnce" ],
> "resources": {
> "requests": {
> "storage": "1Gi"
> }
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-819?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-819.
------------------------------
Fix Version/s: 9.0.2.GA
(was: 9.0.1.GA)
Resolution: Done
About icons fixed by Lars - will see it in 9.0.2.
> Update fuse icons for 9.0.1.GA
> ------------------------------
>
> Key: JBTIS-819
> URL: https://issues.jboss.org/browse/JBTIS-819
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution, Fuse IDE
> Affects Versions: 9.0.1.CR3
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 9.0.2.GA
>
> Attachments: jbdsis901ga_camel_icon1.png, jbdsis901ga_camel_icon2.png
>
>
> Update the fuse icons - they are out of date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22079) Import wizard: Error when import a project already existing in workspace
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22079.
---------------------------------
Verified in DevStudio 10.1.0.AM3 build ID AM3-v20160812-0415-B5753.
> Import wizard: Error when import a project already existing in workspace
> ------------------------------------------------------------------------
>
> Key: JBIDE-22079
> URL: https://issues.jboss.org/browse/JBIDE-22079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.1.AM3
>
> Attachments: import-error.png
>
>
> When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear).
> Error:
> {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts.
> One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again.
> An exception stack trace is not available.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22274) Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ]
Jeff Johnston resolved JBIDE-22274.
-----------------------------------
Resolution: Done
> Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22274
> URL: https://issues.jboss.org/browse/JBIDE-22274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247
> Reporter: Radim Hopp
> Assignee: Jeff Johnston
> Fix For: 4.4.1.AM3
>
>
> Start docker container with -v parameter pointing to some file. For example: "docker run -d -p 5000:5000 -v /home/rhopp/temp/config.yml_new:/etc/docker/registry/config.yml --name registry1 registry:2"
> Go to Docker Explorer, expand running container->right click on the only volume in there->Show In->System Explorer-> Error is logged:
> {noformat:title=Failed to open in Web Browser}
> java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/rhopp/temp/config.yml_new"): error=20, Not a directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:99)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: error=20, Not a directory
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:248)
> at java.lang.ProcessImpl.start(ProcessImpl.java:134)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3627:
-------------------------------------------
gah - okey. then yeah, [~dhladky] should help you find a way to create a user that don't have permissions.
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months