[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2505:
-------------------------------------
Ok, thanks for the explanation, Nick. To me our approach makes more sense - to me the referenced plugin in a feature is part of the contents. So I'm glad we have this approach :)
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-b
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13631:
-------------------------------------------------
Dan McPherson <dmcphers(a)redhat.com> changed the Status of [bug 923442|https://bugzilla.redhat.com/show_bug.cgi?id=923442] from VERIFIED to CLOSED
> URL for embedded cartridges is empty
> ------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13816) Maven repository is not visible if its not active by default
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13816?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-13816:
-------------------------------------
Snjeza, your PR makes the inactive repos visible as requested but there's no way to tell they're not active from the repo viewer.
Until JBIDE-13831 is fixed, it's important to give users a visual hint of the repo status, IMHO.
I suggest adding a (Disabled) or (Inactive) prefix to the, well, disabled repos. And if they could use an italic font, that'd be even better.
> Maven repository is not visible if its not active by default
> ------------------------------------------------------------
>
> Key: JBIDE-13816
> URL: https://issues.jboss.org/browse/JBIDE-13816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13816) Maven repository is not visible if its not active by default
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13816?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-13816:
--------------------------------
Description: (was: Snjeza, your PR makes the inactive repos visible as requested but there's no way to tell they're not active from the repo viewer.
Until JBIDE-13831 is fixed, it's important to give users a visual hint of the repo status, IMHO.
I suggest adding a (Disabled) or (Inactive) prefix to the, well, disabled repos. And if they could use an italic font, that'd be even better.)
> Maven repository is not visible if its not active by default
> ------------------------------------------------------------
>
> Key: JBIDE-13816
> URL: https://issues.jboss.org/browse/JBIDE-13816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13816) Maven repository is not visible if its not active by default
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13816?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-13816:
--------------------------------
Description:
Snjeza, your PR makes the inactive repos visible as requested but there's no way to tell they're not active from the repo viewer.
Until JBIDE-13831 is fixed, it's important to give users a visual hint of the repo status, IMHO.
I suggest adding a (Disabled) or (Inactive) prefix to the, well, disabled repos. And if they could use an italic font, that'd be even better.
> Maven repository is not visible if its not active by default
> ------------------------------------------------------------
>
> Key: JBIDE-13816
> URL: https://issues.jboss.org/browse/JBIDE-13816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
>
> Snjeza, your PR makes the inactive repos visible as requested but there's no way to tell they're not active from the repo viewer.
> Until JBIDE-13831 is fixed, it's important to give users a visual hint of the repo status, IMHO.
> I suggest adding a (Disabled) or (Inactive) prefix to the, well, disabled repos. And if they could use an italic font, that'd be even better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBDS-2505) JBDS 6.0.1 is based on Juno SR0 instead of SR2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2505?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2505:
----------------------------------
Eclipse rules state that just because a plugin is x.y.z+1, does not mean that its containing feature must also be x.y.z+1. The feature, if nothing in its ACTUAL CONTENT (eg., feature.xml, LICENSE.html, etc.) has changed, can remain at x.y.z. No commits == no upversioning, even if a contained plugin has a commit for maintenance and its version increments.
http://wiki.eclipse.org/Version_Numbering#Versioning_features
Of course in JBT/JBDS, we upversion both feature AND plugin at the same time, as we follow a different convention.
> JBDS 6.0.1 is based on Juno SR0 instead of SR2
> ----------------------------------------------
>
> Key: JBDS-2505
> URL: https://issues.jboss.org/browse/JBDS-2505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.1.GA
> Environment: JBDS 6.0.1.CR1a B354
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-b
> Fix For: 6.0.1.GA
>
>
> JBDS 6.0.1.CR1a B354 is based on Eclipse Juno SR0, but should be Juno SR2.
> I know about the recent issue where TP wasn't updated to 4.22.2, so I would expect something 4.22.1 (still Juno SR2). But in fact it is SR0.
> My assumption is that while JBDS BYOE can be installed on the minimal version of Eclipse, the JBDS installer should contain the maximum TP. I hope I'm not wrong here.
> Now I also checked the previous build - JBDS 6.0.1.CR1 B338 and that is based on Eclipse Juno 4.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13818) openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13818?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13818:
-------------------------------------------------
Dan McPherson <dmcphers(a)redhat.com> changed the Status of [bug 923369|https://bugzilla.redhat.com/show_bug.cgi?id=923369] from VERIFIED to CLOSED
> openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
> -------------------------------------------------------------------------
>
> Key: JBIDE-13818
> URL: https://issues.jboss.org/browse/JBIDE-13818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> This is a watcher issue that helps us tracking the progress of https://bugzilla.redhat.com/show_bug.cgi?id=923369
> In the openshift-java-client integration tests, restarting a stopped application is failing since a few hours (very latest OpenShift origin code):
> https://ci.dev.openshift.redhat.com/jenkins/job/openshift-java-client-dev...
> {code}
> Fehlermeldung
> Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: " Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> Stacktrace
> com.openshift.client.OpenShiftEndpointException: Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: "
> Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> at com.openshift.internal.client.RestService.request(RestService.java:106)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:124)
> at com.openshift.internal.client.ApplicationResource$StopApplicationRequest.execute(ApplicationResource.java:739)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:245)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:238)
> at com.openshift.internal.client.ApplicationResourceIntegrationTest.shouldRestartStoppedApplication(ApplicationResourceIntegrationTest.java:237)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:74)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:194)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:135)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":-1,"field":null,"severity":"error","text":"\nReference ID: 877bbfd174ddd2b8fec93e4fb560b17a"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.0"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:193)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:135)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:131)
> at com.openshift.internal.client.RestService.request(RestService.java:144)
> at com.openshift.internal.client.RestService.request(RestService.java:98)
> ... 69 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:163)
> ... 73 more
> Standard Ausgabe (STDOUT)
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/api
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/user
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting POST on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13897) Remote EAP 6.1 cannot stop (maintenance)
by Martin Malina (JIRA)
Martin Malina created JBIDE-13897:
-------------------------------------
Summary: Remote EAP 6.1 cannot stop (maintenance)
Key: JBIDE-13897
URL: https://issues.jboss.org/browse/JBIDE-13897
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.1.0.Alpha1
Environment: JBDS 7.0.0.Alpha1a B10
EAP 6.1.0.DR4.1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.1.0.Alpha2
After JBIDE-13585 added support for EAP 6.1 I tried to use it as a remote server. Server start and deploy worked fine, but when I tried to stop the server it won't do it.
{code}
!ENTRY org.eclipse.wst.server.core 4 0 2013-02-20 11:06:05.662
!MESSAGE Server JBoss EAP 6.1 Runtime Server marvin failed to stop.
{code}
!remote-server-stop.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13897) Remote EAP 6.1 cannot stop (maintenance)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13897?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-13897:
----------------------------------
Affects Version/s: 4.0.1.Final
(was: 4.1.0.Alpha1)
> Remote EAP 6.1 cannot stop (maintenance)
> ----------------------------------------
>
> Key: JBIDE-13897
> URL: https://issues.jboss.org/browse/JBIDE-13897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.1.Final
> Environment: JBDS 7.0.0.Alpha1a B10
> EAP 6.1.0.DR4.1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha2
>
>
> After JBIDE-13585 added support for EAP 6.1 I tried to use it as a remote server. Server start and deploy worked fine, but when I tried to stop the server it won't do it.
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2013-02-20 11:06:05.662
> !MESSAGE Server JBoss EAP 6.1 Runtime Server marvin failed to stop.
> {code}
> !remote-server-stop.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13897) Remote EAP 6.1 cannot stop (maintenance)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13897?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-13897:
----------------------------------
Fix Version/s: 4.0.2.Final
(was: 4.1.0.Alpha2)
> Remote EAP 6.1 cannot stop (maintenance)
> ----------------------------------------
>
> Key: JBIDE-13897
> URL: https://issues.jboss.org/browse/JBIDE-13897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.1.Final
> Environment: JBDS 7.0.0.Alpha1a B10
> EAP 6.1.0.DR4.1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.0.2.Final
>
>
> After JBIDE-13585 added support for EAP 6.1 I tried to use it as a remote server. Server start and deploy worked fine, but when I tried to stop the server it won't do it.
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2013-02-20 11:06:05.662
> !MESSAGE Server JBoss EAP 6.1 Runtime Server marvin failed to stop.
> {code}
> !remote-server-stop.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years