April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3847) Need new screenshot for JBDS 9.1 update site page

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3847: -------------------------------- Summary: Need new screenshot for JBDS 9.1 update site page Key: JBDS-3847 URL: https://issues.jboss.org/browse/JBDS-3847 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: documentation, updatesite Affects Versions: 9.1.0.GA Reporter: Nick Boldt https://devstudio.redhat.com/9.0/stable/updates/ contains two screenshots, both showing "JBoss Central". Since we're now calling that Red Hat Central, we need new screenshots for that page. -- 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 commented on JBIDE-22193: ------------------------------------- [~mmalina] indeed, I thought that would be enough to see the image in the docker explorer. But it's just a tag in the docker daemon. Pushing to the docker registry is another story (which requires logging in to that registry) Also I'm not sure why the docker image we see in the docker explorer as a size of 0B > 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: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Priority: Blocker > > 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] (JBTIS-654) JBDSIS stand-alone installer

by Aileen Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Aileen Cunningham commented on JBTIS-654: ----------------------------------------- Success! Got it installed on Windows with Java 8. I now see Fuse in New menu and the Fuse cheat sheets. It's a bit improvement on the 2 phase install - now we need the new wizard to guide users through next stage. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-675) can't install JBoss SOA 5.x Development connector from JBDS 9.1.0.GA central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-675?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-675: ----------------------------------------- Verified with JBDS 9.1.0.GA without specifying any additional vm args. All tools from JBDS-IS 9.0.0.Beta1 via RH central were successfully installed. [~pleacu] I'm a bit confused by the fix version '9.0.1.GA', maybe a typo? > can't install JBoss SOA 5.x Development connector from JBDS 9.1.0.GA central > ---------------------------------------------------------------------------- > > Key: JBTIS-675 > URL: https://issues.jboss.org/browse/JBTIS-675 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > > Tried to install everything in Central from JBDS 9.1.0.GA, after enabling Early Access. > {code} > !MESSAGE The following connectors are not available: JBoss SOA 5.x Development > (id=org.eclipse.bpel.apache.ode.runtime.feature.feature.group, > org.jboss.tools.esb.feature.feature.group, > org.jboss.tools.runtime.esb.detector.feature.feature.group, > org.jboss.tools.jbpm.common.feature.feature.group, > org.jboss.tools.jbpm.convert.feature.feature.group, > org.jboss.tools.jbpm3.feature.feature.group, > org.jbpm.gd.jpdl.feature.feature.group, > site=https://devstudio.redhat.com/9.0/stable/updates/) > {code} > Is it possible I have an old version of earlyaccess properties ? > https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.1... > I can see the features here: > https://devstudio.redhat.com/9.0/stable/updates/integration-stack/earlyac... > * org.jboss.tools.runtime.esb.detector.feature.feature.group 1.5.530.Final-v20150310-1957-B70 > * org.eclipse.bpel.apache.ode.runtime.feature.feature.group 1.0.5.Final (two copies) > * org.jboss.tools.runtime.esb.detector.feature.feature.group 1.5.530.Final-v20150310-1957-B70 > * ... > Or... why is Central looking at > {code}jboss.discovery.site.url|devstudio|9=https://devstudio.redhat.com/9.0/stable/updates/{code} > instead of > {code}jboss.discovery.earlyaccess.site.url|devstudio|9=https://devstudio.redhat.com/9.0/stable/updates/earlyaccess/{code} > [~fbricon] any idea? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-662) TP refers to a nonexisting update site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-662?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-662. ----------------------------------- Verified > TP refers to a nonexisting update site > -------------------------------------- > > Key: JBTIS-662 > URL: https://issues.jboss.org/browse/JBTIS-662 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.1.Final-TP > Environment: target-platform-4.3.1.Final-20160408.151437-7-base-ea.target > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 4.3.1.Final-TP > > > The TP refers to the following update site > http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.CR1a/ > which doesn't exist anymore -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22221) Typo in New OpenShift 3 Adapter section

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22221?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22221. --------------------------------- Verified. > Typo in New OpenShift 3 Adapter section > --------------------------------------- > > Key: JBIDE-22221 > URL: https://issues.jboss.org/browse/JBIDE-22221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.1.Final > Reporter: Marián Labuda > Assignee: Marián Labuda > Fix For: 4.3.1.Final > > > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html... contains following sentence > {code}From the OpenShift Explorer, right-click on a deployed Service a select the Server Adapter… menu: it will either create a new Server adapter or display one in the Servers view if it already exists.{code} > there should be and instead of a (a deployed Service *and* select the) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-672) JBTIS Stable EA site broken due to composite site listing p2.index file as if it's a child folder, and missing org.kie.eclipse features

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-672?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-672. ------------------------------ Resolution: Done Corrected JBTIS EA components. We are now picking up the JBTIS 4.3.0.Beta1 bits. Will keep an eye out if the p2.index gets sucked in as if it were a child folder again. > JBTIS Stable EA site broken due to composite site listing p2.index file as if it's a child folder, and missing org.kie.eclipse features > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-672 > URL: https://issues.jboss.org/browse/JBTIS-672 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Critical > Labels: early-access > Fix For: 4.3.0.Final > > Attachments: where-is-kie.png, where-is-kie_2.png > > > http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac... is broken, since it lists the p2.index file as if it's a child folder. > So, Eclipse complains: > {code} > eclipse.buildId=4.5.2.M20160212-1500 > java.version=1.8.0_60 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -data /home/nboldt/eclipse/workspace-clean45-2 -consolelog -product org.eclipse.epp.package.jee.product -data file:/home/nboldt/eclipse/workspace-clean45-2/ -consolelog > org.eclipse.equinox.p2.metadata.repository > Error > Mon Apr 18 18:59:56 EDT 2016 > No repository found at http://download.jboss.org/jbosstools/mars/stable/updates/integration-stac.... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-22225: --------------------------------- Component/s: javascript > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Reporter: Gorkem Ercan > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22221) Typo in New OpenShift 3 Adapter section

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22221?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22221: -------------------------------------- Fix Version/s: 4.3.1.Final Assignee: Marián Labuda Resolution: Done > Typo in New OpenShift 3 Adapter section > --------------------------------------- > > Key: JBIDE-22221 > URL: https://issues.jboss.org/browse/JBIDE-22221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.3.1.Final > Reporter: Marián Labuda > Assignee: Marián Labuda > Fix For: 4.3.1.Final > > > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html... contains following sentence > {code}From the OpenShift Explorer, right-click on a deployed Service a select the Server Adapter… menu: it will either create a new Server adapter or display one in the Servers view if it already exists.{code} > there should be and instead of a (a deployed Service *and* select the) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-22225: ------------------------------------ Summary: Debugging for node.js applications on Openshift Key: JBIDE-22225 URL: https://issues.jboss.org/browse/JBIDE-22225 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Gorkem Ercan We should be able to start and connect the new debugger to a node.js application running on Openshift. -- 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