May 2016 - jbosstools-issues - Jboss List Archives

[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: ---------------------------------- Story Points: 1 (was: 2) > 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-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: ---------------------------------- Story Points: 1 (was: 2) > "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-22177) Docker Image host is missing from Deployment Config when deploying from a private registry

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22177?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22177: -------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) Story Points: 2 > Docker Image host is missing from Deployment Config when deploying from a private registry > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22177 > URL: https://issues.jboss.org/browse/JBIDE-22177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > > If you deploy a docker image from myregistry:5000/example/myimage, the deployment config is generated with only example/myimage, so can't find the image to deploy -- 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: ---------------------------------- Story Points: 3 > 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-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: ---------------------------------- Story Points: 1 > 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-22193) Can't deploy locally built docker images

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22193: ----------------------------------- Story Points: 18 Assignee: Xavier Coulon > Can't deploy locally built docker images > ---------------------------------------- > > Key: JBIDE-22193 > URL: https://issues.jboss.org/browse/JBIDE-22193 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift, upstream > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > I can't deploy locally built docker images, pushed to the CDK docker registry, to OpenShift > Trying to adapt the steps from https://github.com/redhat-developer-tooling/openshift-vagrant#how-to-run-... to Eclipse, I can't seem to be able to deploy anything > Here's what the CLI generates from > {quote} > eval "$(vagrant service-manager env docker)" > $ oc login 10.1.2.2:8443 -u openshift-dev -p devel > Login successful. > $ oc new-project my-ghost > Now using project "my-ghost" on server "https://10.1.2.2:8443". > $ docker pull ghost > $ docker tag ghost hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost > $ docker login -u openshift-dev -p `oc whoami -t` -e foo(a)bar.com hub.openshift.rhel-cdk.10.1.2.2.xip.io > $ docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost > $ oc new-app --image-stream=ghost --name=ghost > $ oc expose service ghost --hostname=my-ghost-blog.rhel-cdk.10.1.2.2.xip.io > {quote} > Deployment Config > {noformat} > { > "kind" : "DeploymentConfig", > "apiVersion" : "v1", > "metadata" : { > "name" : "ghost", > "namespace" : "my-ghost", > "selfLink" : "/oapi/v1/namespaces/my-ghost/deploymentconfigs/ghost", > "uid" : "a7dafee5-03c8-11e6-82b7-525400ac6ae1", > "resourceVersion" : "29849", > "creationTimestamp" : "2016-04-16T11:45:02Z", > "labels" : {"app" : "ghost"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftNewApp"} > }, > "spec" : { > "strategy" : { > "type" : "Rolling", > "rollingParams" : { > "updatePeriodSeconds" : 1, > "intervalSeconds" : 1, > "timeoutSeconds" : 600, > "maxUnavailable" : "25%", > "maxSurge" : "25%" > } > }, > "triggers" : [ > {"type" : "ConfigChange"}, > { > "type" : "ImageChange", > "imageChangeParams" : { > "automatic" : true, > "containerNames" : ["ghost"], > "from" : { > "kind" : "ImageStreamTag", > "namespace" : "my-ghost", > "name" : "ghost:latest" > }, > "lastTriggeredImage" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8" > } > } > ], > "replicas" : 1, > "selector" : { > "app" : "ghost", > "deploymentconfig" : "ghost" > }, > "template" : { > "metadata" : { > "labels" : { > "app" : "ghost", > "deploymentconfig" : "ghost" > }, > "annotations" : { > "openshift.io/container.ghost.image.entrypoint" : "[\"/entrypoint.sh\",\"npm\",\"start\"]", > "openshift.io/generated-by" : "OpenShiftNewApp" > } > }, > "spec" : { > "volumes" : [{"name" : "ghost-volume-1"}], > "containers" : [{ > "name" : "ghost", > "image" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8", > "ports" : [{ > "containerPort" : 2368, > "protocol" : "TCP" > }], > "volumeMounts" : [{ > "name" : "ghost-volume-1", > "mountPath" : "/var/lib/ghost" > }], > "terminationMessagePath" : "/dev/termination-log", > "imagePullPolicy" : "Always" > }], > "restartPolicy" : "Always", > "terminationGracePeriodSeconds" : 30, > "dnsPolicy" : "ClusterFirst" > } > } > }, > "status" : { > "latestVersion" : 1, > "details" : {"causes" : [{"type" : "ConfigChange"}]} > } > } > {noformat} > Image Stream > {noformat} > { > "kind" : "ImageStream", > "apiVersion" : "v1", > "metadata" : { > "name" : "ghost", > "namespace" : "my-ghost", > "selfLink" : "/oapi/v1/namespaces/my-ghost/imagestreams/ghost", > "uid" : "98a32494-03c8-11e6-82b7-525400ac6ae1", > "resourceVersion" : "29842", > "creationTimestamp" : "2016-04-16T11:44:37Z", > "annotations" : {"openshift.io/image.dockerRepositoryCheck" : "2016-04-16T11:44:37Z"} > }, > "status" : { > "dockerImageRepository" : "172.30.178.20:5000/my-ghost/ghost", > "tags" : [{ > "tag" : "latest", > "items" : [{ > "created" : "2016-04-16T11:44:37Z", > "dockerImageReference" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8", > "image" : "sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8" > }] > }] > } > } > {noformat} > When following these steps in Eclipse, no deployment occurs. Going to the web console et clicking deploy on the Deployment, no image is found to deploy. > {quote} > - Clone https://github.com/burrsutter/cdk_helloworlds/ > - import java/wildflyswarm_helloworld as a Maven Project > - Run a Maven build (Run As > Maven > package) > - Edit Dockerfile: replace `FROM rhel7` with `FROM centos` > - right click on Dockerfile > Run As > Docker Image build > - Select `CDK Server Adapter at localhost` connection > - Repository Name : hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm > - from OpenShift explorer, create a fredo project > - In OpenShift explorer, right-click the fredo project and Deploy Docker Image... > - select hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm:latest for the image > - swarm as resource name > - click next > - Deployment configuration & scalability page displays, click next > - click add route button, click finish > - resources are created, but no deployment happens > {quote} > Here are the resources created from Eclipse: > Deployment Config > {noformat} > { > "metadata" : { > "name" : "swarm", > "namespace" : "fredo", > "selfLink" : "/oapi/v1/namespaces/fredo/deploymentconfigs/swarm", > "uid" : "2e9d1df4-03cc-11e6-82b7-525400ac6ae1", > "resourceVersion" : "30206", > "creationTimestamp" : "2016-04-16T12:10:17Z", > "labels" : {"deploymentconfig" : "swarm"}, > "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"} > }, > "spec" : { > "strategy" : { > "type" : "Rolling", > "rollingParams" : { > "updatePeriodSeconds" : 1, > "intervalSeconds" : 1, > "timeoutSeconds" : 600, > "maxUnavailable" : "25%", > "maxSurge" : "25%" > } > }, > "triggers" : [ > {"type" : "ConfigChange"}, > { > "type" : "ImageChange", > "imageChangeParams" : { > "automatic" : true, > "containerNames" : ["swarm"], > "from" : { > "kind" : "ImageStreamTag", > "name" : "swarm:latest" > } > } > } > ], > "replicas" : 1, > "selector" : {"deploymentconfig" : "swarm"}, > "template" : { > "metadata" : {"labels" : {"deploymentconfig" : "swarm"}}, > "spec" : { > "containers" : [{ > "name" : "swarm", > "image" : "fredo/swarm:latest", > "ports" : [{ > "name" : "8080-tcp", > "containerPort" : 8080, > "protocol" : "TCP" > }], > "terminationMessagePath" : "/dev/termination-log", > "imagePullPolicy" : "Always" > }], > "restartPolicy" : "Always", > "terminationGracePeriodSeconds" : 30, > "dnsPolicy" : "ClusterFirst" > } > } > }, > "apiVersion" : "v1", > "kind" : "DeploymentConfig" > } > {noformat} > Image Stream > {noformat} > { > "metadata" : { > "name" : "swarm", > "namespace" : "fredo", > "selfLink" : "/oapi/v1/namespaces/fredo/imagestreams/swarm", > "uid" : "2e42dfc8-03cc-11e6-82b7-525400ac6ae1", > "resourceVersion" : "30202", > "creationTimestamp" : "2016-04-16T12:10:16Z", > "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"} > }, > "spec" : {"dockerImageRepository" : "hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm"}, > "status" : {"dockerImageRepository" : "172.30.178.20:5000/fredo/swarm"}, > "apiVersion" : "v1", > "kind" : "ImageStream" > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21422) Server adapter editor: details should be editable

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21422?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21422: -------------------------------- Sprint: (was: devex #114 May 2017) > Server adapter editor: details should be editable > ------------------------------------------------- > > Key: JBIDE-21422 > URL: https://issues.jboss.org/browse/JBIDE-21422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha2 > > > Currently when I open a server adapter overview (by double click on a server adapter) there is whole section of details to which project it is bind to, paths etc. in the Project Settings section. This area is not editable. It would be nice to allow user modify this, to allow to choose different eclipse project or fix path if it was filled in wrong... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22292) Add support for private registry authentication

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22292: ----------------------------------- Summary: Add support for private registry authentication Key: JBIDE-22292 URL: https://issues.jboss.org/browse/JBIDE-22292 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: docker Reporter: Fred Bricon we need to authenticate to openshift docker registry to push images -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22227. --------------------------------- Resolution: Done > Hotcode replace fails on local wildfly if breakpoint is set > ----------------------------------------------------------- > > Key: JBIDE-22227 > URL: https://issues.jboss.org/browse/JBIDE-22227 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. > This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. > Workflow: > 1) Create a dynamic web project with simple servlet > 2) Start a wildfly 10 in debug mode and deploy the web project > 3) Run-on-server the servlet object and verify it shows expected output > 4) Set a breakpoint inside the doGet() method > 5) refresh browser (breakpoint gets hit), press play > 6) Make a non-breaking change (change text inside doGet()) > 7) refresh website, verify breakpoint is hit, website content is updated > 8) make a breaking change by adding a new method > 9) hotcode-replace dialog appears. Press 'restart module' > 10) refresh web browser, verify breakpoint is hit, output has changed as expected > 11) make a non-breaking change in output of doGet() > 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS -- 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: ---------------------------------- Story Points: 3 > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016