[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22382:
--------------------------------------
Assignee: Fred Bricon
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: respin-a
> Fix For: 4.4.0.Final
>
> Attachments: central-rhd-icon.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ]
Josef Kopriva edited comment on ERT-204 at 6/6/16 12:05 PM:
------------------------------------------------------------
In devstudio 10.0.0.GA B5526 and devstudio 10.0.0.GA B5510 this was working without issues.
In Eclipse Neon RC3(build id: 20160602-0837) and docker tooling 2.0.0.201606022203 it didn't worked. The error message:
*There are no more files. Plugin org.eclipse.linuxtools.docker.core*
The error message is raised with command:
Failed to execute command 'C:\Program Files\Docker Toolbox\docker-machine.exe env default' (exit code=1): There are no more files.
The error message could be related with this:
https://wiki.eclipse.org/IRC_FAQ#Eclipse_is_constantly_crashing_for_me_on....
Workaround:
a) Run eclipse with debug flags in eclipse.ini:
-Xdebug
-Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000
b) Change value in eclipse.ini(not always works):
-Xms256m to -Xms512m
c) Run eclipse with eclipsec.exe
was (Author: jkopriva):
In devstudio 10.0.0.GA B5526 and devstudio 10.0.0.GA B5510 this was working without issues.
In Eclipse Neon RC3(build id: 20160602-0837) and docker tooling 2.0.0.201606022203 it didn't worked. The error message:
*There are no more files. Plugin org.eclipse.linuxtools.docker.core*
The error message is raised with command:
Failed to execute command 'C:\Program Files\Docker Toolbox\docker-machine.exe env default' (exit code=1): There are no more files.
The error message could be related with this:
https://wiki.eclipse.org/IRC_FAQ#Eclipse_is_constantly_crashing_for_me_on....
Workaround:
a) Run eclipse with debug flags in eclipse.ini:
-Xdebug
-Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000
b) Change value in eclipse.ini:
-Xms256m to -Xms512m
c) Run eclipse with eclipsec.exe
> Docker Machine lookup does not work on Windows machines [EBZ#494305]
> --------------------------------------------------------------------
>
> Key: ERT-204
> URL: https://issues.jboss.org/browse/ERT-204
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ]
Josef Kopriva commented on ERT-204:
-----------------------------------
In devstudio 10.0.0.GA B5526 and devstudio 10.0.0.GA B5510 this was working without issues.
In Eclipse Neon RC3(build id: 20160602-0837) and docker tooling 2.0.0.201606022203 it didn't worked. The error message:
*There are no more files. Plugin org.eclipse.linuxtools.docker.core*
The error message is raised with command:
Failed to execute command 'C:\Program Files\Docker Toolbox\docker-machine.exe env default' (exit code=1): There are no more files.
The error message could be related with this:
https://wiki.eclipse.org/IRC_FAQ#Eclipse_is_constantly_crashing_for_me_on....
Workaround:
a) Run eclipse with debug flags in eclipse.ini:
-Xdebug
-Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000
b) Change value in eclipse.ini:
-Xms256m to -Xms512m
c) Run eclipse with eclipsec.exe
> Docker Machine lookup does not work on Windows machines [EBZ#494305]
> --------------------------------------------------------------------
>
> Key: ERT-204
> URL: https://issues.jboss.org/browse/ERT-204
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22193) Can't deploy locally built docker images
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22193:
---------------------------------------
I am not sure if we cant consider this one as "done". It is true, one can deploy docker image from docker connection of CDK to OpenShift, but on the other hand, any docker connection outside of CDK won't work. This is not only related to CDK but also to remote OSE instances, where docker registries are self-signed - it won't work there either and I don't think it is ok, because if I would be a developer trying to deploy local existing docker image, I would not definitely build it on remote docker where I would have no access to the image except the access via deployed image to that same OpenShift instance. Please correct fix version to partially done and create follow up JIRA for outstanding issue of insecure registries.
> 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: Critical
> Fix For: 4.4.0.Final
>
>
> 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, 10 months
[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3924:
-----------------------------
Fix Version/s: 10.x
> Installation looks incomplete but is actually completed
> -------------------------------------------------------
>
> Key: JBDS-3924
> URL: https://issues.jboss.org/browse/JBDS-3924
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.GA
> Environment: Fedora 23
> Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Labels: install, installation, installer
> Fix For: 10.x
>
> Attachments: devstudio10install.png
>
>
> Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2044 at 6/6/16 11:29 AM:
-----------------------------------------------------------
Turns out this PR does nothing because devstudio includes a number of features which depend explicitly on org.eclipse.platform feature, not just the org.eclipse.platform plugin:
{code}
o.e.m2e.wtp.feature
o.e.m2e.jaxrs.feature
o.e.m2e.jpa.feature
o.e.m2e.jsf.feature
o.j.t.maven.cdi.feature
o.j.t.maven.feature
o.j.t.maven.hibernatefeature
o.j.t.maven.project.examples.feature
o.j.t.maven.sourcelookup.feature
o.sonatype.m2e.egit.feature
{code}
So, to prevent our .eclipseproduct file from being overwritten with Eclipse info, we need to have all the above projects stop depending on o.e.platform.feature.
Is this important enough to bother asking all those projects to fix their feature deps?
WDYT, [~dgolovin] [~fbricon] ?
Given this has been "broken" since 2012/02 and doesn't seem to have adversely impacted anyone, I'm inclined to close this as rejected or won'tfix.
was (Author: nickboldt):
Turns out this PR does nothing because devstudio includes a number of features which depend explicitly on org.eclipse.platform feature, not just the org.eclipse.platform plugin:
{code}
o.e.m2e.wtp.feature
o.e.m2e.jaxrs.feature
o.e.m2e.jpa.feature
o.e.m2e.jsf.feature
o.j.t.maven.cdi.feature
o.j.t.maven.feature
o.j.t.maven.hibernatefeature
o.j.t.maven.project.examples.feature
o.j.t.maven.sourcelookup.feature
o.sonatype.m2e.egit.feature
{code}
So, to prevent our .eclipseproduct file from being overwritten with Eclipse info, we need to have all the above projects stop depending on o.e.platform.feature.
Is this important enough to bother asking all those projects to fix their feature deps?
WDYT, [~dgolovin] [~fbricon] ?
> .eclipseproduct file no longer refers to JBDS
> ---------------------------------------------
>
> Key: JBDS-2044
> URL: https://issues.jboss.org/browse/JBDS-2044
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Labels: discuss
> Fix For: 10.1.0.Alpha1
>
>
> Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read:
> {code}
> name=JBoss Developer Studio
> id=com.jboss.jbds.all
> version=5.0.0.v201202271832M-H79-Beta1
> {code}
> Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads:
> {code}
> name=Eclipse Platform
> id=org.eclipse.platform
> version=3.7.0
> {code}
> Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2044 at 6/6/16 11:28 AM:
-----------------------------------------------------------
Turns out this PR does nothing because devstudio includes a number of features which depend explicitly on org.eclipse.platform feature, not just the org.eclipse.platform plugin:
{code}
o.e.m2e.wtp.feature
o.e.m2e.jaxrs.feature
o.e.m2e.jpa.feature
o.e.m2e.jsf.feature
o.j.t.maven.cdi.feature
o.j.t.maven.feature
o.j.t.maven.hibernatefeature
o.j.t.maven.project.examples.feature
o.j.t.maven.sourcelookup.feature
o.sonatype.m2e.egit.feature
{code}
So, to prevent our .eclipseproduct file from being overwritten with Eclipse info, we need to have all the above projects stop depending on o.e.platform.feature.
Is this important enough to bother asking all those projects to fix their feature deps?
WDYT, [~dgolovin] [~fbricon] ?
was (Author: nickboldt):
Turns out this PR does nothing because devstudio includes a number of features which depend explicitly on org.eclipse.platform feature, not just the org.eclipse.platform plugin:
{code}
o.e.m2e.wtp.feature
o.e.m2e.jaxrs.feature
o.e.m2e.jpa.feature
o.e.m2e.jsf.feature
o.j.t.maven.cdi.feature
o.j.t.maven.feature
o.j.t.maven.hibernatefeature
o.j.t.maven.project.examples.feature
o.j.t.maven.sourcelookup.feature
o.sonatype.m2e.egit.feature
{code}
> .eclipseproduct file no longer refers to JBDS
> ---------------------------------------------
>
> Key: JBDS-2044
> URL: https://issues.jboss.org/browse/JBDS-2044
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Labels: discuss
> Fix For: 10.1.0.Alpha1
>
>
> Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read:
> {code}
> name=JBoss Developer Studio
> id=com.jboss.jbds.all
> version=5.0.0.v201202271832M-H79-Beta1
> {code}
> Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads:
> {code}
> name=Eclipse Platform
> id=org.eclipse.platform
> version=3.7.0
> {code}
> Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22418) Update AERI Eclipse IDE Client to 2.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22418?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22418:
------------------------------------
OK, I'll just pull the latest from Neon.0.RC4 when it's available on Jun 9. TP .target locks down the version to include, but our devstudio .product file just includes whatever is available in the TP, so it'll just use 2.0.0 if that's what's there.
> Update AERI Eclipse IDE Client to 2.0
> -------------------------------------
>
> Key: JBIDE-22418
> URL: https://issues.jboss.org/browse/JBIDE-22418
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: aeri, target-platform
> Affects Versions: 4.4.0.Final
> Reporter: Marcel Bruch
> Assignee: Nick Boldt
> Fix For: 4.4.0.Final
>
>
> I'm about to release 2.0.0 for Neon.0.
> [~nickboldt], what is the earliest release of JBIDE / Devstudio that will pick up 2.0.0?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months