[JBoss JIRA] (JBDS-3677) Add Red Hat OpenJDK 8 on Windows to support matrix for JBDS
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3677?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3677:
--------------------------------
> Add Red Hat OpenJDK 8 on Windows to support matrix for JBDS
> -----------------------------------------------------------
>
> Key: JBDS-3677
> URL: https://issues.jboss.org/browse/JBDS-3677
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Misha Ali
> Fix For: 9.1.0.GA
>
>
> Since a major use case for JBDS will be that users will install it using the big installer including Azul JDK on Windows, we need to make sure this combination is actually tested and supported.
> I guess nobody realized this before, but it seems pretty obvious that this is necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22193) Can't deploy locally built docker images
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22193:
---------------------------------------
[~fbricon], ok, so I gave this a try and if anything it's a bug in docker itself (not sure which part, but the bottom line is that docker cli client does the same thing).
I built my custom Dockerfile and in Docker Images view, you can see the Virtual Size being non-zero. Then I looked in Docker Explorer and clicked the image. And indeed, the Properties view shows its size as 0. But the same applies for another image that I have: docker.io/jboss/wildfly: 8.2.0.Final.
Then I fired up cli and it shows the same (using "docker images --digests").
And finally I looked at my Docker Machine connection in JBDS and selected centos: latest image in Docker Explorer and voila, Size 0 in Properties view. All of my images in Docker Machine show Size 0. Interestingly, the images from registry.access.redhat.com in CDK show non-0 size.
> 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
[JBoss JIRA] (JBIDE-22213) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Forge]
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22213?page=com.atlassian.jira.plugi... ]
George Gastaldi closed JBIDE-22213.
-----------------------------------
Resolution: Done
The major listed commits are version bumps. The remaining others are present in master already.
> For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Forge]
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-22213
> URL: https://issues.jboss.org/browse/JBIDE-22213
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Rob Stryker
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Forge]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master.
> Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in master
> 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-forge at https://github.com/jbosstools/jbosstools-forge/
> Searching for commits present in jbosstools-4.3.x and missing from master
> Commit hash "0b5f88" is the last common ancestor of jbosstools-4.3.x and master
> 0b5f88 is 23 commits ago in branch master
> 0b5f88 is 24 commits ago in branch jbosstools-4.3.x
> Commits missing from master that are in jbosstools-4.3.x:
> - https://github.com/jbosstools/jbosstools-forge//commit/ee1e4d2b7ddc8545cb...
> - https://github.com/jbosstools/jbosstools-forge//commit/e699c29351401a15a1...
> - https://github.com/jbosstools/jbosstools-forge//commit/89e1a098136c5c6f24...
> - https://github.com/jbosstools/jbosstools-forge//commit/6ef52ee18de7740fe5...
> - https://github.com/jbosstools/jbosstools-forge//commit/11f1a8cd60495c3dee...
> - https://github.com/jbosstools/jbosstools-forge//commit/1f03e7f5edff62053b...
> - https://github.com/jbosstools/jbosstools-forge//commit/29c215d98fe0450bbe...
> - https://github.com/jbosstools/jbosstools-forge//commit/6652db2d6d1e398764...
> - https://github.com/jbosstools/jbosstools-forge//commit/bbae2fdf4b9d051753...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Forge task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[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:
-----------------------------------------
I did have Java 8 on fedora, still don't understand why Installer did not work there.
> 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
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Lars Heinemann commented on JBTIS-654:
--------------------------------------
The tooling requires you to have Java 8. Thats the reason you don't see the tooling. The bundles simply don't start because of the wrong java version.
> 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
[JBoss JIRA] (JBTIS-675) can't install JBoss SOA 5.x Development connector from JBDS 9.1.0.GA central
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-675?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-675:
----------------------------------
Yes - it's fixed in 9.1.0.GA (JBDS infrastructure)
> 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.1.0.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
[JBoss JIRA] (JBTIS-675) can't install JBoss SOA 5.x Development connector from JBDS 9.1.0.GA central
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-675?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-675:
-----------------------------
Fix Version/s: 9.1.0.GA
(was: 9.0.1.GA)
> 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.1.0.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