[JBoss JIRA] (JBIDE-22010) For JBIDE 4.3.1.CR1: Prepare for Final/GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22010?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22010 at 3/31/16 9:50 AM:
-------------------------------------------------------------
Status so far:
{code}
cd ~/tru/jbosstools-build-ci/util; ./getProjectRootPomParents.sh -w1 ~/tru -w2 ~/truu -b jbosstools-4.3.x -pv 4.3.1.Final-SNAPSHOT
Found these root pom versions [CORRECT]:
aerogear :: <version>4.3.1.Final-SNAPSHOT</version>
arquillian :: <version>4.3.1.Final-SNAPSHOT</version>
base :: <version>4.3.1.Final-SNAPSHOT</version>
browsersim :: <version>4.3.1.Final-SNAPSHOT</version>
discovery :: <version>4.3.1.Final-SNAPSHOT</version>
freemarker :: <version>4.3.1.Final-SNAPSHOT</version>
javaee :: <version>4.3.1.Final-SNAPSHOT</version>
jst :: <version>4.3.1.Final-SNAPSHOT</version>
playground :: <version>4.3.1.Final-SNAPSHOT</version>
vpe :: <version>4.3.1.Final-SNAPSHOT</version>
webservices :: <version>4.3.1.Final-SNAPSHOT</version>
build-sites :: <version>4.3.1.Final-SNAPSHOT</version>
product :: <version>4.3.1.Final-SNAPSHOT</version>
Found these root pom versions [INCORRECT]:
central :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
forge :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
hibernate :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
openshift :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
{code}
So we're close to being ready for spin today. Only 6 projects left to go.
was (Author: nickboldt):
Status so far (from running 'cd ~/tru/buildci/util; ./getProjectRootPomParents.sh -w1 ~/tru -w2 ~/truu -b jbosstools-4.3.x -pv 4.3.1.Final-SNAPSHOT`):
Found these root pom versions [CORRECT]:
aerogear :: <version>4.3.1.Final-SNAPSHOT</version>
arquillian :: <version>4.3.1.Final-SNAPSHOT</version>
base :: <version>4.3.1.Final-SNAPSHOT</version>
browsersim :: <version>4.3.1.Final-SNAPSHOT</version>
discovery :: <version>4.3.1.Final-SNAPSHOT</version>
freemarker :: <version>4.3.1.Final-SNAPSHOT</version>
javaee :: <version>4.3.1.Final-SNAPSHOT</version>
jst :: <version>4.3.1.Final-SNAPSHOT</version>
playground :: <version>4.3.1.Final-SNAPSHOT</version>
vpe :: <version>4.3.1.Final-SNAPSHOT</version>
webservices :: <version>4.3.1.Final-SNAPSHOT</version>
build-sites :: <version>4.3.1.Final-SNAPSHOT</version>
product :: <version>4.3.1.Final-SNAPSHOT</version>
Found these root pom versions [INCORRECT]:
central :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
forge :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
hibernate :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
openshift :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
So we're close to being ready for spin today. Only 6 projects left to go.
> For JBIDE 4.3.1.CR1: Prepare for Final/GA
> -----------------------------------------
>
> Key: JBIDE-22010
> URL: https://issues.jboss.org/browse/JBIDE-22010
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.CR1
>
>
> For JBIDE 4.3.1.CR1: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
> [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
> {code}
> git checkout jbosstools-4.3.x
> {code}
> 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3740
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22010) For JBIDE 4.3.1.CR1: Prepare for Final/GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22010?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22010:
------------------------------------
Status so far (from running 'cd ~/tru/buildci/util; ./getProjectRootPomParents.sh -w1 ~/tru -w2 ~/truu -b jbosstools-4.3.x -pv 4.3.1.Final-SNAPSHOT`):
Found these root pom versions [CORRECT]:
aerogear :: <version>4.3.1.Final-SNAPSHOT</version>
arquillian :: <version>4.3.1.Final-SNAPSHOT</version>
base :: <version>4.3.1.Final-SNAPSHOT</version>
browsersim :: <version>4.3.1.Final-SNAPSHOT</version>
discovery :: <version>4.3.1.Final-SNAPSHOT</version>
freemarker :: <version>4.3.1.Final-SNAPSHOT</version>
javaee :: <version>4.3.1.Final-SNAPSHOT</version>
jst :: <version>4.3.1.Final-SNAPSHOT</version>
playground :: <version>4.3.1.Final-SNAPSHOT</version>
vpe :: <version>4.3.1.Final-SNAPSHOT</version>
webservices :: <version>4.3.1.Final-SNAPSHOT</version>
build-sites :: <version>4.3.1.Final-SNAPSHOT</version>
product :: <version>4.3.1.Final-SNAPSHOT</version>
Found these root pom versions [INCORRECT]:
central :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
forge :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
hibernate :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
openshift :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.1.CR1-SNAPSHOT</version> </parent>
So we're close to being ready for spin today. Only 6 projects left to go.
> For JBIDE 4.3.1.CR1: Prepare for Final/GA
> -----------------------------------------
>
> Key: JBIDE-22010
> URL: https://issues.jboss.org/browse/JBIDE-22010
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.CR1
>
>
> For JBIDE 4.3.1.CR1: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
> [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
> {code}
> git checkout jbosstools-4.3.x
> {code}
> 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3740
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21997) Aeri causes NPE when running unittests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21997?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21997:
------------------------------------
Max says: "the link to PR was not given yesterday (or i didn't have it at least). as long as we are 100% sure it will install that latest Aeri and not change jetty then that is good." So I'll take that as a +1 to apply the PR.
With Marcel and Paul's feedback, that sounds like a +3.
> Aeri causes NPE when running unittests
> --------------------------------------
>
> Key: JBIDE-21997
> URL: https://issues.jboss.org/browse/JBIDE-21997
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aeri, target-platform
> Affects Versions: 4.3.1.CR1
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> an Eclipse bug was fixed 4 weeks ago in AERi and we need this fix to launch Integration tests for JBoss Fuse Tooling.
> We need the version containing the fix of https://bugs.eclipse.org/bugs/show_bug.cgi?id=488868
> Seems that we need to use the org.eclipse.epp.logging.aeri.core_1.100.0.v20160304-1116.jar although we are using org.eclipse.epp.logging.aeri.core_1.100.0.v20160211-1103
> Please take care because the version number are both 1.100.0
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21995) Hostname is set to localhost when prompt for route is checked
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21995?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21995:
-----------------------------------------------
[~rob.stryker], it is a feature that route may remain _not_ chosen when server adapter is created so that user may select route in a dialog (always or until he selects 'remember' option).
[~xcoulon], if route is removed or changed, when Show In Browser is called, it will check if there is a route available. If it is one then it will be opened, if more then user will have dialog to choose a route and selection will be remembered, if none then user will be informed of it. I see one minor issue - the removed/changed route will remain written in server adapter editor, we can validate it on open and show a warning.
> Hostname is set to localhost when prompt for route is checked
> -------------------------------------------------------------
>
> Key: JBIDE-21995
> URL: https://issues.jboss.org/browse/JBIDE-21995
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik edited comment on JBIDE-22004 at 3/31/16 9:43 AM:
--------------------------------------------------------------------
See also https://github.com/projectatomic/adb-atomic-developer-bundle/issues/310
Personally I am not sure whether adding the .cdk file to the CDK distro makes sense, since hopefully one will be able to bootstrap a CDK _Vagrantfile_ by a simple {{vagrant init}}.
What is this file good for really? Can we find other ways to achieve the same goal?
Right now we have this:
{code}
openshift.auth.scheme=Basic
openshift.auth.username=openshift-dev
openshift.auth.password=devel
cdk.version=2.0
{code}
It looks like it mixes several concerns. There seems to be some OpenShift information and I believe what the server-adapter is really after, _cdk.version_. What's really needed here and why?
[~rob.stryker] !?
was (Author: hardy.ferentschik):
See also https://github.com/projectatomic/adb-atomic-developer-bundle/issues/310
Personally I am not sure whether adding the .cdk file to the CDK distro makes sense, since hopefully one will be able to bootstrap a CDK _Vagrantfile_ by a simple {{vagrant init}}.
What is this file good for really? Can we find other ways to achieve the same goal?
Right now we have this:
{code}
openshift.auth.scheme=Basic
openshift.auth.username=openshift-dev
openshift.auth.password=devel
cdk.version=2.0
{code}
It looks like it mixes several concerns. There seems to be some OpenShift information and I believe what the server-adapter is really after, _cdk.version_. What's really needed here and why?
[~rob.stryker] !?
{code}
> Runtime detection unable to detect CDK
> --------------------------------------
>
> Key: JBIDE-22004
> URL: https://issues.jboss.org/browse/JBIDE-22004
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Radim Hopp
> Assignee: Hardy Ferentschik
> Fix For: 4.4.x
>
>
> Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it.
> Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21997) Aeri causes NPE when running unittests
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21997?page=com.atlassian.jira.plugi... ]
Paul Leacu commented on JBIDE-21997:
------------------------------------
+1 Using Nick's pull seems to have resolved the original Fuse Tooling issue.
> Aeri causes NPE when running unittests
> --------------------------------------
>
> Key: JBIDE-21997
> URL: https://issues.jboss.org/browse/JBIDE-21997
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aeri, target-platform
> Affects Versions: 4.3.1.CR1
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> an Eclipse bug was fixed 4 weeks ago in AERi and we need this fix to launch Integration tests for JBoss Fuse Tooling.
> We need the version containing the fix of https://bugs.eclipse.org/bugs/show_bug.cgi?id=488868
> Seems that we need to use the org.eclipse.epp.logging.aeri.core_1.100.0.v20160304-1116.jar although we are using org.eclipse.epp.logging.aeri.core_1.100.0.v20160211-1103
> Please take care because the version number are both 1.100.0
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21999) Server adapter: stream closed exception when debugging
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21999?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21999:
----------------------------------
Sprint: devex #4 March 2016 (was: devex #4 March 2016, devex #5 April 2016)
> Server adapter: stream closed exception when debugging
> -------------------------------------------------------
>
> Key: JBIDE-21999
> URL: https://issues.jboss.org/browse/JBIDE-21999
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> [ERROR] 2016-03-25 12:19:53,006 com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync - Could not retrieve error message from process
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:336)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.Reader.read(Reader.java:140)
> at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1485)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1461)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1408)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1433)
> at org.apache.commons.io.IOUtils.toString(IOUtils.java:585)
> at org.apache.commons.io.IOUtils.toString(IOUtils.java:563)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.getErrorMessage(OpenShiftBinaryRSync.java:107)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.await(OpenShiftBinaryRSync.java:94)
> {code}
> This error happened at the same time as the deployment failed, as reported in JBIDE-21981, but since there are 2 distinct problems, we should track them in 2 separate issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21999) Server adapter: stream closed exception when debugging
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21999?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21999.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B258.
> Server adapter: stream closed exception when debugging
> -------------------------------------------------------
>
> Key: JBIDE-21999
> URL: https://issues.jboss.org/browse/JBIDE-21999
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> [ERROR] 2016-03-25 12:19:53,006 com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync - Could not retrieve error message from process
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:336)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.Reader.read(Reader.java:140)
> at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1485)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1461)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1408)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1433)
> at org.apache.commons.io.IOUtils.toString(IOUtils.java:585)
> at org.apache.commons.io.IOUtils.toString(IOUtils.java:563)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.getErrorMessage(OpenShiftBinaryRSync.java:107)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.await(OpenShiftBinaryRSync.java:94)
> {code}
> This error happened at the same time as the deployment failed, as reported in JBIDE-21981, but since there are 2 distinct problems, we should track them in 2 separate issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months