[JBoss JIRA] (JBIDE-12618) CLONE - Remove need for jax-rs-api.jar
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12618?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-12618:
------------------------------------
Release Notes Text: Previously, the JBoss JAX-RS Tools plug-in contained the JAX-RS API (jaxrs-api.jar). The API was solely needed to retrieve class names so it has been removed from the JBoss JAX-RS Tools plug-in and class names explicitly included as necessary. This has reduced the overall size of the JBoss JAX-RS Tools plug-in. (was: The JBoss JAX-RS plugin does not bundle the jaxrs-api.jar anymore. This jar was just used to retrieve some class names.
Previously, the JBoss JAX-RS Tools plug-in contained the JAX-RS API (jaxrs-api.jar). The Eclipse Orbit repository now contains a plug-in for the JAX-RS API and so it has been removed from JBoss JAX-RS Tools plug-in.)
> CLONE - Remove need for jax-rs-api.jar
> --------------------------------------
>
> Key: JBIDE-12618
> URL: https://issues.jboss.org/browse/JBIDE-12618
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Webservices
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 3.3.2
>
> Attachments: JBIDE-10115.patch, JBIDE-10115b.patch
>
>
> The Eclipse Orbit repository (http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/r...) contains the JAX-RS API bundled as a plugin, so we could probably remove the jars I've put in the org.jboss.tools.ws.jaxrs projects' /lib folder and just add a dependency on that plugin, which would reduce the SVN size.
> On the other side, it would add an external dependency that devs should grab to avoid compilation errors, and it may have an impact on the build chain (have to confirm that with Nick Boldt)
> WDYT ?
--
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, 2 months
[JBoss JIRA] (JBIDE-12618) CLONE - Remove need for jax-rs-api.jar
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12618?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-12618:
------------------------------------
Release Notes Text:
The JBoss JAX-RS plugin does not bundle the jaxrs-api.jar anymore. This jar was just used to retrieve some class names.
Previously, the JBoss JAX-RS Tools plug-in contained the JAX-RS API (jaxrs-api.jar). The Eclipse Orbit repository now contains a plug-in for the JAX-RS API and so it has been removed from JBoss JAX-RS Tools plug-in.
was:The JAX-RS plugin does not bundle the jaxrs-api.jar anymore. This jar was just used to retrieve some class names.
> CLONE - Remove need for jax-rs-api.jar
> --------------------------------------
>
> Key: JBIDE-12618
> URL: https://issues.jboss.org/browse/JBIDE-12618
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Webservices
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 3.3.2
>
> Attachments: JBIDE-10115.patch, JBIDE-10115b.patch
>
>
> The Eclipse Orbit repository (http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/r...) contains the JAX-RS API bundled as a plugin, so we could probably remove the jars I've put in the org.jboss.tools.ws.jaxrs projects' /lib folder and just add a dependency on that plugin, which would reduce the SVN size.
> On the other side, it would add an external dependency that devs should grab to avoid compilation errors, and it may have an impact on the build chain (have to confirm that with Nick Boldt)
> WDYT ?
--
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, 2 months
[JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi... ]
Michelle Murray closed JBIDE-11215.
-----------------------------------
Resolution: Done
> JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
> --------------------------------------------------------------
>
> Key: JBIDE-11215
> URL: https://issues.jboss.org/browse/JBIDE-11215
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.M5
> Environment: Windows XP, Eclipse 3.7.sr2
> Reporter: Jesper Skov
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 3.3.2, 4.0.0.Beta2
>
> Attachments: eclipseproblem.zip
>
>
> JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many successful deployments).
> Similar behavior from the nightly build 2012.02.27.
> M4 is working without problems, and this is the version we revert to when restarts of Eclipse with M5 gets too tedious.
> The Eclipse log shows JMX console login problems as the (propable) cause, see below.
> We use admin/admin credentials for the JMX console, and don't change these during the day.
> Hard to reproduce, but (obviously) we are willing and happy to test any build you might feel should fix this. We don't want to get stranded at M4 :)
> (I will attach a snapshot of the server configuration page when I get a chance.)
> Let me know if there is any logging we can tweak to help you find and fix the cause of this.
> Log output from the 2012.02.27 nightly build:
> {code}
> java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
> at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
> at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
> at sun.rmi.transport.Transport$1.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Unknown Source)
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
> at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
> at sun.rmi.server.UnicastRef.invoke(Unknown Source)
> at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
> at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
> at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
> at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
> at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
> at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
> at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
> at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
> at $Proxy30.invoke(Unknown Source)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
> at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
> at org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
> at org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
> {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, 2 months
[JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11215?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-11215:
------------------------------------
Release Notes Text: (was: JBPAPP-9973 is fixed and I verified it with JBT 4.0.0.Beta2 and EAP 5.2.0.ER4.
I opened a related issue JBIDE-13013. But it may not really be a bug.)
Removing text from 'Release Notes Text' as this bug appears to be an EAP issue not JBT/JBDS so I don't believe it needs a release note. Perhaps the related issue JBIDE-13013 needs a release note instead.
> JbossTools 3.3.0M5 (EAP5.1.1) fail deployment after some time
> --------------------------------------------------------------
>
> Key: JBIDE-11215
> URL: https://issues.jboss.org/browse/JBIDE-11215
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.M5
> Environment: Windows XP, Eclipse 3.7.sr2
> Reporter: Jesper Skov
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 3.3.2, 4.0.0.Beta2
>
> Attachments: eclipseproblem.zip
>
>
> JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many successful deployments).
> Similar behavior from the nightly build 2012.02.27.
> M4 is working without problems, and this is the version we revert to when restarts of Eclipse with M5 gets too tedious.
> The Eclipse log shows JMX console login problems as the (propable) cause, see below.
> We use admin/admin credentials for the JMX console, and don't change these during the day.
> Hard to reproduce, but (obviously) we are willing and happy to test any build you might feel should fix this. We don't want to get stranded at M4 :)
> (I will attach a snapshot of the server configuration page when I get a chance.)
> Let me know if there is any logging we can tweak to help you find and fix the cause of this.
> Log output from the 2012.02.27 nightly build:
> {code}
> java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
> at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855)
> at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
> at sun.rmi.transport.Transport$1.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Unknown Source)
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
> at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
> at sun.rmi.server.UnicastRef.invoke(Unknown Source)
> at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
> at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
> at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
> at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
> at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
> at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68)
> at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
> at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
> at $Proxy30.invoke(Unknown Source)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69)
> at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194)
> at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102)
> at org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232)
> at org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149)
> {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, 2 months
[JBoss JIRA] (JBIDE-11217) Forge: present verbose mode functionality in Forge JBT/JBDS Tooling
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11217?page=com.atlassian.jira.plugi... ]
Michelle Murray resolved JBIDE-11217.
-------------------------------------
Resolution: Done
> Forge: present verbose mode functionality in Forge JBT/JBDS Tooling
> -------------------------------------------------------------------
>
> Key: JBIDE-11217
> URL: https://issues.jboss.org/browse/JBIDE-11217
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 3.3.2, 4.0.0.Alpha1
>
> Attachments: JBIDE-11217-3.3.x.patch, JBIDE-11217.patch
>
>
> You can run the command: 'set VERBOSE true' in forge running from standard command line. This is not possible/working in JBDS/JBT Forge console. It would be very helpful to have some preference option where you can turn ON/OFF the verbose mode and probably log all the exceptions to the Eclipse Error log. What do you think?
--
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, 2 months
[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-13319:
-----------------------------------------
[~maxandersen] The release notes text currently says 'For this release of the associated tooling, MongoDB 2.2 is now fully supported.' but this is contrary to the 'Won't fix' closure of the JIRA. Please can you clarify?
If going with 'Won't fix', then I would suggest putting this in the release notes as a known issue, with text directing users to JBT 4/JBDS 6 as your comment suggests. Would that be ok?
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: embed-by-name.patch, mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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, 2 months
[JBoss JIRA] (JBIDE-11217) Forge: present verbose mode functionality in Forge JBT/JBDS Tooling
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11217?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-11217:
-----------------------------------------
[~koen.aers] I'm getting release notes ready for JBDS 5.0.2. Please can you tell me what the 'set VERBOSE true' command does? Thanks.
> Forge: present verbose mode functionality in Forge JBT/JBDS Tooling
> -------------------------------------------------------------------
>
> Key: JBIDE-11217
> URL: https://issues.jboss.org/browse/JBIDE-11217
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 3.3.2, 4.0.0.Alpha1
>
> Attachments: JBIDE-11217-3.3.x.patch, JBIDE-11217.patch
>
>
> You can run the command: 'set VERBOSE true' in forge running from standard command line. This is not possible/working in JBDS/JBT Forge console. It would be very helpful to have some preference option where you can turn ON/OFF the verbose mode and probably log all the exceptions to the Eclipse Error log. What do you think?
--
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, 2 months