April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22190) Application wizard: Support "URL" templates to create a new application

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22190?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-22190 at 4/28/16 9:46 AM: ------------------------------------------------------------- Yes, I agree but using the file you provided was not relevant for the required feature. The file should be processed with JBIDE-20937 But the required feature has been implemented using other sample files was (Author: jeffmaury): Yes, I agree but using the file you provided was not relevant for the required feature. The file should be processed with JBIDE-20937 > Application wizard: Support "URL" templates to create a new application > ----------------------------------------------------------------------- > > Key: JBIDE-22190 > URL: https://issues.jboss.org/browse/JBIDE-22190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Currently, we can choose on the server template or to use a local template. it would be nice to be able to use an URL template too. > My current use case: I want to create a Fuse Integration Service application based on a template which is available on github at https://raw.githubusercontent.com/jboss-fuse/application-templates/master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22190) Application wizard: Support "URL" templates to create a new application

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22190?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22190: ------------------------------------ Yes, I agree but using the file you provided was not relevant for the required feature. The file should be processed with JBIDE-20937 > Application wizard: Support "URL" templates to create a new application > ----------------------------------------------------------------------- > > Key: JBIDE-22190 > URL: https://issues.jboss.org/browse/JBIDE-22190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Currently, we can choose on the server template or to use a local template. it would be nice to be able to use an URL template too. > My current use case: I want to create a Fuse Integration Service application based on a template which is available on github at https://raw.githubusercontent.com/jboss-fuse/application-templates/master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20938) Report proper error when blog author is unknown

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20938?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20938: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Report proper error when blog author is unknown > ----------------------------------------------- > > Key: JBIDE-20938 > URL: https://issues.jboss.org/browse/JBIDE-20938 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.x > > > Building the website fails hard if a blog entry has a unknown author. There should be a proper error message instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-21823: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) Assignee: (was: Xavier Coulon) > Unable to re-edit Service config > -------------------------------- > > Key: JBIDE-21823 > URL: https://issues.jboss.org/browse/JBIDE-21823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Fix For: 4.4.x > > > Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes. > Steps to reproduce: > - select a service in the OpenShift Explorer > - click on the {{Edit...}} command. > - in the JSON editor for the service config, note the resource version. Eg: > {code} > { > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38301", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > }, > ... > {code} > - make some changes and save > - the service config version should have incremented: > {code} > { > "kind" : "Service", > "apiVersion" : "v1", > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38390", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > } > .... > {code} > - close the config editor > - re-open the config editor > *ASSERT: the editor displays the latest config* > *FAIL the editor displays the initial config* > *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version* > {code} > Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again > Could not update resource jee-sample: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "jee-sample", > "kind": "services" > }, > "code": 409 > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21608?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21608: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > "Show In -> Web Browser via Live Reload" on EJB module should be disabled > ------------------------------------------------------------------------- > > Key: JBIDE-21608 > URL: https://issues.jboss.org/browse/JBIDE-21608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.4.x > > > This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. > Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. > So for Livereload, there are these two items that should be disabled on an ejb module: > Show in -> Web Browser via Livereload > Show in -> Web Browser on External device -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21517) Disable livereload quick access option for modules on stopped server

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21517?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21517: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Disable livereload quick access option for modules on stopped server > -------------------------------------------------------------------- > > Key: JBIDE-21517 > URL: https://issues.jboss.org/browse/JBIDE-21517 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.4.x > > > Since the 'show in web browser via livereload' quick access will fail in the end. Plus context menu option on modules is already disabled when the server is not running. It might be nicer to have both options disabled in this instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21936) Disable livereload context menu on stopped server modules

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21936?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21936: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Disable livereload context menu on stopped server modules > --------------------------------------------------------- > > Key: JBIDE-21936 > URL: https://issues.jboss.org/browse/JBIDE-21936 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.4.x > > > Similar to JBIDE-21517, but this time the server is running, but the deployed project is not. Both the context menu for show in via livereload and the quick access command are enabled for a stopped module. And they just open a browser tab with 404 - not found. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21916) Build image function of Docker Tooling shows no message on console

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21916: ---------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Build image function of Docker Tooling shows no message on console > ------------------------------------------------------------------ > > Key: JBIDE-21916 > URL: https://issues.jboss.org/browse/JBIDE-21916 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Joseph Hwang > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha2 > > Attachments: 2016-03-19_8-47-37.jpg, 2016-03-23_19-38-10.jpg > > > "docker build" command show the message of build process and error on consol like below. > {code} > *_$ docker build --tag=jboss/wildfly:joseph . > Sending build context to Docker daemon 1.021 MB > Step 1 : FROM jboss/wildfly > ---> bda4b726bee1 > Step 2 : MAINTAINER Joseph Hwang "gladitor67(a)naver.com" > ---> Using cache > ---> 8914ffd24e28 > Step 3 : ENV WILDFLY_VERSION 10.0.0.Final > ---> Using cache > ---> 176b7b9a5b7f > Step 4 : ENV JBOSS_HOME /opt/jboss/wildfly > ---> Using cache > ---> 3f8d1e30f787 > Step 5 : RUN cd $HOME && curl -O https://download.jboss.org/wildfly/$WILDFLY_VERSION/wildfly-$WILDFLY_VERS... && unzip wildfly-$WILDFLY_VERSION.zip && mv $HOME/wildfly-$WILDFLY_VERSION $JBOSS_HOME && rm wildfly-$WILDFLY_VERSION.zip > ---> Using cache > ---> 454f6749ff6c > Step 6 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql > ---> Using cache > ---> 2fce5a99913c > Step 7 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql/main > ---> Using cache > ---> 1e4f8bd9aa50 > Step 8 : ADD module.xml $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ > ---> Using cache > ---> 723e4a09b3a0 > Step 9 : ADD mysql-connector-java-5.1.38-bin.jar $JBOSS_HOME/modules/system/layers/base/com/mysql/main/ > ---> Using cache > ---> 7cc730359445 > Step 10 : ADD standalone.xml $JBOSS_HOME/standalone/configuration/ > ---> Using cache > ---> 9ac873838925 > Successfully built 79d34c841245_* > {code} > But in JBossTools there is no message shown on console except progress bar. > !2016-03-19_8-47-37.jpg! > I recommend the 'build image function of docker tooling' to show the build message on console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22195: ---------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha2 > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21983) RuntimeException when trying to see Docker containers/images

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21983?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21983: ---------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > RuntimeException when trying to see Docker containers/images > ------------------------------------------------------------ > > Key: JBIDE-21983 > URL: https://issues.jboss.org/browse/JBIDE-21983 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > 1. CDK sever adapter -> Show In -> Docker Explorer > 2. Unfold Containers or Images of the rhel-ose CDK Server: > {code} > java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152) > at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120) > at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:95) > at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:106) > at org.glassfish.jersey.client.JerseyWebTarget.<init>(JerseyWebTarget.java:82) > at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:192) > at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:70) > at com.spotify.docker.client.DefaultDockerClient.resource(DefaultDockerClient.java:1051) > at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:320) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:787) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750) > at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:122) > at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:225) > at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:135) > ... 12 more > Caused by: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.internalCreate(ServiceLocatorFactoryImpl.java:266) > at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.create(ServiceLocatorFactoryImpl.java:247) > at org.glassfish.jersey.internal.inject.Injections._createLocator(Injections.java:138) > at org.glassfish.jersey.internal.inject.Injections.createLocator(Injections.java:109) > at org.glassfish.jersey.internal.RuntimeDelegateImpl.<init>(RuntimeDelegateImpl.java:61) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118) > ... 14 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016