[jira] Closed: (GSHELL-111) The cursor can not move to the provious line if the command is broken to multiple lines
[
https://issues.apache.org/jira/browse/GSHELL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-111.
---
Resolution: Invalid
> The cursor can not move to the provious line if the command is broken to
> multiple lines
> ---
>
> Key: GSHELL-111
> URL: https://issues.apache.org/jira/browse/GSHELL-111
> Project: GShell
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CLI
>Affects Versions: 1.0-alpha-2
> Environment: Windows
>Reporter: YunFeng Ma
>Assignee: Jason Dillon
> Fix For: 1.0-alpha-2
>
>
> If the input command is too long and broken into multiple lines, the cursor
> can not be moved to the previous line.
> For example:
> {noformat}
> [EMAIL PROTECTED]:/> deploy/install-plugon F:/Geronimo/2.1/samples/plugins/
> jsp-examples-tomcat/target/jsp-examples-tomcat-2.1.0.0.car
> {noformat}
> I notice that there is a typo error in "deploy/install-plugon", but I can
> not move the cursor to the first line to modify it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3994) GShell command remote-control/server-control can not control the remote server
[
https://issues.apache.org/jira/browse/GERONIMO-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GERONIMO-3994.
--
Resolution: Fixed
Fix Version/s: (was: 2.1.2)
(was: 2.1.x)
(was: 2.1.1)
2.2
The {{remote-control}} command has been dropped.
> GShell command remote-control/server-control can not control the remote server
> --
>
> Key: GERONIMO-3994
> URL: https://issues.apache.org/jira/browse/GERONIMO-3994
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands
>Affects Versions: 2.1.1, 2.1.2, 2.1.x
> Environment: Windows
>Reporter: YunFeng Ma
>Assignee: Jason Dillon
> Fix For: 2.2
>
>
> First run remote/rsh to login the remote rsh-server, then run the following
> gsh commands:
> {noformat}
> remote-control/server-control start defaultServer
> {noformat}
> No any response.
> Here is the gshell log in the remote server.
> {noformat}
> 19:36:47,234 DEBUG (SocketAcceptorIoProcessor-0.0)
> [org.apache.mina.filter.executor.ExecutorFilter] Launching thread for
> /127.0.0.1:3699
> 19:36:47,234 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.remote.server.RshServer$Handler]
> [/127.0.0.1:3699] RECEIVED: ExecuteMessage{ flavor=STRING, path=,
> args=[ remote-control/server-control start defaultServer ], id=7, cid=,
> sequence=7, timestamp=1209436607234 }
> 19:36:47,234 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandExecutor] Executing (String):
> remote-control/server-control start defaultServer
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.parser.CommandLineParser] Parsing from reader:
> [EMAIL PROTECTED]
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] CommandLine
> (org.apache.geronimo.gshell.parser.ASTCommandLine)
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] Expression
> (org.apache.geronimo.gshell.parser.ASTExpression)
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] PlainString(
> remote-control/server-control )
> (org.apache.geronimo.gshell.parser.ASTPlainString)
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] PlainString( start )
> (org.apache.geronimo.gshell.parser.ASTPlainString)
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] PlainString(
> defaultServer ) (org.apache.geronimo.gshell.parser.ASTPlainString)
> 19:36:47,234 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandExecutor] Executing
> (remote-control/server-control): [start, defaultServer]
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.plugin.PlexusCommandWrapper] Child container
> realm: gshell:e47ff117-c940-4e2e-87a8-5b9257bc16e9
> 19:36:47,343 DEBUG (TcpTransportServer-0-0)
> [org.codehaus.plexus.PlexusContainer] Found 0 components to load on start
> 19:36:47,343 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.commands.RemoteServerControlCommand.geronimo-commands:remote-server-control]
> Executing w/args: [start, defaultServer]
> 19:36:47,390 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.remote.server.handler.ExecuteHandler] Fault:
> java.lang.IllegalStateException: File D:\geronimo
> server-1\bin\etc\server-configuration.xml does not exist
> 19:36:47,390 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.remote.server.RshServer$Handler]
> [/127.0.0.1:3699] WRITE: Fault{ result=java.lang.IllegalStateException: File
> D:\geronimo server-1\bin\etc\server-configuration.xml does not exist, id=10,
> cid=7, sequence=10, timestamp=1209436607390 }
> 19:36:47,390 DEBUG (TcpTransportServer-0-0)
> [org.apache.mina.filter.executor.ExecutorFilter] Exiting since queue is empty
> for /127.0.0.1:3699
> 19:36:47,390 DEBUG (SocketAcceptorIoProcessor-0.0)
> [org.apache.mina.filter.executor.ExecutorFilter] Launching thread for
> /127.0.0.1:3699
> 19:36:47,453 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.remote.server.RshServer$Handler]
> [/127.0.0.1:3699] SENT: Fault{ result=java.lang.IllegalStateException: File
> D:\geronimo server-1\bin\etc\server-configuration.xml does not exist, id=10,
> cid=7, sequence=10, timestamp=
[jira] Assigned: (GERONIMO-3994) GShell command remote-control/server-control can not control the remote server
[
https://issues.apache.org/jira/browse/GERONIMO-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GERONIMO-3994:
--
Assignee: Jason Dillon (was: Jason Warner)
> GShell command remote-control/server-control can not control the remote server
> --
>
> Key: GERONIMO-3994
> URL: https://issues.apache.org/jira/browse/GERONIMO-3994
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands
>Affects Versions: 2.1.1, 2.1.2, 2.1.x
> Environment: Windows
>Reporter: YunFeng Ma
>Assignee: Jason Dillon
> Fix For: 2.1.1, 2.1.2, 2.1.x
>
>
> First run remote/rsh to login the remote rsh-server, then run the following
> gsh commands:
> {noformat}
> remote-control/server-control start defaultServer
> {noformat}
> No any response.
> Here is the gshell log in the remote server.
> {noformat}
> 19:36:47,234 DEBUG (SocketAcceptorIoProcessor-0.0)
> [org.apache.mina.filter.executor.ExecutorFilter] Launching thread for
> /127.0.0.1:3699
> 19:36:47,234 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.remote.server.RshServer$Handler]
> [/127.0.0.1:3699] RECEIVED: ExecuteMessage{ flavor=STRING, path=,
> args=[ remote-control/server-control start defaultServer ], id=7, cid=,
> sequence=7, timestamp=1209436607234 }
> 19:36:47,234 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandExecutor] Executing (String):
> remote-control/server-control start defaultServer
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.parser.CommandLineParser] Parsing from reader:
> [EMAIL PROTECTED]
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] CommandLine
> (org.apache.geronimo.gshell.parser.ASTCommandLine)
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] Expression
> (org.apache.geronimo.gshell.parser.ASTExpression)
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] PlainString(
> remote-control/server-control )
> (org.apache.geronimo.gshell.parser.ASTPlainString)
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] PlainString( start )
> (org.apache.geronimo.gshell.parser.ASTPlainString)
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandLineBuilder] PlainString(
> defaultServer ) (org.apache.geronimo.gshell.parser.ASTPlainString)
> 19:36:47,234 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.DefaultCommandExecutor] Executing
> (remote-control/server-control): [start, defaultServer]
> 19:36:47,234 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.plugin.PlexusCommandWrapper] Child container
> realm: gshell:e47ff117-c940-4e2e-87a8-5b9257bc16e9
> 19:36:47,343 DEBUG (TcpTransportServer-0-0)
> [org.codehaus.plexus.PlexusContainer] Found 0 components to load on start
> 19:36:47,343 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.commands.RemoteServerControlCommand.geronimo-commands:remote-server-control]
> Executing w/args: [start, defaultServer]
> 19:36:47,390 DEBUG (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.remote.server.handler.ExecuteHandler] Fault:
> java.lang.IllegalStateException: File D:\geronimo
> server-1\bin\etc\server-configuration.xml does not exist
> 19:36:47,390 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.remote.server.RshServer$Handler]
> [/127.0.0.1:3699] WRITE: Fault{ result=java.lang.IllegalStateException: File
> D:\geronimo server-1\bin\etc\server-configuration.xml does not exist, id=10,
> cid=7, sequence=10, timestamp=1209436607390 }
> 19:36:47,390 DEBUG (TcpTransportServer-0-0)
> [org.apache.mina.filter.executor.ExecutorFilter] Exiting since queue is empty
> for /127.0.0.1:3699
> 19:36:47,390 DEBUG (SocketAcceptorIoProcessor-0.0)
> [org.apache.mina.filter.executor.ExecutorFilter] Launching thread for
> /127.0.0.1:3699
> 19:36:47,453 INFO (TcpTransportServer-0-0)
> [org.apache.geronimo.gshell.remote.server.RshServer$Handler]
> [/127.0.0.1:3699] SENT: Fault{ result=java.lang.IllegalStateException: File
> D:\geronimo server-1\bin\etc\server-configuration.xml does not exist, id=10,
> cid=7, sequence=10, timestamp=1209436607390 }
> 19:36:47,453 DEBUG (TcpTransportServer-0-0)
> [org.apache.mina.filter.executor.ExecutorFilter] Exiting since queue
Re: [BUILD] trunk: Failed for Revision: 653204
I think this is related to loggers not being static in some gbean
instance data muck...
--jason
On May 4, 2008, at 9:32 PM, [EMAIL PROTECTED] wrote:
Geronimo Revision: 653204 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080504/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080504
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 32 minutes 47 seconds
[INFO] Finished at: Sun May 04 09:34:28 EDT 2008
[INFO] Final Memory: 327M/1012M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080504/logs-0900-tomcat/test.log
[INFO] [INFO] Tests are skipped.
[INFO] [INFO] [surefire:test {execution: test}]
[INFO] [INFO] Tests are skipped.
[INFO] [INFO] [jar:jar]
[INFO] [INFO] Building jar: /home/geronimo/geronimo/trunk/testsuite/
webservices-testsuite/jaxws-tests/jaxws-client/target/jaxws-
client-2.2-SNAPSHOT.jar
[INFO] [INFO] [geronimo:deploy-module {execution: deploy-service}]
[INFO] [INFO] Using non-artifact based module archive: /home/
geronimo/geronimo/trunk/testsuite/webservices-testsuite/jaxws-tests/
jaxws-client/target/jaxws-client-2.2-SNAPSHOT.jar
[INFO] [INFO] Using non-artifact based plan: null
[INFO] [INFO] Distributing module artifact: /home/geronimo/geronimo/
trunk/testsuite/webservices-testsuite/jaxws-tests/jaxws-client/
target/jaxws-client-2.2-SNAPSHOT.jar with plan null
[WARNING] Deployer operation failed: java.io.IOException: Unable to
serialize GBeanData for JEE5/JAXWSClient/1.1/car?
J2EEApplication=JEE5/JAXWSClient/1.1/
car,j2eeType=StaticJndiContext,name=StaticJndiContext
[WARNING] org.apache.geronimo.common.DeploymentException:
java.io.IOException: Unable to serialize GBeanData for JEE5/
JAXWSClient/1.1/car?J2EEApplication=JEE5/JAXWSClient/1.1/
car,j2eeType=StaticJndiContext,name=StaticJndiContext
[WARNING] at
org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:275)
[WARNING] at
org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:133)
[WARNING] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[WARNING] at
sun
.reflect
.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[WARNING] at
sun
.reflect
.DelegatingMethodAccessorImpl
.invoke(DelegatingMethodAccessorImpl.java:25)
[WARNING] at java.lang.reflect.Method.invoke(Method.java:585)
[WARNING] at
org
.apache
.geronimo
.gbean
.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:
34)
[WARNING] at
org
.apache
.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
[WARNING] at
org
.apache
.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:849)
[WARNING] at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:
236)
[WARNING] at
org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342)
[WARNING] at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown
Source)
[WARNING] at
sun
.reflect
.DelegatingMethodAccessorImpl
.invoke(DelegatingMethodAccessorImpl.java:25)
[WARNING] at java.lang.reflect.Method.invoke(Method.java:585)
[WARNING] at
org
.apache
.geronimo
.gbean
.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:
34)
[WARNING] at
org
.apache
.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
[WARNING] at
org
.apache
.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:849)
[WARNING] at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:
236)
[WARNING] at
org
.apache
.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:
172)
[WARNING] at
com
.sun
.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:
213)
[WARNING] at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
[WARNING] at
com
.sun
.jmx
.interceptor
.DefaultMBeanServerInterceptor
.invoke(DefaultMBeanServerInterceptor.java:815)
[WARNING] at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
[WARNING] at
javax
.management
.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410)
[WARNING] at javax.management.remote.rmi.RMIConnectionImpl.access
$100(RMIConnectionImpl.java:81)
[WARNING] at javax.management.remote.rmi.RMIConnectionImpl
$PrivilegedOperation.run(RMIConnectionImpl.java:1247)
[WARNING] at java.security.AccessController.doPrivileged(Native
Method)
[WARNING] at
javax
.management
.remote
.rmi.RMIConnectionImpl.doPrivileg
Re: svn commit: r651912 - in /geronimo/server/trunk/framework/modules/geronimo-naming/src/main/java/org/apache/geronimo/gjndi: KernelContextGBean.java binding/GBeanBinding.java binding/GBeanFormatBind
Ya, I think so... I *ucked up when I did the conversion. Though using
instance loggers does provide more ability to provide context specific
logging muck, and is recommended by the SLF4J docs. But I'm finding
some problem with GBean serialization... trying to track it down.
IMO instance loggers are preferable, but parts of the system need the
statics... :-\
--jason
On Apr 27, 2008, at 5:31 PM, Gianny Damour wrote:
The same goes for many many logs no?
Thanks,
Gianny
On 27/04/2008, at 8:20 PM, [EMAIL PROTECTED] wrote:
Author: jdillon
Date: Sun Apr 27 03:20:35 2008
New Revision: 651912
URL: http://svn.apache.org/viewvc?rev=651912&view=rev
Log:
Make loggers static again
Modified:
geronimo/server/trunk/framework/modules/geronimo-naming/src/main/
java/org/apache/geronimo/gjndi/KernelContextGBean.java
geronimo/server/trunk/framework/modules/geronimo-naming/src/main/
java/org/apache/geronimo/gjndi/binding/GBeanBinding.java
geronimo/server/trunk/framework/modules/geronimo-naming/src/main/
java/org/apache/geronimo/gjndi/binding/GBeanFormatBinding.java
Modified: geronimo/server/trunk/framework/modules/geronimo-naming/
src/main/java/org/apache/geronimo/gjndi/KernelContextGBean.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-naming/src/main/java/org/apache/geronimo/gjndi/KernelContextGBean.java?rev=651912&r1=651911&r2=651912&view=diff
=
=
=
=
=
=
=
=
=
=
--- geronimo/server/trunk/framework/modules/geronimo-naming/src/
main/java/org/apache/geronimo/gjndi/KernelContextGBean.java
(original)
+++ geronimo/server/trunk/framework/modules/geronimo-naming/src/
main/java/org/apache/geronimo/gjndi/KernelContextGBean.java Sun Apr
27 03:20:35 2008
@@ -45,7 +45,7 @@
* @version $Rev$ $Date$
*/
public class KernelContextGBean extends WritableContext implements
GBeanLifecycle {
-private final Logger log = LoggerFactory.getLogger(getClass());
+private static final Logger log =
LoggerFactory.getLogger(KernelContextGBean.class);
private final Kernel kernel;
private final AbstractNameQuery abstractNameQuery;
Modified: geronimo/server/trunk/framework/modules/geronimo-naming/
src/main/java/org/apache/geronimo/gjndi/binding/GBeanBinding.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-naming/src/main/java/org/apache/geronimo/gjndi/binding/GBeanBinding.java?rev=651912&r1=651911&r2=651912&view=diff
=
=
=
=
=
=
=
=
=
=
--- geronimo/server/trunk/framework/modules/geronimo-naming/src/
main/java/org/apache/geronimo/gjndi/binding/GBeanBinding.java
(original)
+++ geronimo/server/trunk/framework/modules/geronimo-naming/src/
main/java/org/apache/geronimo/gjndi/binding/GBeanBinding.java Sun
Apr 27 03:20:35 2008
@@ -40,7 +40,7 @@
* @version $Rev$ $Date$
*/
public class GBeanBinding implements GBeanLifecycle {
-private final Logger log = LoggerFactory.getLogger(getClass());
+private static final Logger log =
LoggerFactory.getLogger(GBeanBinding.class);
private final Context context;
private final String name;
Modified: geronimo/server/trunk/framework/modules/geronimo-naming/
src/main/java/org/apache/geronimo/gjndi/binding/
GBeanFormatBinding.java
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-naming/src/main/java/org/apache/geronimo/gjndi/binding/GBeanFormatBinding.java?rev=651912&r1=651911&r2=651912&view=diff
=
=
=
=
=
=
=
=
=
=
--- geronimo/server/trunk/framework/modules/geronimo-naming/src/
main/java/org/apache/geronimo/gjndi/binding/GBeanFormatBinding.java
(original)
+++ geronimo/server/trunk/framework/modules/geronimo-naming/src/
main/java/org/apache/geronimo/gjndi/binding/GBeanFormatBinding.java
Sun Apr 27 03:20:35 2008
@@ -42,7 +42,7 @@
* @version $Rev$ $Date$
*/
public class GBeanFormatBinding extends KernelContextGBean {
-protected final Logger log =
LoggerFactory.getLogger(getClass());
+protected static final Logger log =
LoggerFactory.getLogger(GBeanFormatBinding.class);
private static final Pattern PATTERN = Pattern.compile("(\\{)(\
\w+)(})");
protected final String format;
[jira] Updated: (GERONIMO-2475) Extend the scope of the condition expression to support plugins (maybe more)
[ https://issues.apache.org/jira/browse/GERONIMO-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GERONIMO-2475: --- Fix Version/s: 2.2 Assignee: (was: Jason Dillon) > Extend the scope of the condition expression to support plugins (maybe more) > > > Key: GERONIMO-2475 > URL: https://issues.apache.org/jira/browse/GERONIMO-2475 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: core >Reporter: Jason Dillon > Fix For: 2.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2474) Pick the Jexl or Ognl parser for condition expression evaluation
[ https://issues.apache.org/jira/browse/GERONIMO-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-2474. -- Resolution: Fixed Fix Version/s: 2.2 Dropped OGNL support > Pick the Jexl or Ognl parser for condition expression evaluation > > > Key: GERONIMO-2474 > URL: https://issues.apache.org/jira/browse/GERONIMO-2474 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: core >Affects Versions: 1.2 > Reporter: Jason Dillon >Assignee: Jason Dillon >Priority: Minor > Fix For: 2.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [BUILD] trunk: Failed for Revision: 651174
Did something in openejb change recently? These tests were all passing while I was testing my SLF4J changes with `mvn -o` and then I did an online built and now they are failing because of: java.lang.NullPointerException: context or beanClass input parameter is null at org .apache.openejb.core.CoreDeploymentInfo.(CoreDeploymentInfo.java: 182) at org .apache .geronimo .openejb.cluster.stateful.container.ClusteredStatefulContainerTest $1.(ClusteredStatefulContainerTest.java:107) at org .apache .geronimo .openejb .cluster .stateful .container .ClusteredStatefulContainerTest .setUp(ClusteredStatefulContainerTest.java:95) at com.agical.rmock.extension.junit.BasicJUnitStrategyTestCase $1.run(BasicJUnitStrategyTestCase.java:32) at com .agical.rmock.core.strategy.impl.CompositeStep.run(CompositeStep.java: 24) at com.agical.rmock.core.strategy.impl.FinallyStep.run(FinallyStep.java:19) at com.agical.rmock.core.expectation.Engine.runStrategy(Engine.java: 142) ... and java.lang.IllegalStateException: No existing context at org.apache.openejb.core.ThreadContext.exit(ThreadContext.java:65) at org .apache .geronimo .openejb .cluster .stateful .container .ClusteredStatefulInstanceManagerTest .tearDown(ClusteredStatefulInstanceManagerTest.java:102) at com.agical.rmock.extension.junit.BasicJUnitStrategyTestCase $2.run(BasicJUnitStrategyTestCase.java:61) at com.agical.rmock.core.strategy.impl.FinallyStep.run(FinallyStep.java:23) at com.agical.rmock.core.expectation.Engine.runStrategy(Engine.java: 142) It appears to be unrelated to SLF4J changes, but I'm not sure... anyone know better why these tests are failing? --jason On Apr 24, 2008, at 3:55 PM, [EMAIL PROTECTED] wrote: Geronimo Revision: 651174 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080424/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20080424 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 32 minutes 43 seconds [INFO] Finished at: Thu Apr 24 03:40:55 EDT 2008 [INFO] Final Memory: 337M/672M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080424/logs-0300-tomcat/test.log Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080424/logs-0300-jetty/test.log [INFO] Running TestSuite [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 79.962 sec <<< FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20080424/samples-0300.log Build status: OK
[jira] Commented: (GERONIMO-3661) Optimize GShell libs for G server assemblies
[ https://issues.apache.org/jira/browse/GERONIMO-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592475#action_12592475 ] Jason Dillon commented on GERONIMO-3661: This is pending the GShell implementation of dependencies via maven-artifact. > Optimize GShell libs for G server assemblies > > > Key: GERONIMO-3661 > URL: https://issues.apache.org/jira/browse/GERONIMO-3661 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Affects Versions: 2.1 >Reporter: Jason Dillon >Assignee: Jason Dillon >Priority: Blocker > Fix For: 2.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2474) Pick the Jexl or Ognl parser for condition expression evaluation
[ https://issues.apache.org/jira/browse/GERONIMO-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592474#action_12592474 ] Jason Dillon commented on GERONIMO-2474: I'm still leaning towords Jexl... and will probably drop Ognl stuff soon. > Pick the Jexl or Ognl parser for condition expression evaluation > > > Key: GERONIMO-2474 > URL: https://issues.apache.org/jira/browse/GERONIMO-2474 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: core >Affects Versions: 1.2 >Reporter: Jason Dillon >Assignee: Jason Dillon >Priority: Minor > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3978) Unable to CTRL-C "start-server" process on Windows
[ https://issues.apache.org/jira/browse/GERONIMO-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GERONIMO-3978: --- Summary: Unable to CTRL-C "start-server" process on Windows (was: Problem when Geronimo 2.1 server is started using "start-server") > Unable to CTRL-C "start-server" process on Windows > -- > > Key: GERONIMO-3978 > URL: https://issues.apache.org/jira/browse/GERONIMO-3978 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Environment: Win XP, G Tomcat 2.1 > Reporter: Vamsavardhana Reddy >Assignee: Jason Dillon > > On Windows XP, if I start a Geronimo Tomcat 2.1 server using bin\start-server > from a command prompt, I am noticing that the server can not be shutdown > using Control+C. So, I am using Admin Console to shutdown the server. But > it does not return to command prompt unless I kill the java process from > Windows Task Manager. > Jarek says, "As a workaround, you can start gshell with -T false option and > then > control-c worked fine while running the server in foreground." > See http://www.mail-archive.com/dev@geronimo.apache.org/msg57308.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3985) Use SLF4J as the logging facade for Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-3985. -- Resolution: Fixed Fix Version/s: 2.2 > Use SLF4J as the logging facade for Geronimo > > > Key: GERONIMO-3985 > URL: https://issues.apache.org/jira/browse/GERONIMO-3985 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Reporter: Jason Dillon >Assignee: Jason Dillon > Fix For: 2.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Geronimo server/trunk is now using SLF4J
I've just committed my changes to used SLF4J as the primary logging
facade for server/trunk.
Commons logging should be completely gone now. For dependencies which
use JCL, we are using the jcl104-over-slf4j adapter which provides the
JCL API and tunnels it through SLF4J.
I still need to hook up the - stuff to turn up the verbosity,
might get to that tonight. Otherwise, looks like things most just
work as they did before.
* * *
Now the thing to do is to start cleaning up logging code to make use
of SLF4J's more elegant API. Thats primarily the varargs methods and
{} substing magic it has. So something like this:
if (log.isDebugEnabled()) {
log.debug("This is foo: " + foo + ", this is bar: " + bar);
}
becomes simply:
log.debug("This is foo: {}, this is bar: {}", foo, bar);
* * *
We are still using Log4j as the underlying logging provider, which
SLF4J delegates to. I did however nuke the caching bits, and we no
longer have any special bootstrap logging stuff. Just a
log4j.properties in geronimo-cli which provides the bootstrap log4j
configuration used before the Log4jService boots up.
* * *
Let me know if you run into any problems.
Cheers,
--jason
Re: [GSHELL] Unable to build gshell
There are some other issues I noticed with the shading, but as long as you clean install its happy. Will fix soonish. --jason On Apr 25, 2008, at 8:59 PM, Jason Warner wrote: I'm actually having trouble building GShell myself. I'm getting a weird error. I haven't had time to look at it yet but maybe I'll just throw it out there in case you've seen it before. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating shaded jar. Embedded error: duplicate entry: org/apache/geronimo/gshell/common/ Arguments.class [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error creating shaded jar. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 564) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 459) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:278) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun .reflect .DelegatingMethodAccessorImpl .invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating shaded jar. at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java: 327) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 443) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 539) ... 16 more Caused by: java.util.zip.ZipException: duplicate entry: org/apache/ geronimo/gshell/common/Arguments.class at java.util.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:163) at java.util.jar.JarOutputStream.putNextEntry(JarOutputStream.java:90) at org .apache .maven .plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:182) at org .apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java: 104) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java: 285) ... 18 more Look familiar at all? On Fri, Apr 25, 2008 at 9:50 AM, Jason Dillon <[EMAIL PROTECTED]> wrote: No, I have not pulled in your changes yet. The repo is already defined in the parent pom here: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/config/project-config/1.3/project-config-1.3.pom --jason On Apr 25, 2008, at 8:42 PM, Guillaume Nodet wrote: Yeah, I've just added the plugin repo ;-) On Fri, Apr 25, 2008 at 3:40 PM, Jason Dillon <[EMAIL PROTECTED]> wrote: They are available here (and have been for many days now): http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/ The build seems to be happy from what I can tell... chugging away, downloading things fine: Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/runtime/gmaven-runtime-1.5/1.0-beta-4-SNAPSHOT/gmaven-runtime-1.5-1.0-beta-4-20080419.173658-4.jar 43K downloaded Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/feature/gmaven-feature-support/1.0-beta-4-SNAPSHOT/gmaven-feature-support-1.0-beta-4-20080418.100607-1.jar 15K downloaded Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/runtime/gmaven-runtime-support/1.0-beta-4-SNAPSHOT/gmaven-runtime-support-1.0-beta-4-20080419.173658-5.jar 71K downloaded --jason On Apr 25, 2008, at 3:34 PM, Guillaume Nodet wrote: Gshell is missing the following dependency: org.codehaus.groovy.maven:gmaven-plugin:pom:1.0-beta-4-SNAPSHOT Is there anyway it can be uploaded to a know snapshot repo so that gshell can
Re: svn commit: r651601 - /geronimo/gshell/trunk/pom.xml
Kay. --jason On Apr 25, 2008, at 9:00 PM, Guillaume Nodet wrote: So I've removed the repositories definition, but I've kept the override of the organization, because the informations from the genesis-config are wrong. The apache top pom says: The Apache Software Foundation http://www.apache.org/ and these are the agreed on values, but genesis override those with: Apache Software Foundation http://www.apache.org I think genesis should be fixed and those values removed from the genesis pom, so in the mean time, i'd rather have them overriden to the correct values in the gshell parent pom. On Fri, Apr 25, 2008 at 3:56 PM, Jason Dillon <[EMAIL PROTECTED]> wrote: Kay, I understand... blame maven, thats what I do :-P --jason On Apr 25, 2008, at 8:50 PM, Guillaume Nodet wrote: Right, not sure why it failed the first time. I'll remove the repository from the pom. On Fri, Apr 25, 2008 at 3:44 PM, Jason Dillon <[EMAIL PROTECTED]> wrote: This is duplicate information which is picked up from genesis project-config. Please revert. --jason On Apr 25, 2008, at 8:28 PM, [EMAIL PROTECTED] wrote: Author: gnodet Date: Fri Apr 25 06:28:41 2008 New Revision: 651601 URL: http://svn.apache.org/viewvc?rev=651601&view=rev Log: Add repository for the gmaven plugin Modified: geronimo/gshell/trunk/pom.xml Modified: geronimo/gshell/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/gshell/trunk/pom.xml?rev=651601&r1=651600&r2=651601&view=diff = = = = = = = = = = --- geronimo/gshell/trunk/pom.xml (original) +++ geronimo/gshell/trunk/pom.xml Fri Apr 25 06:28:41 2008 @@ -37,6 +37,11 @@ 1.0-alpha-2-SNAPSHOT + +The Apache Software Foundation +http://www.apache.org/ + + GShell is a framework for building rich command-line applications. @@ -640,6 +645,22 @@ + + +codehaus-snapshots +Codehaus Snapshots Repository +http://snapshots.repository.codehaus.org +default + +true +daily +ignore + + +false + + + -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: svn commit: r651601 - /geronimo/gshell/trunk/pom.xml
Kay, I understand... blame maven, thats what I do :-P --jason On Apr 25, 2008, at 8:50 PM, Guillaume Nodet wrote: Right, not sure why it failed the first time. I'll remove the repository from the pom. On Fri, Apr 25, 2008 at 3:44 PM, Jason Dillon <[EMAIL PROTECTED]> wrote: This is duplicate information which is picked up from genesis project-config. Please revert. --jason On Apr 25, 2008, at 8:28 PM, [EMAIL PROTECTED] wrote: Author: gnodet Date: Fri Apr 25 06:28:41 2008 New Revision: 651601 URL: http://svn.apache.org/viewvc?rev=651601&view=rev Log: Add repository for the gmaven plugin Modified: geronimo/gshell/trunk/pom.xml Modified: geronimo/gshell/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/gshell/trunk/pom.xml?rev=651601&r1=651600&r2=651601&view=diff = = = = = = = = = = --- geronimo/gshell/trunk/pom.xml (original) +++ geronimo/gshell/trunk/pom.xml Fri Apr 25 06:28:41 2008 @@ -37,6 +37,11 @@ 1.0-alpha-2-SNAPSHOT + +The Apache Software Foundation +http://www.apache.org/ + + GShell is a framework for building rich command-line applications. @@ -640,6 +645,22 @@ + + +codehaus-snapshots +Codehaus Snapshots Repository +http://snapshots.repository.codehaus.org +default + +true +daily +ignore + + +false + + + -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: [GSHELL] Unable to build gshell
No, I have not pulled in your changes yet. The repo is already defined in the parent pom here: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/config/project-config/1.3/project-config-1.3.pom --jason On Apr 25, 2008, at 8:42 PM, Guillaume Nodet wrote: Yeah, I've just added the plugin repo ;-) On Fri, Apr 25, 2008 at 3:40 PM, Jason Dillon <[EMAIL PROTECTED]> wrote: They are available here (and have been for many days now): http://snapshots.repository.codehaus.org/org/codehaus/groovy/ maven/ The build seems to be happy from what I can tell... chugging away, downloading things fine: Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/runtime/gmaven-runtime-1.5/1.0-beta-4-SNAPSHOT/gmaven-runtime-1.5-1.0-beta-4-20080419.173658-4.jar 43K downloaded Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/feature/gmaven-feature-support/1.0-beta-4-SNAPSHOT/gmaven-feature-support-1.0-beta-4-20080418.100607-1.jar 15K downloaded Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/runtime/gmaven-runtime-support/1.0-beta-4-SNAPSHOT/gmaven-runtime-support-1.0-beta-4-20080419.173658-5.jar 71K downloaded --jason On Apr 25, 2008, at 3:34 PM, Guillaume Nodet wrote: Gshell is missing the following dependency: org.codehaus.groovy.maven:gmaven-plugin:pom:1.0-beta-4-SNAPSHOT Is there anyway it can be uploaded to a know snapshot repo so that gshell can download it ? -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: svn commit: r651601 - /geronimo/gshell/trunk/pom.xml
This is duplicate information which is picked up from genesis project- config. Please revert. --jason On Apr 25, 2008, at 8:28 PM, [EMAIL PROTECTED] wrote: Author: gnodet Date: Fri Apr 25 06:28:41 2008 New Revision: 651601 URL: http://svn.apache.org/viewvc?rev=651601&view=rev Log: Add repository for the gmaven plugin Modified: geronimo/gshell/trunk/pom.xml Modified: geronimo/gshell/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/gshell/trunk/pom.xml?rev=651601&r1=651600&r2=651601&view=diff = = = = = = = = == --- geronimo/gshell/trunk/pom.xml (original) +++ geronimo/gshell/trunk/pom.xml Fri Apr 25 06:28:41 2008 @@ -37,6 +37,11 @@ 1.0-alpha-2-SNAPSHOT + +The Apache Software Foundation +http://www.apache.org/ + + GShell is a framework for building rich command-line applications. @@ -640,6 +645,22 @@ + + +codehaus-snapshots +Codehaus Snapshots Repository +http://snapshots.repository.codehaus.org +default + +true +daily +ignore + + +false + + +
[jira] Commented: (GERONIMO-2401) Upgrade commons-logging to 1.1
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592375#action_12592375 ] Jason Dillon commented on GERONIMO-2401: Ya, too late... the heavy lifting is all done now, not that heavy though ;-) > Upgrade commons-logging to 1.1 > -- > > Key: GERONIMO-2401 > URL: https://issues.apache.org/jira/browse/GERONIMO-2401 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: dependencies, Logging >Affects Versions: 1.2, 2.0-M5 >Reporter: Jason Dillon >Assignee: Jason Dillon > Fix For: 2.2 > > > Upgrade commons-logging to the latest release 1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [GSHELL] Unable to build gshell
They are available here (and have been for many days now): http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/ The build seems to be happy from what I can tell... chugging away, downloading things fine: Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/runtime/gmaven-runtime-1.5/1.0-beta-4-SNAPSHOT/gmaven-runtime-1.5-1.0-beta-4-20080419.173658-4.jar 43K downloaded Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/feature/gmaven-feature-support/1.0-beta-4-SNAPSHOT/gmaven-feature-support-1.0-beta-4-20080418.100607-1.jar 15K downloaded Downloading: http://snapshots.repository.codehaus.org/org/codehaus/groovy/maven/runtime/gmaven-runtime-support/1.0-beta-4-SNAPSHOT/gmaven-runtime-support-1.0-beta-4-20080419.173658-5.jar 71K downloaded --jason On Apr 25, 2008, at 3:34 PM, Guillaume Nodet wrote: Gshell is missing the following dependency: org.codehaus.groovy.maven:gmaven-plugin:pom:1.0-beta-4-SNAPSHOT Is there anyway it can be uploaded to a know snapshot repo so that gshell can download it ? -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: Platform scripts, cli tooling and GShell
Okay, I'll look at getting that sorted after I finish the SLF4J stuff. --jason On Apr 24, 2008, at 10:59 PM, David Jencks wrote: On Apr 24, 2008, at 1:19 AM, Jason Dillon wrote: Anyone know what the status of the GShell commands are for bin/ client and bin/deploy users? They've all been implemented and worked at one time :-) I think we need to clean up these scripts, so they all go through GShell, and drop the additional platform-specific script muck. +1 from me Anyone know how well the GShell commands cover the functionality of the previous cli bits? I don't know of any missing functionality, but haven't looked at this for a long time. thanks david jencks --jason
Re: SLF4J over Commons Logging
Took way too long at the airport, so punting commit until tomorrow
when I'm awake again.
--jason
On Apr 24, 2008, at 5:18 AM, David Jencks wrote:
+higher than I can count :-)
thanks
david jencks
On Apr 23, 2008, at 1:25 PM, Jason Dillon wrote:
Yo yo... we've talked about this before, though a while ago... but
IMO its about time we drop Commons Logging like a rock and move
over to SLF4J.
The API is mostly the same, though SLF4J has native support for
things like:
log.trace()
And has additional varargs support for things like:
log.info("this is my foo: {}", foo)
I can dig up the old email I posted hella long ago if needed, but I
think its time to switch over. Its been on the shelf for too long
already IMO. I'm ready to start updating things to use the new
API, but before I do I want to get a general consensus from the
group.
So chime in... failure to chime in means you agree with me :-P
:-)
--jason
Re: SLF4J over Commons Logging
Aight... well, ~9 hours later, I think its working or at 99% I need
to re-add support for the org.apache.geronimo.log.ConsoleLogLevel
property, perhaps even add a special bootstrap SLF4J impl, but I think
that the work is almost ready to commit.
Re-building to see how the testsuite fairs with my latest changes...
and I have to go pick up my mom at the airport, but I hope to get this
committed later tonight :-)
--jason
On Apr 24, 2008, at 5:18 AM, David Jencks wrote:
+higher than I can count :-)
thanks
david jencks
On Apr 23, 2008, at 1:25 PM, Jason Dillon wrote:
Yo yo... we've talked about this before, though a while ago... but
IMO its about time we drop Commons Logging like a rock and move
over to SLF4J.
The API is mostly the same, though SLF4J has native support for
things like:
log.trace()
And has additional varargs support for things like:
log.info("this is my foo: {}", foo)
I can dig up the old email I posted hella long ago if needed, but I
think its time to switch over. Its been on the shelf for too long
already IMO. I'm ready to start updating things to use the new
API, but before I do I want to get a general consensus from the
group.
So chime in... failure to chime in means you agree with me :-P
:-)
--jason
Re: SLF4J over Commons Logging
And testing now :-)
--jason
On Apr 24, 2008, at 5:18 AM, David Jencks wrote:
+higher than I can count :-)
thanks
david jencks
On Apr 23, 2008, at 1:25 PM, Jason Dillon wrote:
Yo yo... we've talked about this before, though a while ago... but
IMO its about time we drop Commons Logging like a rock and move
over to SLF4J.
The API is mostly the same, though SLF4J has native support for
things like:
log.trace()
And has additional varargs support for things like:
log.info("this is my foo: {}", foo)
I can dig up the old email I posted hella long ago if needed, but I
think its time to switch over. Its been on the shelf for too long
already IMO. I'm ready to start updating things to use the new
API, but before I do I want to get a general consensus from the
group.
So chime in... failure to chime in means you agree with me :-P
:-)
--jason
Re: SLF4J over Commons Logging
Almost done ;-)
--jason
On Apr 24, 2008, at 5:18 AM, David Jencks wrote:
+higher than I can count :-)
thanks
david jencks
On Apr 23, 2008, at 1:25 PM, Jason Dillon wrote:
Yo yo... we've talked about this before, though a while ago... but
IMO its about time we drop Commons Logging like a rock and move
over to SLF4J.
The API is mostly the same, though SLF4J has native support for
things like:
log.trace()
And has additional varargs support for things like:
log.info("this is my foo: {}", foo)
I can dig up the old email I posted hella long ago if needed, but I
think its time to switch over. Its been on the shelf for too long
already IMO. I'm ready to start updating things to use the new
API, but before I do I want to get a general consensus from the
group.
So chime in... failure to chime in means you agree with me :-P
:-)
--jason
Platform scripts, cli tooling and GShell
Anyone know what the status of the GShell commands are for bin/client and bin/deploy users? I think we need to clean up these scripts, so they all go through GShell, and drop the additional platform-specific script muck. Anyone know how well the GShell commands cover the functionality of the previous cli bits? --jason
Re: svn commit: r650176 - in /geronimo/server/trunk: ./ assemblies/geronimo-boilerplate-minimal/ assemblies/geronimo-boilerplate-minimal/src/main/assembly/ assemblies/geronimo-boilerplate-minimal/src/
On Apr 24, 2008, at 9:51 AM, Donald Woods wrote:
Jason, could you explain this change a little. Does this mean trunk
now uses a private build of ANT from the groovy project at Codehaus?
Yes and no... it uses a patched Ant:
https://svn.codehaus.org/groovy/gmaven/trunk/gmaven-support/ant-1.7.0
Which contains all of the original org.apache.ant:ant stuff with this
one class overwritten to encode URI's correctly for Winblows:
https://svn.codehaus.org/groovy/gmaven/trunk/gmaven-support/ant-1.7.0/src/main/java/org/apache/tools/ant/launch/Locator.java
Shouldn't we just be using a ANT trunk-snapshot instead?
No, cause then stuff starts puking when there is any spaces in
classpath elements (ie "Documents and Settings" or "Program Files").
I've no idea if the Ant folks ever fixed this. I guess we should ask
them to fix it...
I'd like to merge this change in 2.1.2 to fix the Windows problem,
but I'm a little weary on pulling in beta/snapshot code at this
point
Well, I think the best thing todo would be to ask the nice folks over
at the Ant project if they could apply this fix and make a 1.7.1, then
we wouldn't need this at all...
--jason
-Donald
[EMAIL PROTECTED] wrote:
Author: jdillon
Date: Mon Apr 21 08:41:52 2008
New Revision: 650176
URL: http://svn.apache.org/viewvc?rev=650176&view=rev
Log:
(GERONIMO-3977) Use gmaven's ant 1.7.0 libraries which are
compatible with Groovy and Windows
Modified:
geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
pom.xml
geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
src/main/assembly/boilerplate.xml
geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
src/main/underlay/etc/gsh-classworlds.conf
geronimo/server/trunk/framework/modules/geronimo-commands/pom.xml
geronimo/server/trunk/pom.xml
Modified: geronimo/server/trunk/assemblies/geronimo-boilerplate-
minimal/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/pom.xml?rev=650176&r1=650175&r2=650176&view=diff
=
=
=
=
=
=
=
=
=
=
--- geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
pom.xml (original)
+++ geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
pom.xml Mon Apr 21 08:41:52 2008
@@ -109,10 +109,17 @@
+org.codehaus.groovy.maven.support
+ant-1.7.0
+
++
+
org.apache.ant
ant-launcher
Modified: geronimo/server/trunk/assemblies/geronimo-boilerplate-
minimal/src/main/assembly/boilerplate.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/src/main/assembly/boilerplate.xml?rev=650176&r1=650175&r2=650176&view=diff
=
=
=
=
=
=
=
=
=
=
--- geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
src/main/assembly/boilerplate.xml (original)
+++ geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
src/main/assembly/boilerplate.xml Mon Apr 21 08:41:52 2008
@@ -138,7 +138,6 @@
org.apache.yoko:yoko-rmi-spec
-
Modified: geronimo/server/trunk/assemblies/geronimo-boilerplate-
minimal/src/main/underlay/etc/gsh-classworlds.conf
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/src/main/underlay/etc/gsh-classworlds.conf?rev=650176&r1=650175&r2=650176&view=diff
=
=
=
=
=
=
=
=
=
=
--- geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
src/main/underlay/etc/gsh-classworlds.conf (original)
+++ geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/
src/main/underlay/etc/gsh-classworlds.conf Mon Apr 21 08:41:52 2008
@@ -26,7 +26,8 @@
[gshell]
load ${gshell.home}/etc
load ${gshell.home}/lib/gshell/*.jar
-load ${gshell.home}/repository/org/apache/ant/ant/1.7.0/ant-
*.jar
+load ${gshell.home}/repository/org/codehaus/groovy/maven/
support/ant-1.7.0/1.0-beta-4-SNAPSHOT/ant-1.7.0-*.jar
+#load ${gshell.home}/repository/org/apache/ant/ant/1.7.0/ant-
*.jar
load ${gshell.home}/repository/org/apache/ant/ant-launcher/
1.7.0/ant-launcher-*.jar
load ${gshell.home}/repository/org/apache/geronimo/gshell/
gshell-cli/1.0-alpha-1/gshell-cli-*.jar
load ${gshell.home}/repository/org/apache/geronimo/gshell/
gshell-embeddable/1.0-alpha-1/gshell-embeddable-*.jar
Modified: geronimo/server/trunk/framework/modules/geronimo-commands/
pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-commands/pom.xml?rev=650176&r1=650175&r2=650176&view=diff
=
=
=
=
=
=
=
=
=
=
--- geronimo/server/trunk/framework/modules/
Re: [DISCUSS] Geronimo Server 2.1.1 Release
Um, this is really where they belong those, since they are specific to Geronimo. But it should be possible to generate the resources w/o license details... but probably have to use the new archetype-ng stuff, which is on my list todo actually... --jason On Apr 24, 2008, at 5:23 AM, David Jencks wrote: Maybe apache is not the place for these archetypes.I don't want users of these archetypes to have to include a NOTICE file crediting apache simply because they kick-started their project by using these archetypes before doing all the customization to actually make them work. Should I move them to a codehaus mojo? thanks david jencks On Apr 23, 2008, at 2:45 PM, Kevan Miller wrote: On Apr 23, 2008, at 5:15 PM, Joe Bohn wrote: Kevan Miller wrote: On Apr 23, 2008, at 3:19 PM, Joe Bohn wrote: Discussion thread for the Geronimo 2.1.1 Release vote. We should make a habit of cc:'ing user list on release votes. Looking things over now. Afraid that there are some source files missing src license headers :-( --kevan Thanks Kevan. I'm anxiously awaiting your list. I will copy the user list on the next rev of the vote. svn ci --message "Update files missing src license headers. Most were added post-2.1.0. One was a reverted change post-2.1.0." Sending2.1/buildsupport/geronimo-assembly-archetype/pom.xml Sending2.1/buildsupport/geronimo-assembly-archetype/src/ main/resources/META-INF/maven/archetype.xml Sending2.1/buildsupport/geronimo-assembly-archetype/src/ main/resources/archetype-resources/pom.sample.xml Sending2.1/buildsupport/geronimo-assembly-archetype/src/ main/resources/archetype-resources/pom.xml Sending2.1/buildsupport/geronimo-plugin-archetype/src/main/ resources/META-INF/maven/archetype.xml Sending2.1/buildsupport/geronimo-plugin-archetype/src/main/ resources/archetype-resources/pom.sample.xml Sending2.1/buildsupport/geronimo-plugin-archetype/src/main/ resources/archetype-resources/pom.xml Sending2.1/framework/modules/geronimo-commands/src/test/ resources/etc/aliases.xml Sending2.1/plugins/monitoring/mconsole-ear/src/main/ resources/MonitoringClientDB.sql Transmitting file data . Committed revision 651078. 'merge -r 651077:651078 https://svn.apache.org/repos/asf/geronimo/server/branches/2.1 .' should do the trick... --kevan
Re: Legal files in server/trunk, ianal & m-r-r-p
On Apr 24, 2008, at 5:17 AM, David Jencks wrote: THANKS!! I didn't quite understand. do we need to push on the rar and war plugins for new, more m-r-r-p friendly releases? Um, I think the EAR, RAR and WAR plugins all need some kinda updated to allow more flexible resource inclusion. Maybe WAR is already good enough, but the others all suck. There is no need to get new versions, as I updated the build to work with their limitations, but I had to hack in some antrun here and there to make it work, which isn't very nice. --jason
Re: [DISCUSS] Geronimo Server 2.1.1 Release
Barf... I'll see if I can make the ianal-maven-plugin check for this ASAP... --jason On Apr 24, 2008, at 4:04 AM, Kevan Miller wrote: On Apr 23, 2008, at 3:19 PM, Joe Bohn wrote: Discussion thread for the Geronimo 2.1.1 Release vote. We should make a habit of cc:'ing user list on release votes. Looking things over now. Afraid that there are some source files missing src license headers :-( --kevan
[jira] Closed: (GSHELL-110) Upgrade Mina to 1.1.7
[ https://issues.apache.org/jira/browse/GSHELL-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-110. --- Resolution: Fixed > Upgrade Mina to 1.1.7 > - > > Key: GSHELL-110 > URL: https://issues.apache.org/jira/browse/GSHELL-110 > Project: GShell > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Whisper >Reporter: Jason Dillon > Assignee: Jason Dillon > Fix For: 1.0-alpha-2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GSHELL-110) Upgrade Mina to 1.1.7
Upgrade Mina to 1.1.7 - Key: GSHELL-110 URL: https://issues.apache.org/jira/browse/GSHELL-110 Project: GShell Issue Type: Improvement Security Level: public (Regular issues) Components: Whisper Reporter: Jason Dillon Assignee: Jason Dillon Fix For: 1.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Geronimo Server 2.1.1 Release
BTW, I'm about to commit a cli-testsuite, depending on if I can muster enough steam tonight to make it reality... which should help test the command-line interfaces to Geronimo better... or at least a start in that direction. --jason On Apr 24, 2008, at 3:20 AM, Jarek Gawor wrote: -1. GShell does not start up because the gsh-classworlds.conf file still refers to 2.1.1-SNAPSHOT jars. Jarek On Wed, Apr 23, 2008 at 10:31 AM, Joe Bohn <[EMAIL PROTECTED]> wrote: All, I've prepared a 2.1.1 release candidate for your review and vote. The source for the Geronimo 2.1.1 release currently resides here: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.1 When the release vote is approved, I will svn mv the code to https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.1 An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-2.1.1-src.tar.gz http://people.apache.org/~jbohn/geronimo-2.1.1-dist/ contains the 10 Java EE, Minimal, and Framework server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES and source code archives for the release. For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-jetty6-javaee5-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-jetty6-minimal-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-tomcat6-javaee5-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-tomcat6-minimal-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-framework-2.1.1-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.1/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo 2.1.1 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.1.1 (please provide rationale) I'll plan on calling this vote on Saturday evening (11 PM EST). I will start tck runs shortly on these images Joe Bohn
Re: [VOTE] Geronimo Server 2.1.1 Release
Barf, stupid gshell and its world of classes Sorry 'bout dat... hopefully I can make that file go away soon, or at least become so small that its not a problem anymore :-\ --jason On Apr 24, 2008, at 3:20 AM, Jarek Gawor wrote: -1. GShell does not start up because the gsh-classworlds.conf file still refers to 2.1.1-SNAPSHOT jars. Jarek On Wed, Apr 23, 2008 at 10:31 AM, Joe Bohn <[EMAIL PROTECTED]> wrote: All, I've prepared a 2.1.1 release candidate for your review and vote. The source for the Geronimo 2.1.1 release currently resides here: https://svn.apache.org/repos/asf/geronimo/server/branches/2.1.1 When the release vote is approved, I will svn mv the code to https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.1 An archive of this source code can be found here: http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-2.1.1-src.tar.gz http://people.apache.org/~jbohn/geronimo-2.1.1-dist/ contains the 10 Java EE, Minimal, and Framework server binary distributions to be released (framework, tomcat/jetty, Java EE/Minimal, tar/zip) as well as the RELEASE_NOTES and source code archives for the release. For your convenience, here are pointers to the urls for the distributions in zip format: http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-jetty6-javaee5-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-jetty6-minimal-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-tomcat6-javaee5-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-tomcat6-minimal-2.1.1-bin.zip http://people.apache.org/~jbohn/geronimo-2.1.1-dist/geronimo-framework-2.1.1-bin.zip The maven artifacts for the release can be found here: http://people.apache.org/~jbohn/staging-repo/geronimo-2.1.1/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Geronimo 2.1.1 [ ] 0 No opinion [ ] -1 Do not release Geronimo 2.1.1 (please provide rationale) I'll plan on calling this vote on Saturday evening (11 PM EST). I will start tck runs shortly on these images Joe Bohn
SLF4J over Commons Logging
Yo yo... we've talked about this before, though a while ago... but IMO
its about time we drop Commons Logging like a rock and move over to
SLF4J.
The API is mostly the same, though SLF4J has native support for things
like:
log.trace()
And has additional varargs support for things like:
log.info("this is my foo: {}", foo)
I can dig up the old email I posted hella long ago if needed, but I
think its time to switch over. Its been on the shelf for too long
already IMO. I'm ready to start updating things to use the new API,
but before I do I want to get a general consensus from the group.
So chime in... failure to chime in means you agree with me :-P
:-)
--jason
[jira] Closed: (GERONIMO-2401) Upgrade commons-logging to 1.1
[ https://issues.apache.org/jira/browse/GERONIMO-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-2401. -- Resolution: Fixed Fix Version/s: (was: Wish List) 2.2 Going with SLF4J as the logging facade instead of the problematic Commons Logging API. > Upgrade commons-logging to 1.1 > -- > > Key: GERONIMO-2401 > URL: https://issues.apache.org/jira/browse/GERONIMO-2401 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: dependencies, Logging >Affects Versions: 1.2, 2.0-M5 > Reporter: Jason Dillon >Assignee: Jason Dillon > Fix For: 2.2 > > > Upgrade commons-logging to the latest release 1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3986) Upgrade SLF4J to 1.5.0
[ https://issues.apache.org/jira/browse/GERONIMO-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-3986. -- Resolution: Fixed Fix Version/s: 2.2 > Upgrade SLF4J to 1.5.0 > -- > > Key: GERONIMO-3986 > URL: https://issues.apache.org/jira/browse/GERONIMO-3986 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Reporter: Jason Dillon >Assignee: Jason Dillon > Fix For: 2.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3986) Upgrade SLF4J to 1.5.0
[ https://issues.apache.org/jira/browse/GERONIMO-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon reassigned GERONIMO-3986: -- Assignee: Jason Dillon > Upgrade SLF4J to 1.5.0 > -- > > Key: GERONIMO-3986 > URL: https://issues.apache.org/jira/browse/GERONIMO-3986 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Reporter: Jason Dillon >Assignee: Jason Dillon > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3987) Upgrade Log4j to 1.2.15
[ https://issues.apache.org/jira/browse/GERONIMO-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-3987. -- Resolution: Fixed Fix Version/s: 2.2 > Upgrade Log4j to 1.2.15 > --- > > Key: GERONIMO-3987 > URL: https://issues.apache.org/jira/browse/GERONIMO-3987 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Reporter: Jason Dillon >Assignee: Jason Dillon > Fix For: 2.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3987) Upgrade Log4j to 1.2.15
Upgrade Log4j to 1.2.15 --- Key: GERONIMO-3987 URL: https://issues.apache.org/jira/browse/GERONIMO-3987 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Reporter: Jason Dillon Assignee: Jason Dillon -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3986) Upgrade SLF4J to 1.5.0
Upgrade SLF4J to 1.5.0 -- Key: GERONIMO-3986 URL: https://issues.apache.org/jira/browse/GERONIMO-3986 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Reporter: Jason Dillon -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3985) Use SLF4J as the logging facade for Geronimo
Use SLF4J as the logging facade for Geronimo Key: GERONIMO-3985 URL: https://issues.apache.org/jira/browse/GERONIMO-3985 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Reporter: Jason Dillon Assignee: Jason Dillon -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3978) Problem when Geronimo 2.1 server is started using "start-server"
[ https://issues.apache.org/jira/browse/GERONIMO-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591761#action_12591761 ] Jason Dillon commented on GERONIMO-3978: This has something todo with JLine... looking into it more. > Problem when Geronimo 2.1 server is started using "start-server" > > > Key: GERONIMO-3978 > URL: https://issues.apache.org/jira/browse/GERONIMO-3978 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Environment: Win XP, G Tomcat 2.1 >Reporter: Vamsavardhana Reddy >Assignee: Jason Dillon > > On Windows XP, if I start a Geronimo Tomcat 2.1 server using bin\start-server > from a command prompt, I am noticing that the server can not be shutdown > using Control+C. So, I am using Admin Console to shutdown the server. But > it does not return to command prompt unless I kill the java process from > Windows Task Manager. > Jarek says, "As a workaround, you can start gshell with -T false option and > then > control-c worked fine while running the server in foreground." > See http://www.mail-archive.com/dev@geronimo.apache.org/msg57308.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2924) Upgrade to latest commons-io 1.3.1
[ https://issues.apache.org/jira/browse/GERONIMO-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-2924. -- Resolution: Invalid Too old > Upgrade to latest commons-io 1.3.1 > -- > > Key: GERONIMO-2924 > URL: https://issues.apache.org/jira/browse/GERONIMO-2924 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 2.0-M7 > Reporter: Jason Dillon >Assignee: Jason Dillon >Priority: Minor > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3088) geroniom-activemq-ra's ra.xml is not kept in sync with the AMQ distribution
[ https://issues.apache.org/jira/browse/GERONIMO-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-3088. -- Resolution: Won't Fix Apparently not a problem... based on comments recently from DJencks and his chat with Hiram about the spec. > geroniom-activemq-ra's ra.xml is not kept in sync with the AMQ distribution > --- > > Key: GERONIMO-3088 > URL: https://issues.apache.org/jira/browse/GERONIMO-3088 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 1.2, 2.0-M5 >Reporter: Jason Dillon >Assignee: Jason Dillon >Priority: Minor > > Currently the geronimo-activemq-ra's (embedded AMQ RA) ra.xml is not kept in > sync with the AMQ dists activemq-rar. > Should update the build to extract the ra.xml and include that for the > embedded ra. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Legal files in server/trunk, ianal & m-r-r-p
Folks, I've updated server/trunk to build with the latest maven-remote- resources-plugin, using v1.4 of the jar resources plugin, which I understand generates the right bits. I also moved the legal file checking bits out into a separate plugin, ianal-maven-plugin, hosted at the Mojo project, which now helps ensure our modules are spitting out artifacts with legal mumbo in them. I've also go through and nuked almost all of the LICENSE.txt and NOTICE.txt files littered throughout the tree, most of them were the same anyways. For those that had additions, I've added m-r-r-p configuration to append those critical legal details to the files which are included. So now there are only the LICENSE.txt, NOTICE.txt in the top-level under server/trunk and the files which are included in the assemblies under assemblies/geronimo-boilerplate-minimal/src/main/underlay. I did drop the .txt suffix on those files, which I have mixed feelings about... but it makes it easier to keep the ianal plugin (and configuration of it) simple since the m-r-r-p doesn't generate .txt extensions. Had to add a few wee hacks, for all RAR modules and a few WAR and EAR modules to get the m-r-r-p generated files included... those plugins aren't really m-r-r-p friendly, but I gave Maven a kick in the ass to make it do my bidding as usual ;-) And its nothing major, just a bit of a PITA... extra pom code blah. * * * So, now server/trunk is *completely* from using the old genesis tools- maven-plugin. Still using maven-maven-plugin, but I hope to fix that soon. And then I'll re-craft genesis 2.x to reduce alot of the common pom muck we have in server/trunk/pom.xml. Cheers, --jason
Added profile support to geronimo/start-server (aka easy debug flags)
Nothing fancy here... but you can now:
geronimo/start-server --profile debug
which will flip on the standard debug flags. This is done via the etc/
rc.d script with:
// If the debug profile was selected, then append some debugging flags
if (command.profiles.contains('debug')) {
command.javaFlags << '-Xdebug'
command.javaFlags << '-
Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000'
}
Maybe later we can work on making it easier for folks to change the
values w/o changing the file... but for now this will do.
--jason
[jira] Closed: (GERONIMO-3651) gshell should make it dead simple to run geronimo with remote debugging
[
https://issues.apache.org/jira/browse/GERONIMO-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GERONIMO-3651.
--
Resolution: Fixed
Fix Version/s: (was: 2.1.x)
Done... finally :-\
Nothing fancy here... but you can now:
{noformat}
geronimo/start-server --profile debug
{noformat}
which will flip on the standard debug flags. This is done via the etc/rc.d
script with:
{code}
// If the debug profile was selected, then append some debugging flags
if (command.profiles.contains('debug')) {
command.javaFlags << '-Xdebug'
command.javaFlags <<
'-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000'
}
{code}
Maybe later we can work on making it easier for folks to change the values w/o
changing the file... but for now this will do.
> gshell should make it dead simple to run geronimo with remote debugging
> ---
>
> Key: GERONIMO-3651
> URL: https://issues.apache.org/jira/browse/GERONIMO-3651
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: startup/shutdown
>Affects Versions: 2.1, 2.1.x, 2.2
>Reporter: David Jencks
>Assignee: Jason Dillon
>Priority: Blocker
> Fix For: 2.2
>
>
> we need some options for start-server so g. starts up with debugging. I
> think we should be able to set the port and suspend as persistent options in
> the environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ianal-maven-plugin
Folks, I've moved the bits of the tools-maven-plugin which we were using to verify legal files in project artifacts over to the mojo project under the ianal-maven-plugin. Testing that it works in server/trunk before I commit, but expect to see it there soon. This stuff is going to be verifying the legal muck which gets pulled in from the maven-remote-resources-plugin. Already found that the maven-rar-plugin requires hacks to make it work, but so far everything else looks happy. * * * As I have time, I am also going to be adding source-level checks to the ianal-maven-plugin to make sure headers are in order and such, but thats when I have time... Site is here (empty, pending some real docs at the moment): http://mojo.codehaus.org/ianal-maven-plugin And sources here: https://svn.codehaus.org/mojo/trunk/sandbox/ianal-maven-plugin/ Its a GMaven-based plugin of course ;-) --jason
Re: [BUILD] trunk: Failed for Revision: 650855
Sorry, missed this one...
--jason
On Apr 23, 2008, at 9:01 PM, [EMAIL PROTECTED] wrote:
Geronimo Revision: 650855 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080423/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080423/unit-test-reports
[INFO] Installing /home/geronimo/geronimo/trunk/plugins/welcome/
geronimo-welcome/target/geronimo-welcome-2.2-SNAPSHOT.war to /home/
geronimo/.m2/repository/org/apache/geronimo/plugins/geronimo-welcome/
2.2-SNAPSHOT/geronimo-welcome-2.2-SNAPSHOT.war
[INFO]
[INFO] Building Geronimo Plugins, Welcome :: Jetty
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated: /home/geronimo/geronimo/trunk/plugins/welcome/
welcome-jetty/target/resources/META-INF/plan.xml
[INFO] [car:package]
[INFO] snapshot org.apache.geronimo.plugins:geronimo-welcome:2.2-
SNAPSHOT: checking for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.plugins:geronimo-welcome:2.2-
SNAPSHOT: checking for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.plugins:geronimo-welcome:2.2-
SNAPSHOT: checking for updates from apache.snapshots
[INFO] Packaging module configuration: /home/geronimo/geronimo/trunk/
plugins/welcome/welcome-jetty/target/resources/META-INF/plan.xml
[INFO] Started deployer: org.apache.geronimo.framework/geronimo-
gbean-deployer/2.2-SNAPSHOT/car
[INFO] Started deployer: org.apache.geronimo.configs/j2ee-deployer/
2.2-SNAPSHOT/car
[INFO] Started deployer: org.apache.geronimo.configs/jetty6-deployer/
2.2-SNAPSHOT/car
[INFO] Started deployer: org.apache.geronimo.configs/jasper-deployer/
2.2-SNAPSHOT/car
[INFO] [car:prepare-metadata]
[INFO] [car:archive-car]
[INFO] Building jar: /home/geronimo/geronimo/trunk/plugins/welcome/
welcome-jetty/target/welcome-jetty-2.2-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/trunk/plugins/welcome/
welcome-jetty/target/welcome-jetty-2.2-SNAPSHOT.car to /home/
geronimo/.m2/repository/org/apache/geronimo/configs/welcome-jetty/
2.2-SNAPSHOT/welcome-jetty-2.2-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO]
[INFO] Building Geronimo Plugins, Welcome :: Tomcat
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated: /home/geronimo/geronimo/trunk/plugins/welcome/
welcome-tomcat/target/resources/META-INF/plan.xml
[INFO] [car:package]
[INFO] Packaging module configuration: /home/geronimo/geronimo/trunk/
plugins/welcome/welcome-tomcat/target/resources/META-INF/plan.xml
[INFO] Started deployer: org.apache.geronimo.framework/geronimo-
gbean-deployer/2.2-SNAPSHOT/car
[INFO] Started deployer: org.apache.geronimo.configs/j2ee-deployer/
2.2-SNAPSHOT/car
[INFO] Started deployer: org.apache.geronimo.configs/tomcat6-
deployer/2.2-SNAPSHOT/car
[INFO] Started deployer: org.apache.geronimo.configs/jasper-deployer/
2.2-SNAPSHOT/car
[INFO] [car:prepare-metadata]
[INFO] [car:archive-car]
[INFO] Building jar: /home/geronimo/geronimo/trunk/plugins/welcome/
welcome-tomcat/target/welcome-tomcat-2.2-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/trunk/plugins/welcome/
welcome-tomcat/target/welcome-tomcat-2.2-SNAPSHOT.car to /home/
geronimo/.m2/repository/org/apache/geronimo/configs/welcome-tomcat/
2.2-SNAPSHOT/welcome-tomcat-2.2-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO]
[INFO] Building Geronimo Assemblies
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/trunk/assemblies/pom.xml
to /home/geronimo/.m2/repository/org/apache/geronimo/assemblies/
assemblies/2.2-SNAPSHOT/assemblies-2.2-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo Assemblies :: Boilerplate Minimal
[INFO]
[jira] Closed: (GERONIMO-593) Make error handling in deployment plugin more user friendly
[ https://issues.apache.org/jira/browse/GERONIMO-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-593. - Resolution: Invalid Fix Version/s: (was: Wish List) Too old > Make error handling in deployment plugin more user friendly > --- > > Key: GERONIMO-593 > URL: https://issues.apache.org/jira/browse/GERONIMO-593 > Project: Geronimo > Issue Type: Improvement > Components: geronimo-maven-plugin >Affects Versions: 1.0-M3 >Reporter: John Sisson > Assignee: Jason Dillon >Priority: Minor > > E.G. for a "Connection reset" error, rather than dumping out approx 37 lines > of stack trace, just output a message identifying the operation that failed > and the cause (e.g. java.net.SocketException: Connection reset). Possibly > provide a verbose option to dump whole stack trace? > E.G. currently you get: > java.rmi.UnmarshalException: Error unmarshaling return header; nested > exception is: > java.net.SocketException: Connection reset > org.apache.geronimo.kernel.InternalKernelException: > java.rmi.UnmarshalException: Error unmarshaling return header; nested > exception is: > java.net.SocketException: Connection reset > at > org.apache.geronimo.kernel.jmx.KernelDelegate.invoke(KernelDelegate.java:232) > at > org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:92) > at > org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:71) > at java.lang.Thread.run(Thread.java:534) > Caused by: java.rmi.UnmarshalException: Error unmarshaling return header; > nested exception is: > java.net.SocketException: Connection reset > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:203) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) > at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown > Source) > at mx4j.remote.rmi.ClientInvoker.invoke(ClientInvoker.java:207) > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3973) Fail to assemble a server via gsh when Geronimo is installed in a directory with white space
[
https://issues.apache.org/jira/browse/GERONIMO-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GERONIMO-3973:
--
Assignee: (was: Jason Dillon)
Looks like this might be fixed, pending verification please... :-)
> Fail to assemble a server via gsh when Geronimo is installed in a directory
> with white space
>
>
> Key: GERONIMO-3973
> URL: https://issues.apache.org/jira/browse/GERONIMO-3973
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands
> Environment: Windows
>Reporter: YunFeng Ma
>
> Geronimo is install in directory: h:\geronimo server1\
> {noformat}
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> Server artifact name: abcd
> ERROR UnmarshalException: error unmarshalling return; nested exception is:
> java.net.MalformedURLException: no protocol:
> server1/repository/org/apache/geronimo/framework/geronimo-common/2.1.1-SNAPSHOT/geronimo-common-2.1.1-SNAPSHOT.jar
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3700) alias command fails
[ https://issues.apache.org/jira/browse/GERONIMO-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-3700. -- Resolution: Fixed Geronimo-specific GShell alias commands dropped. > alias command fails > --- > > Key: GERONIMO-3700 > URL: https://issues.apache.org/jira/browse/GERONIMO-3700 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: general >Affects Versions: 2.1, 2.1.1 >Reporter: Kevan Miller >Assignee: Jason Dillon > Fix For: 2.2 > > > Running the alias command fails with an IllegalStateException: > [EMAIL PROTECTED]:/> alias > ERROR IllegalStateException: Alias file > /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml > does not exist > Could be that Geronimo should be including this file in assemblies, or gshell > should create (if not present), or something else is wrong... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: yoko deps in repository module
So... should these be removed from the repository/pom.xml? --jason On Apr 22, 2008, at 4:04 AM, Rick McGuire wrote: Jason Dillon wrote: Why are there yoko deps listed in the repository module, but there are no artifacts for org/apache/yoko checked in there? Looks like it was just a missed update when trunk was switched back to pick up the snapshot dependency. We've been shipping with a new pinned yoko version in the repository when we've been spinning a new G. release Rick 8< org.apache.yoko yoko-core org.apache.yoko yoko-rmi-impl org.apache.yoko yoko-rmi-spec org.apache.yoko yoko-spec-corba >8 This causes the repository module build to pull them from a remote repository... which isn't really the purpose of this module at at... its only to install those artifacts which are under repository/* into the local repo cache. Anyone know whats up with this? --jason
[jira] Created: (GERONIMO-3979) Update archetypes to use new archtype-ng configuration
Update archetypes to use new archtype-ng configuration -- Key: GERONIMO-3979 URL: https://issues.apache.org/jira/browse/GERONIMO-3979 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: buildsystem Reporter: Jason Dillon Assignee: Jason Dillon -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3980) Replace maven-maven-plugin usage with shitty-maven-plugin
Replace maven-maven-plugin usage with shitty-maven-plugin - Key: GERONIMO-3980 URL: https://issues.apache.org/jira/browse/GERONIMO-3980 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: buildsystem Reporter: Jason Dillon Assignee: Jason Dillon -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
geronimo-deployment test failing on windows w/space in path
Anyone notice on windows, that geronimo-deployment tests fail when built from a path with a space? --- Test set: org.apache.geronimo.deployment.SingleFileHotDeployerTest --- Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.281 sec <<< FAILURE! testNoRedeploy (org.apache.geronimo.deployment.SingleFileHotDeployerTest) Time elapsed: 0 sec <<< FAILURE! junit.framework.AssertionFailedError: Did not expect configuration to be unloaded new/new/new/new at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.geronimo.deployment.SingleFileHotDeployerTest $ MockConfigurationManager .unloadConfiguration(SingleFileHotDeployerTest.java:368) at org .apache .geronimo .deployment.SingleFileHotDeployer.start(SingleFileHotDeployer.java:116) at org .apache .geronimo .deployment.SingleFileHotDeployer.(SingleFileHotDeployer.java:73) at org .apache .geronimo .deployment .SingleFileHotDeployerTest .testNoRedeploy(SingleFileHotDeployerTest.java:226) Using path: c:\ws\ser ver While this path works fine: c:\ws\server :-( --jason
Why 2 versions of tomcat/catalina stuff in repository?
--jason
yoko deps in repository module
Why are there yoko deps listed in the repository module, but there are no artifacts for org/apache/yoko checked in there? 8< org.apache.yoko yoko-core org.apache.yoko yoko-rmi-impl org.apache.yoko yoko-rmi-spec org.apache.yoko yoko-spec-corba >8 This causes the repository module build to pull them from a remote repository... which isn't really the purpose of this module at at... its only to install those artifacts which are under repository/* into the local repo cache. Anyone know whats up with this? --jason
Re: svn commit: r600872 - in /geronimo/server/trunk: ./ assemblies/geronimo-boilerplate-minimal/ assemblies/geronimo-boilerplate-minimal/src/main/assembly/ assemblies/geronimo-boilerplate-minimal/src/
Hey, what exactly does this remote-server-control command intend to solve? This got committed at the same time as your aliasing work... which sorry to say I'm about to nuke. I wish you had mentioned you wanted to work on alias stuff and I would have given you a nudge on how I was planning on implementing it. The idea was to follow how the alias stuff works for the Groovy Shell (aka. groovysh), which closely resembles how aliasing works for /bin/bash. To do so means adding a few hooks into the GShell core and adding alias, unalias commands to builtins. * * * Anyways, I comprehend what the alias bits are intended for, but I'm lost for what the remote-server-control bits are for completely. I'm a bit weary about adding some of these commands to the distribution w/o adequate testing and documentation... or use-cases. Perhaps if you want to keep this around we can move it to a sandbox module, where we can test out new commands, then once they are rocksolid move them over? --jason On Tue, Dec 4, 2007 at 5:46 PM, <[EMAIL PROTECTED]> wrote: > Author: gdamour > Date: Tue Dec 4 02:46:27 2007 > New Revision: 600872 > > URL: http://svn.apache.org/viewvc?rev=600872&view=rev > Log: > Add a couple of gshell commands to simplify the remote control of servers. > The commands being added are: > * alias: used to alias a commond along with some options and arguments. > etc/layout.xml provides a first aliasing mechanism: a hierarchical name is > mapped to a command. alias suplements this first aliasing mechanism with the > ability to alias a command along with its typical options and arguments. > * unalias: to remove an alias > * execute-alias: to execute an alias > * remote/rsh to start an rsh client > * remote/rsh-server to start an rsh-server > * remote-control/server-control to control a server > > Samples for the aliasing commands: > // create the alias 'st' for the quoted command > > alias st 'geronimo/start-server -G server.name=yellow -D property=value' > // execute the alias 'st'. This executes the command in quote above > > excute-alias st > // display defined aliases > > alias > // remove the alias 'st' > > unalias st > > Samples for the remote server control commands: > // start an rsh-server: > > remote/rsh-server tcp://localhost: > // remote 'start' the server 'defaultServer' > > remote-control/server-control start defaultServer > // remote 'stop' the server 'defaultServer' > > remote-control/server-control stop defaultServer > > All the commands are implemented in Groovy. XML manipulations are done via > XmlSlurpers. > > Aliases are stored in a configuration file located by default in > etc/aliases.xml > > Server configurations, used by the remote control command, are stored in a > configuration file located by default in > etc/server-configuration.xml > > New JARs are being added to lib/gshell for the support of the rsh bits. > > Added: > > geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/src/main/underlay/etc/aliases.xml > > geronimo/server/trunk/assemblies/geronimo-boilerplate-minimal/src/main/underlay/etc/server-configuration.xml > > geronimo/server/trunk/framework/modules/geronimo-commands/src/main/groovy/org/apache/geronimo/commands/AbstractAliasCommand.groovy > > geronimo/server/trunk/framework/modules/geronimo-commands/src/main/groovy/org/apache/geronimo/commands/AliasCommand.groovy > > geronimo/server/trunk/framework/modules/geronimo-commands/src/main/groovy/org/apache/geronimo/commands/ExecuteAliasCommand.groovy > > geronimo/server/trunk/framework/modules/geronimo-commands/src/main/groovy/org/apache/geronimo/commands/RemoteServerControlCommand.groovy > > geronimo/server/trunk/framework/modules/geronimo-commands/src/main/groovy/org/apache/geronimo/commands/UnaliasCommand.groovy > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/ > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/ > > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/org/ > > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/org/apache/ > > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/org/apache/geronimo/ > > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/org/apache/geronimo/commands/ > > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/org/apache/geronimo/commands/AliasCommandTest.groovy > > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/org/apache/geronimo/commands/ExecuteAliasCommandTest.groovy > > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/org/apache/geronimo/commands/GroovyTestSupport.groovy > > geronimo/server/trunk/framework/modules/geronimo-commands/src/test/groovy/org/apache/geronimo/commands/RemoteServerControlCommandTest.groovy > > geronim
[jira] Commented: (GERONIMO-3700) alias command fails
[ https://issues.apache.org/jira/browse/GERONIMO-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590985#action_12590985 ] Jason Dillon commented on GERONIMO-3700: I think I'm going to nuke the alias command... this isn't how I had intended to allow users to create aliases, and well since it does not work its IMO more harm than good. > alias command fails > --- > > Key: GERONIMO-3700 > URL: https://issues.apache.org/jira/browse/GERONIMO-3700 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: general >Affects Versions: 2.1, 2.1.1 > Reporter: Kevan Miller >Assignee: Jason Dillon > Fix For: 2.2 > > > Running the alias command fails with an IllegalStateException: > [EMAIL PROTECTED]:/> alias > ERROR IllegalStateException: Alias file > /Users/kevan/geronimo/server/trunk/assemblies/geronimo-framework/target/geronimo-framework-2.1-SNAPSHOT/bin/etc/aliases.xml > does not exist > Could be that Geronimo should be including this file in assemblies, or gshell > should create (if not present), or something else is wrong... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GSHELL-109) GShell fails to retrieve the previous commands if the command is too long
[ https://issues.apache.org/jira/browse/GSHELL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GSHELL-109. --- Resolution: Invalid Fix Version/s: (was: 1.0-alpha-2) Based on its content, I do not believe this issue to be valid. > GShell fails to retrieve the previous commands if the command is too long > - > > Key: GSHELL-109 > URL: https://issues.apache.org/jira/browse/GSHELL-109 > Project: GShell > Issue Type: Bug > Security Level: public(Regular issues) > Components: CLI >Affects Versions: 1.0-alpha-2 > Environment: Windows >Reporter: YunFeng Ma >Assignee: Jason Dillon > > Run the following command in GShell: > -- > [EMAIL PROTECTED]:/> deploy/deploy H:/FTP_ROOT/Build/Pre-Version/sample_v > 2.0.0.1_GM/200711082220GM/samples-2.0.0.1/applications/cviewer/target/cvie > wer-2.0.0.1.war > -- > Note that the command is broken into three lines, then using the "up" button > to retrieve the previous commands > and get the following result: > -- > [EMAIL PROTECTED]:/> deploy/deploy H:/FTP_ROOT/Build/Pre-Version/sample_V > 2.0.0.1_GM/200711082220GM/samples-2.0.0.1/applications/cviewer/target/cvie > quit > -- -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3424) Fatal error in geronimo-service-builder during copy-xmlbeans-schemas on windows
[
https://issues.apache.org/jira/browse/GERONIMO-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GERONIMO-3424.
--
Resolution: Fixed
Fix Version/s: 2.2
> Fatal error in geronimo-service-builder during copy-xmlbeans-schemas on
> windows
> ---
>
> Key: GERONIMO-3424
> URL: https://issues.apache.org/jira/browse/GERONIMO-3424
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: buildsystem
>Affects Versions: 2.1
> Environment: windows
>Reporter: Anita Kulshreshtha
>Assignee: Jason Dillon
>Priority: Minor
> Fix For: 2.2
>
>
>The build for trunk rev 567880 is failing in geronimo-service-builder.
> This may be a windows only problem. The module builds fine after commenting
> out the copy-xmlbeans-schemas part.
> .
> [INFO] [enforcer:enforce {execution: default}]
> [INFO] [xmlbeans:xmlbeans {execution: default}]
> Time to build schema type system: 1.016 seconds
> Time to generate code: 0.422 seconds
> Time to compile code: 2.625 seconds
> [INFO] [tools:copy-legal-files {execution: install-legal-files}]
> [INFO] Created dir:
> C:\anita\geronimo\g2.0\modules\geronimo-service-builder\targ
> et\classes\META-INF
> [INFO] Copying 2 files to
> C:\anita\geronimo\g2.0\modules\geronimo-service-builde
> r\target\classes\META-INF
> [INFO] [buildsupport:copy-xmlbeans-schemas {execution: default}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> Illegal character in path at index 18: file:/C:/Documents and
> Settings/Anita/.m2
> /repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> [INFO]
>
> [INFO] Trace
> java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:842)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
> at
> org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:11
> 9)
> at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
> at org.apache.tools.ant.Project.setAntLib(Project.java:313)
> at org.apache.tools.ant.Project.initProperties(Project.java:309)
> at org.apache.tools.ant.Project.init(Project.java:295)
> at
> org.codehaus.mojo.groovy.util.AntBuilder.createProject(AntBuilder.jav
> a:65)
> at org.codehaus.mojo.groovy.util.AntBuilder.(AntBuilder.java:39)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
> orAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
> onstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at
> org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaC
> lassHelper.java:563)
> at
> groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1864
> )
> at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:804)
> at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:734)
> at
> org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:
> 143)
> at
> org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(Invoker
> Helper.java:114)
> at
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBy
> tecodeAdapter.java:214)
> at
> org.codehaus.mojo.groovy.GroovyMojoSupport.getAnt(GroovyMojoSupport.g
> roovy:42)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at
[jira] Closed: (GERONIMO-3858) start-server.bat fails to start server if there is a space in the path
[ https://issues.apache.org/jira/browse/GERONIMO-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-3858. -- Resolution: Fixed Fix Version/s: 2.2 > start-server.bat fails to start server if there is a space in the path > -- > > Key: GERONIMO-3858 > URL: https://issues.apache.org/jira/browse/GERONIMO-3858 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: startup/shutdown >Affects Versions: 2.1, 2.1.1, 2.2 > Environment: Windows XP >Reporter: YunFeng Ma >Assignee: Jason Dillon > Fix For: 2.2 > > > start-server.bat fails to start server if there is a space in the install > path, but startup.bat works fine. Looks like it's an Ant bug. > H:\myf\Apache Geronimo\bin>start-server.bat > --- > constituent[0]: file:/H:/myf/Apache Geronimo/etc/ > constituent[1]: file:/H:/myf/Apache > Geronimo/lib/gshell/geronimo-commands-2.1-SN > APSHOT.jar > constituent[2]: file:/H:/myf/Apache > Geronimo/repository/org/apache/ant/ant/1.7.0 > /ant-1.7.0.jar > constituent[3]: file:/H:/myf/Apache > Geronimo/repository/org/apache/ant/ant-launc > her/1.7.0/ant-launcher-1.7.0.jar > constituent[4]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/gshe > ll/gshell-cli/1.0-alpha-1-SNAPSHOT/gshell-cli-1.0-alpha-1-SNAPSHOT.jar > constituent[5]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/gshe > ll/gshell-embeddable/1.0-alpha-1-SNAPSHOT/gshell-embeddable-1.0-alpha-1-SNAPSHOT > .jar > constituent[6]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/gshe > ll/remote/gshell-remote-client/1.0-alpha-1-SNAPSHOT/gshell-remote-client-1.0-alp > ha-1-SNAPSHOT.jar > constituent[7]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/gshe > ll/remote/gshell-remote-common/1.0-alpha-1-SNAPSHOT/gshell-remote-common-1.0-alp > ha-1-SNAPSHOT.jar > constituent[8]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/gshe > ll/remote/gshell-remote-server/1.0-alpha-1-SNAPSHOT/gshell-remote-server-1.0-alp > ha-1-SNAPSHOT.jar > constituent[9]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/gshe > ll/gshell-whisper/1.0-alpha-1-SNAPSHOT/gshell-whisper-1.0-alpha-1-SNAPSHOT.jar > constituent[10]: file:/H:/myf/Apache > Geronimo/repository/org/apache/mina/mina-co > re/1.1.2/mina-core-1.1.2.jar > constituent[11]: file:/H:/myf/Apache > Geronimo/repository/org/apache/mina/mina-fi > lter-ssl/1.1.2/mina-filter-ssl-1.1.2.jar > constituent[12]: file:/H:/myf/Apache > Geronimo/repository/org/codehaus/groovy/gro > ovy-all/1.1-rc-1/groovy-all-1.1-rc-1.jar > constituent[13]: file:/H:/myf/Apache > Geronimo/repository/org/slf4j/slf4j-log4j12 > /1.4.3/slf4j-log4j12-1.4.3.jar > constituent[14]: file:/H:/myf/Apache > Geronimo/repository/org/slf4j/jcl104-over-s > lf4j/1.4.3/jcl104-over-slf4j-1.4.3.jar > constituent[15]: file:/H:/myf/Apache > Geronimo/lib/geronimo-kernel-2.1-SNAPSHOT.j > ar > constituent[16]: file:/H:/myf/Apache Geronimo/lib/log4j-1.2.14.jar > constituent[17]: file:/H:/myf/Apache Geronimo/lib/cglib-nodep-2.1_3.jar > constituent[18]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/spe > cs/geronimo-javaee-deployment_1.1MR3_spec/1.0/geronimo-javaee-deployment_1.1MR3_ > spec-1.0.jar > constituent[19]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/mod > ules/geronimo-cli/2.1-SNAPSHOT/geronimo-cli-2.1-SNAPSHOT.jar > constituent[20]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/mod > ules/geronimo-deploy-config/2.1-SNAPSHOT/geronimo-deploy-config-2.1-SNAPSHOT.jar > constituent[21]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/mod > ules/geronimo-deploy-jsr88/2.1-SNAPSHOT/geronimo-deploy-jsr88-2.1-SNAPSHOT.jar > constituent[22]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/mod > ules/geronimo-deploy-tool/2.1-SNAPSHOT/geronimo-deploy-tool-2.1-SNAPSHOT.jar > constituent[23]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/mod > ules/geronimo-system/2.1-SNAPSHOT/geronimo-system-2.1-SNAPSHOT.jar > constituent[24]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/mod > ules/geronimo-plugin/2.1-SNAPSHOT/geronimo-plugin-2.1-SNAPSHOT.jar > constituent[25]: file:/H:/myf/Apache > Geronimo/repository/org/apache/geronimo/mod > ules/geronimo-common/2.1-SNAPSHOT/geron
[jira] Closed: (GERONIMO-3977) Use gmaven's ant 1.7.0 libraries which are compatible with Groovy and Windows
[ https://issues.apache.org/jira/browse/GERONIMO-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-3977. -- Resolution: Fixed > Use gmaven's ant 1.7.0 libraries which are compatible with Groovy and Windows > - > > Key: GERONIMO-3977 > URL: https://issues.apache.org/jira/browse/GERONIMO-3977 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Jason Dillon >Assignee: Jason Dillon >Priority: Critical > Fix For: 2.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3410) jspc-maven-plugin-2.0-alpha-1 is causing build failures on Windows
[
https://issues.apache.org/jira/browse/GERONIMO-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590933#action_12590933
]
Jason Dillon commented on GERONIMO-3410:
The latest version (2.0-alpha-2-SNAPSHOT) of the jspc-maven-plugin, should
resolve this problem.
> jspc-maven-plugin-2.0-alpha-1 is causing build failures on Windows
> --
>
> Key: GERONIMO-3410
> URL: https://issues.apache.org/jira/browse/GERONIMO-3410
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: buildsystem
>Affects Versions: 2.0, 2.0.x
> Environment: WinXP
>Reporter: Donald Woods
>Assignee: Donald Woods
>Priority: Critical
> Fix For: 2.0.1
>
>
> http://repository.codehaus.org/org/codehaus/mojo/jspc/jspc-compiler
> -tomcat6/2.0-alpha-1/jspc-compiler-tomcat6-2.0-alpha-1.jar
> 4K downloaded
> [INFO] [jspc:compile {execution: default}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> Illegal character in path at index 18: file:/C:/Documents and
> Settings/Anita/.m2
> /repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> [INFO]
>
> [INFO] Trace
> java.lang.IllegalArgumentException
>at java.net.URI.create(URI.java:842)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> The jspc-maven-plugin-2.0-alpha-1.jar is to blame. I still had a copy of the
> last alpha-1-SNAPSHOT laying around
> (jspc-maven-plugin-2.0-alpha-1-20070806.170854-1.jar) and copied it over the
> released alpha-1.jar from 8/8 and my builds starting working again on
> WinXP
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3973) Fail to assemble a server via gsh when Geronimo is installed in a directory with white space
[
https://issues.apache.org/jira/browse/GERONIMO-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590909#action_12590909
]
Jason Dillon commented on GERONIMO-3973:
Can you please post the full output from {{gsh --debug}} with the
{{deploy/assembly}} command?
> Fail to assemble a server via gsh when Geronimo is installed in a directory
> with white space
>
>
> Key: GERONIMO-3973
> URL: https://issues.apache.org/jira/browse/GERONIMO-3973
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands
> Environment: Windows
>Reporter: YunFeng Ma
>Assignee: Jason Dillon
>
> Geronimo is install in directory: h:\geronimo server1\
> {noformat}
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> Server artifact name: abcd
> ERROR UnmarshalException: error unmarshalling return; nested exception is:
> java.net.MalformedURLException: no protocol:
> server1/repository/org/apache/geronimo/framework/geronimo-common/2.1.1-SNAPSHOT/geronimo-common-2.1.1-SNAPSHOT.jar
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3973) Fail to assemble a server via gsh when Geronimo is installed in a directory with white space
[
https://issues.apache.org/jira/browse/GERONIMO-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590908#action_12590908
]
Jason Dillon commented on GERONIMO-3973:
This issue may depend on GERONIMO-3977, not sure yet. Might just need a
toURI().toURL()
> Fail to assemble a server via gsh when Geronimo is installed in a directory
> with white space
>
>
> Key: GERONIMO-3973
> URL: https://issues.apache.org/jira/browse/GERONIMO-3973
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands
> Environment: Windows
>Reporter: YunFeng Ma
>Assignee: Jason Dillon
>
> Geronimo is install in directory: h:\geronimo server1\
> {noformat}
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> Server artifact name: abcd
> ERROR UnmarshalException: error unmarshalling return; nested exception is:
> java.net.MalformedURLException: no protocol:
> server1/repository/org/apache/geronimo/framework/geronimo-common/2.1.1-SNAPSHOT/geronimo-common-2.1.1-SNAPSHOT.jar
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: What is the master-* cluster-* repository stuff?
On Apr 21, 2008, at 6:28 PM, Gianny Damour wrote: Hello Jason, These two folders are used by the farming feature. They are the MasterConfigurationStore and ClusterStore repositories respectively (see http://cwiki.apache.org/GMOxDOC21/farming.html for description of these two repos.) If need be, we can easily move them. Is the following prettier? Within the root install: farming | +-- master-repository | +-- cluster-repository I think that is better :-) --jason
[jira] Created: (GERONIMO-3977) Use gmaven's ant 1.7.0 libraries which are compatible with Groovy and Windows
Use gmaven's ant 1.7.0 libraries which are compatible with Groovy and Windows - Key: GERONIMO-3977 URL: https://issues.apache.org/jira/browse/GERONIMO-3977 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Reporter: Jason Dillon Assignee: Jason Dillon Priority: Critical Fix For: 2.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2582) Update Commons Logging to Version 1.1
[ https://issues.apache.org/jira/browse/GERONIMO-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-2582. -- Resolution: Duplicate > Update Commons Logging to Version 1.1 > - > > Key: GERONIMO-2582 > URL: https://issues.apache.org/jira/browse/GERONIMO-2582 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: Logging >Reporter: Matt Hogstrom > Assignee: Jason Dillon > > Update o.a.g from Commons-logging from 1.0.4 to 1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-1277) Change group-id to org.apache.geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-1277. -- Resolution: Invalid Fix Version/s: (was: Verification Required) Too old > Change group-id to org.apache.geronimo > -- > > Key: GERONIMO-1277 > URL: https://issues.apache.org/jira/browse/GERONIMO-1277 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 1.0-M5, Verification Required >Reporter: Dain Sundstrom >Assignee: Jason Dillon >Priority: Blocker > > We need to change our group-id to org.apache.geronimo before 1.0 comes out, > or else everyone's server will break when we do switch. We must make this > switch when we convert to maven 2, so it is best to do it now. > I will do this tomorrow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3961) Upgrade to use the latest Groovy 1.5.x release
[ https://issues.apache.org/jira/browse/GERONIMO-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon closed GERONIMO-3961. -- Resolution: Fixed Fix Version/s: (was: 2.1.x) > Upgrade to use the latest Groovy 1.5.x release > -- > > Key: GERONIMO-3961 > URL: https://issues.apache.org/jira/browse/GERONIMO-3961 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 2.1.x, 2.2 >Reporter: Donald Woods >Assignee: Jason Dillon > Fix For: 2.2 > > > It seems that we used an old groupId for the groovy-all GShell depend. > The latest groovy releases (1.1-1.5.5) were published using a new groupId - >org.codehaus.groovy > and can be found under - >http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/ > We should upgrade to a 1.5.x version of groovy, so we are current with their > releases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3961) Upgrade to use the latest Groovy 1.5.x release
[ https://issues.apache.org/jira/browse/GERONIMO-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590887#action_12590887 ] Jason Dillon commented on GERONIMO-3961: I can't see where the old groovy:groovy-all was being used, except that it was stuffed into the repository/* I've dropped it, and have upgrade server/trunk to use the latest gmaven code for maven+groovy integration, which uses Groovy 1.5.4. > Upgrade to use the latest Groovy 1.5.x release > -- > > Key: GERONIMO-3961 > URL: https://issues.apache.org/jira/browse/GERONIMO-3961 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 2.1.x, 2.2 > Reporter: Donald Woods >Assignee: Jason Dillon > Fix For: 2.1.x, 2.2 > > > It seems that we used an old groupId for the groovy-all GShell depend. > The latest groovy releases (1.1-1.5.5) were published using a new groupId - >org.codehaus.groovy > and can be found under - >http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/ > We should upgrade to a 1.5.x version of groovy, so we are current with their > releases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3961) Upgrade to use the latest Groovy 1.5.x release
[ https://issues.apache.org/jira/browse/GERONIMO-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GERONIMO-3961: --- Summary: Upgrade to use the latest Groovy 1.5.x release (was: Upgrade GShell to use the latest Groovy 1.5.x release) > Upgrade to use the latest Groovy 1.5.x release > -- > > Key: GERONIMO-3961 > URL: https://issues.apache.org/jira/browse/GERONIMO-3961 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 2.1.x, 2.2 >Reporter: Donald Woods >Assignee: Jason Dillon > Fix For: 2.1.x, 2.2 > > > It seems that we used an old groupId for the groovy-all GShell depend. > The latest groovy releases (1.1-1.5.5) were published using a new groupId - >org.codehaus.groovy > and can be found under - >http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/ > We should upgrade to a 1.5.x version of groovy, so we are current with their > releases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
What is the master-* cluster-* repository stuff?
Seems very ugly to have these at the top-level... :-( --jason
[jira] Commented: (GSHELL-109) GShell fails to retrieve the previous commands if the command is too long
[
https://issues.apache.org/jira/browse/GSHELL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590871#action_12590871
]
Jason Dillon commented on GSHELL-109:
-
For example, this is what you entered in the issue:
{noformat}
[EMAIL PROTECTED]:/> deploy/deploy H:/FTP_ROOT/Build/Pre-Version/sample_v
2.0.0.1_GM/200711082220GM/samples-2.0.0.1/applications/cviewer/target/cvie
wer-2.0.0.1.war
{noformat}
Which is 3 lines. If it was 1 line it would look like:
{noformat}
[EMAIL PROTECTED]:/> deploy/deploy
H:/FTP_ROOT/Build/Pre-Version/sample_v2.0.0.1_GM/200711082220GM/samples-2.0.0.1/applications/cviewer/target/cviewer-2.0.0.1.war
{noformat}
> GShell fails to retrieve the previous commands if the command is too long
> -
>
> Key: GSHELL-109
> URL: https://issues.apache.org/jira/browse/GSHELL-109
> Project: GShell
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CLI
>Affects Versions: 1.0-alpha-2
> Environment: Windows
> Reporter: YunFeng Ma
>Assignee: Jason Dillon
> Fix For: 1.0-alpha-2
>
>
> Run the following command in GShell:
> --
> [EMAIL PROTECTED]:/> deploy/deploy H:/FTP_ROOT/Build/Pre-Version/sample_v
> 2.0.0.1_GM/200711082220GM/samples-2.0.0.1/applications/cviewer/target/cvie
> wer-2.0.0.1.war
> --
> Note that the command is broken into three lines, then using the "up" button
> to retrieve the previous commands
> and get the following result:
> --
> [EMAIL PROTECTED]:/> deploy/deploy H:/FTP_ROOT/Build/Pre-Version/sample_V
> 2.0.0.1_GM/200711082220GM/samples-2.0.0.1/applications/cviewer/target/cvie
> quit
> --
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-109) GShell fails to retrieve the previous commands if the command is too long
[ https://issues.apache.org/jira/browse/GSHELL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590870#action_12590870 ] Jason Dillon commented on GSHELL-109: - >From what it looks like you are pasting in 3 lines, so sure, the completion >returns them as separate lines. You should update your shell/terminals >configuration so that when you copy/paste lines which are long that they don't >softwrap them for you. > GShell fails to retrieve the previous commands if the command is too long > - > > Key: GSHELL-109 > URL: https://issues.apache.org/jira/browse/GSHELL-109 > Project: GShell > Issue Type: Bug > Security Level: public(Regular issues) > Components: CLI >Affects Versions: 1.0-alpha-2 > Environment: Windows > Reporter: YunFeng Ma >Assignee: Jason Dillon > Fix For: 1.0-alpha-2 > > > Run the following command in GShell: > -- > [EMAIL PROTECTED]:/> deploy/deploy H:/FTP_ROOT/Build/Pre-Version/sample_v > 2.0.0.1_GM/200711082220GM/samples-2.0.0.1/applications/cviewer/target/cvie > wer-2.0.0.1.war > -- > Note that the command is broken into three lines, then using the "up" button > to retrieve the previous commands > and get the following result: > -- > [EMAIL PROTECTED]:/> deploy/deploy H:/FTP_ROOT/Build/Pre-Version/sample_V > 2.0.0.1_GM/200711082220GM/samples-2.0.0.1/applications/cviewer/target/cvie > quit > -- -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3973) Fail to assemble a server via gsh when Geronimo is installed in a directory with white space
[
https://issues.apache.org/jira/browse/GERONIMO-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GERONIMO-3973:
---
Description:
Geronimo is install in directory: h:\geronimo server1\
{noformat}
[EMAIL PROTECTED]:/> deploy/assemble
Listing configurations from Geronimo server
Connecting to Geronimo server: localhost:1099
Username: system
Password: ***
Connection established
Server artifact name: abcd
ERROR UnmarshalException: error unmarshalling return; nested exception is:
java.net.MalformedURLException: no protocol:
server1/repository/org/apache/geronimo/framework/geronimo-common/2.1.1-SNAPSHOT/geronimo-common-2.1.1-SNAPSHOT.jar
{noformat}
was:
Geronimo is install in directory: h:\geronimo server1\
[EMAIL PROTECTED]:/> deploy/assemble
Listing configurations from Geronimo server
Connecting to Geronimo server: localhost:1099
Username: system
Password: ***
Connection established
Server artifact name: abcd
ERROR UnmarshalException: error unmarshalling return; nested exception is:
java.net.MalformedURLException: no protocol: server1/repository/org/apac
he/geronimo/framework/geronimo-common/2.1.1-SNAPSHOT/geronimo-common-2.1.1-SNAPS
HOT.jar
> Fail to assemble a server via gsh when Geronimo is installed in a directory
> with white space
>
>
> Key: GERONIMO-3973
> URL: https://issues.apache.org/jira/browse/GERONIMO-3973
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands
> Environment: Windows
>Reporter: YunFeng Ma
>Assignee: Jason Dillon
>
> Geronimo is install in directory: h:\geronimo server1\
> {noformat}
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> Server artifact name: abcd
> ERROR UnmarshalException: error unmarshalling return; nested exception is:
> java.net.MalformedURLException: no protocol:
> server1/repository/org/apache/geronimo/framework/geronimo-common/2.1.1-SNAPSHOT/geronimo-common-2.1.1-SNAPSHOT.jar
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3974) Shutdown exceptions even for a clean Geronimo
[
https://issues.apache.org/jira/browse/GERONIMO-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590868#action_12590868
]
Jason Dillon commented on GERONIMO-3974:
It would really be nice if you post stack traces or raw output surrounded by a
\{noformat\} macro and don't paste data which is already wrapped... ;-)
> Shutdown exceptions even for a clean Geronimo
> -
>
> Key: GERONIMO-3974
> URL: https://issues.apache.org/jira/browse/GERONIMO-3974
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: connector
>Affects Versions: 2.1.1
> Environment: Windows
>Reporter: YunFeng Ma
> Fix For: 2.1.1
>
>
> Shutdown a clean Geronimo server, get the following exceptions:
> Geronimo Application Server started
> 16:43:00,843 WARN [GeronimoConnectionEventListener] connectionErrorOccurred
> cal
> led with null
> java.sql.SQLException: No current connection.
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknow
> n Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.checkIfClosed(Unknown
> Sour
> ce)
> at org.apache.derby.impl.jdbc.EmbedConnection.getAutoCommit(Unknown
> Sour
> ce)
> at
> org.apache.derby.iapi.jdbc.BrokeredConnection.getAutoCommit(Unknown S
> ource)
> at
> org.tranql.connector.jdbc.ConnectionHandle.rollback(ConnectionHandle.
> java:129)
> at
> org.apache.activemq.store.jdbc.DefaultDatabaseLocker.stop(DefaultData
> baseLocker.java:78)
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.stop(JDBCPersis
> tenceAdapter.java:202)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter.stop(Jour
> nalPersistenceAdapter.java:254)
> at
> org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:42)
> at
> org.apache.activemq.broker.BrokerService.stop(BrokerService.java:443)
> at
> org.apache.geronimo.activemq.BrokerServiceGBeanImpl.doStop(BrokerServ
> iceGBeanImpl.java:119)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBean
> Instance.java:1161)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(
> GBeanInstanceState.java:339)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan
> ceState.java:188)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja
> va:563)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja
> va:423)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan
> ceState.java:180)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja
> va:563)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja
> va:423)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan
> ceState.java:180)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja
> va:563)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja
> va:423)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan
> ceState.java:180)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja
> va:563)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja
> va:423)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan
> ceState.java:180)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja
> va:563)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja
> va:423)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstan
> ceState.java:180)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.ja
> va:563)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.ja
> va:423)
> at
> org.apache.geronimo.kernel.config.KernelConfigurationManager$Shutdown
> Hook.run(KernelConfigurationManager
[jira] Updated: (GERONIMO-3973) Fail to assemble a server via gsh when Geronimo is installed in a directory with white space
[ https://issues.apache.org/jira/browse/GERONIMO-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GERONIMO-3973: --- Component/s: commands > Fail to assemble a server via gsh when Geronimo is installed in a directory > with white space > > > Key: GERONIMO-3973 > URL: https://issues.apache.org/jira/browse/GERONIMO-3973 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: commands > Environment: Windows >Reporter: YunFeng Ma >Assignee: Jason Dillon > > Geronimo is install in directory: h:\geronimo server1\ > [EMAIL PROTECTED]:/> deploy/assemble > Listing configurations from Geronimo server > Connecting to Geronimo server: localhost:1099 > Username: system > Password: *** > Connection established > Server artifact name: abcd > ERROR UnmarshalException: error unmarshalling return; nested exception is: > java.net.MalformedURLException: no protocol: > server1/repository/org/apac > he/geronimo/framework/geronimo-common/2.1.1-SNAPSHOT/geronimo-common-2.1.1-SNAPS > HOT.jar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GSHELL-108) Fail to assemble a server via gsh when Geronimo is installed in a directory with white space
[
https://issues.apache.org/jira/browse/GSHELL-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590867#action_12590867
]
Jason Dillon commented on GSHELL-108:
-
This is not an issue for GSHELL, but for GERONIMO's implementation of its
{{deploy/assembly}} command. Please create issues in the correct project in
the future.
> Fail to assemble a server via gsh when Geronimo is installed in a directory
> with white space
>
>
> Key: GSHELL-108
> URL: https://issues.apache.org/jira/browse/GSHELL-108
> Project: GShell
> Issue Type: Bug
> Security Level: public(Regular issues)
> Environment: Windows
>Reporter: YunFeng Ma
>Assignee: Jason Dillon
>
> Geronimo is install in directory: h:\geronimo server1\
> [EMAIL PROTECTED]:/> deploy/assemble
> Listing configurations from Geronimo server
> Connecting to Geronimo server: localhost:1099
> Username: system
> Password: ***
> Connection established
> Server artifact name: abcd
> ERROR UnmarshalException: error unmarshalling return; nested exception is:
> java.net.MalformedURLException: no protocol:
> server1/repository/org/apac
> he/geronimo/framework/geronimo-common/2.1.1-SNAPSHOT/geronimo-common-2.1.1-SNAPS
> HOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3961) Upgrade GShell to use the latest Groovy 1.5.x release
[ https://issues.apache.org/jira/browse/GERONIMO-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590866#action_12590866 ] Jason Dillon commented on GERONIMO-3961: I'm not actually sure that the old groovy:groovy-all dependency comes from anything gshell related, but I'm looking... > Upgrade GShell to use the latest Groovy 1.5.x release > - > > Key: GERONIMO-3961 > URL: https://issues.apache.org/jira/browse/GERONIMO-3961 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 2.1.x, 2.2 > Reporter: Donald Woods >Assignee: Jason Dillon > Fix For: 2.1.x, 2.2 > > > It seems that we used an old groupId for the groovy-all GShell depend. > The latest groovy releases (1.1-1.5.5) were published using a new groupId - >org.codehaus.groovy > and can be found under - >http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/ > We should upgrade to a 1.5.x version of groovy, so we are current with their > releases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r649685 - /geronimo/server/trunk/pom.xml
This is not a valid pom configuration... have not looked at the
branches, but this certainly won't work. I'm going to fix this one,
but you should check that other poms you've updated with this change
actually *build* ;-)
--jason
On Sat, Apr 19, 2008 at 3:34 AM, <[EMAIL PROTECTED]> wrote:
> Author: jbohn
> Date: Fri Apr 18 13:34:39 2008
> New Revision: 649685
>
> URL: http://svn.apache.org/viewvc?rev=649685&view=rev
> Log:
> Enable release deployment - mirrors r620244 from branches/2.1.0
>
> Modified:
> geronimo/server/trunk/pom.xml
>
> Modified: geronimo/server/trunk/pom.xml
> URL:
> http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=649685&r1=649684&r2=649685&view=diff
>
> ==
> --- geronimo/server/trunk/pom.xml (original)
> +++ geronimo/server/trunk/pom.xml Fri Apr 18 13:34:39 2008
> @@ -2134,6 +2134,39 @@
> 1.0-alpha-1
>
>
> +
> +
> +org.apache.maven.plugins
> +maven-deploy-plugin
> +2.3
> +true
> +
> +true
> +
> ${deploy.altRepository}
> +
> +
> +
> +
> +org.apache.maven.plugins
> +maven-gpg-plugin
> +1.0-alpha-3
> +
> +${gpg.passphrase}
> +
> +
> +
> +
> +sign
> +
> +
> +
> +
> +
> +
> +org.apache.maven.plugins
> +maven-release-plugin
> +2.0-beta-6
> +
>
>
>
>
>
>
Fwd: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync
Getting a fairly constant spam from the website sync script... --jason Begin forwarded message: From: [EMAIL PROTECTED] (Cron Daemon) Date: April 18, 2008 7:19:18 PM GMT+07:00 To: [EMAIL PROTECTED] Subject: Cron <[EMAIL PROTECTED]> /home/jdillon/ws/site/bin/sync chmod: /www/geronimo.apache.org/xbean/xbean-finder/META-INF/ MANIFEST.MF: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/META-INF/LICENSE: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/META-INF/NOTICE: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/META-INF: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.Annotatable.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.AnnotationInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.ClassInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.FieldInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.Info.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.InfoBuildingVisitor.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.MethodInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ClassFinder.PackageInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/ResourceFinder.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use/UrlSet.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/class-use: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.Annotatable.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.AnnotationInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.ClassInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.FieldInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.Info.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.InfoBuildingVisitor.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.MethodInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ClassFinder.PackageInfo.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/package-frame.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/package-summary.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/package-tree.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/package-use.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/ResourceFinder.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder/UrlSet.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean/ finder: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache/xbean: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org/apache: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/org: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/resources/ inherit.gif: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/resources: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/src-html/org/ apache/xbean/finder/ClassFinder.Annotatable.html: Operation not permitted chmod: /www/geronimo.apache.org/xbean/xbean-finder/src-html/org/ apache/xbean/finder/ClassFinder.AnnotationInfo.html: Operation not permitt
[jira] Assigned: (GERONIMO-3961) Upgrade GShell to use the latest Groovy 1.5.x release
[ https://issues.apache.org/jira/browse/GERONIMO-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon reassigned GERONIMO-3961: -- Assignee: Jason Dillon > Upgrade GShell to use the latest Groovy 1.5.x release > - > > Key: GERONIMO-3961 > URL: https://issues.apache.org/jira/browse/GERONIMO-3961 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: dependencies >Affects Versions: 2.1.x, 2.2 >Reporter: Donald Woods >Assignee: Jason Dillon > Fix For: 2.1.x, 2.2 > > > It seems that we used an old groupId for the groovy-all GShell depend. > The latest groovy releases (1.1-1.5.5) were published using a new groupId - >org.codehaus.groovy > and can be found under - >http://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/ > We should upgrade to a 1.5.x version of groovy, so we are current with their > releases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Updating svn:ignore lists
Configure your local svn ignores in ~/.subversion/config under the 'global-ignores' property. --jason On Apr 11, 2008, at 12:47 AM, Vasily Zakharov wrote: Well, I'm using TortoiseSVN and it always considers those files to be added to the repository when I'm going to create a patch. This obstructs a create patch/commit dialog with a lot of unneeded entries, and increases the working copy scan time. In fact, I wouldn't raise this issue if I don't see that many other 'target' and 'build' directories are put to svn:ignore lists, while some are not. Vasily On Thu, Apr 10, 2008 at 7:18 PM, Jason Warner <[EMAIL PROTECTED]> wrote: Hi Vasily, What do you mean by getting in the way? I've never had issues with this. What behavior are you seeing? ~Jason Warner On Thu, Apr 10, 2008 at 1:15 PM, Vasily Zakharov <[EMAIL PROTECTED]> wrote: When trying to create a patch in an already-built environment, a lot of build-generated directories get in the way. Probably they need to be added to the corresponding SVN ignore lists. I've created a GERONIMO-3957 for that, and provided patches for trunk, branches/2.1, branches/2.0 and tags/2.1.0. I hope it would be useful. Vasily -- ~Jason Warner
Re: Heads-up - GBeanInfo via annotations
Looks cool. Only question I have is why the "G" prefix on annotations
other than GBean?
--jason
On Mar 30, 2008, at 2:55 PM, Gianny Damour <[EMAIL PROTECTED]
> wrote:
Hi,
I am working on the declaration of GBeanInfo via annotations.
This is an example GBean with all the possible annotations (note
that some annotation properties have default values so you do not
see all of them in the example):
@GBean(j2eeType="type", name="name")
@GPriority(priority=123)
public class MockGBean implements Runnable {
public MockGBean(@GParamAttribute(name = "name") String name,
@GParamReference(name = "Name") Runnable runnable) {
}
public void run() {
}
@GAttribute
public String getGetterAttribute() {
return null;
}
@GAttribute
public void setSetterAttribute(String value) {
}
@GReference
public void setSetterReference(Runnable value) {
}
}
Above annotations are in the package
org.apache.geronimo.gbean.annotations.
At the same time, I will add support for pluggable strategies to get
the GBeanInfo of a class. We will have two strategies: use
getGBeanInfo method, current approach; or introspect annotations,
the one I am working on. It will be possible to add additional
strategies, e.g. read a service descriptor file a la OpenEJB.
I will also replace the GBean instantiation code of GBeanInstance by
an ObjectRecipe (xbean-reflect class).
Let me know if you have any concerns about the above plan.
Thanks,
Gianny
Re: svn commit: r641813 - in /geronimo/server/branches/2.1: assemblies/geronimo-boilerplate-minimal/src/main/underlay/ assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/ buildsupport/geron
And what about this: set ERRORLEVEL=0 ? --jason On Mar 27, 2008, at 11:09 PM, Donald Woods wrote: "setlocal enableextensions" ensures that long paths are supported correctly on Windows. We have had it in the geronimo.bat/client.bat scripts for awhile, but the new gsh.bat was missing it. Also, just noticed today that the gsh scripts don't use the setenv/ setjavaenv support that geronimo/client scripts use, so I'll be looking to add that next, so all of the scripts use the same starting environment settings.... -Donald Jason Dillon wrote: What is this change for? Modified: geronimo/server/branches/2.1/assemblies/geronimo- boilerplate-minimal/src/main/underlay/bin/gsh.bat URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.1/assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/gsh.bat?rev=641813&r1=641812&r2=641813&view=diff <http://svn.apache.org/viewvc/geronimo/server/branches/2.1/assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/gsh.bat?rev=641813&r1=641812&r2=641813&view=diff > = = = = = = = = = = --- geronimo/server/branches/2.1/assemblies/geronimo-boilerplate- minimal/src/main/underlay/bin/gsh.bat (original) +++ geronimo/server/branches/2.1/assemblies/geronimo-boilerplate- minimal/src/main/underlay/bin/gsh.bat Thu Mar 27 06:45:31 2008 @@ -22,7 +22,8 @@ rem $Rev$ $Date$ rem -if "%OS%"=="Windows_NT" setlocal +if "%OS%"=="Windows_NT" setlocal enableextensions +set ERRORLEVEL=0 :begin --jason
Re: svn commit: r641813 - in /geronimo/server/branches/2.1: assemblies/geronimo-boilerplate-minimal/src/main/underlay/ assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/ buildsupport/geron
On Mar 27, 2008, at 11:09 PM, Donald Woods wrote: "setlocal enableextensions" ensures that long paths are supported correctly on Windows. We have had it in the geronimo.bat/client.bat scripts for awhile, but the new gsh.bat was missing it. Thanks for the explanation, I'll add it to the gshell sources too. Also, just noticed today that the gsh scripts don't use the setenv/ setjavaenv support that geronimo/client scripts use, so I'll be looking to add that next, so all of the scripts use the same starting environment settings I don't think we really want to do that... as it add more platform specific muck to the scripts. It is more desirable to have users configure GShell (ala the rc.d bits) to set up any environment specific bits. --jason -Donald Jason Dillon wrote: What is this change for? Modified: geronimo/server/branches/2.1/assemblies/geronimo- boilerplate-minimal/src/main/underlay/bin/gsh.bat URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.1/assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/gsh.bat?rev=641813&r1=641812&r2=641813&view=diff <http://svn.apache.org/viewvc/geronimo/server/branches/2.1/assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/gsh.bat?rev=641813&r1=641812&r2=641813&view=diff > = = = = = = = = = = --- geronimo/server/branches/2.1/assemblies/geronimo-boilerplate- minimal/src/main/underlay/bin/gsh.bat (original) +++ geronimo/server/branches/2.1/assemblies/geronimo-boilerplate- minimal/src/main/underlay/bin/gsh.bat Thu Mar 27 06:45:31 2008 @@ -22,7 +22,8 @@ rem $Rev$ $Date$ rem -if "%OS%"=="Windows_NT" setlocal +if "%OS%"=="Windows_NT" setlocal enableextensions +set ERRORLEVEL=0 :begin --jason
Re: svn commit: r641813 - in /geronimo/server/branches/2.1: assemblies/geronimo-boilerplate-minimal/src/main/underlay/ assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/ buildsupport/geron
What is this change for? Modified: geronimo/server/branches/2.1/assemblies/geronimo- boilerplate-minimal/src/main/underlay/bin/gsh.bat URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.1/assemblies/geronimo-boilerplate-minimal/src/main/underlay/bin/gsh.bat?rev=641813&r1=641812&r2=641813&view=diff = = = = = = = = == --- geronimo/server/branches/2.1/assemblies/geronimo-boilerplate- minimal/src/main/underlay/bin/gsh.bat (original) +++ geronimo/server/branches/2.1/assemblies/geronimo-boilerplate- minimal/src/main/underlay/bin/gsh.bat Thu Mar 27 06:45:31 2008 @@ -22,7 +22,8 @@ rem $Rev$ $Date$ rem -if "%OS%"=="Windows_NT" setlocal +if "%OS%"=="Windows_NT" setlocal enableextensions +set ERRORLEVEL=0 :begin --jason
Genesis 1.x branch and Genesis 2.x
FYI, I've made a branch for Genesis 1.x work so that I can work on Genesis 2.x in trunk. The branch is here: https://svn.apache.org/repos/asf/geronimo/genesis/branches/genesis-1.x/ --jason
[jira] Commented: (GSHELL-107) Make IO an interface instead of a class
[ https://issues.apache.org/jira/browse/GSHELL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582558#action_12582558 ] Jason Dillon commented on GSHELL-107: - Why do you want to override these? > Make IO an interface instead of a class > --- > > Key: GSHELL-107 > URL: https://issues.apache.org/jira/browse/GSHELL-107 > Project: GShell > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Guillaume Nodet >Assignee: Jason Dillon > > The fields io.in, io.out. io.err are usually accessed directly which makes > things uneasy to override. > Using an interface with getters would be cleaner. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-89) Install thread specific System.out and System.err adapters
[ https://issues.apache.org/jira/browse/GSHELL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-89: --- Component/s: Core > Install thread specific System.out and System.err adapters > -- > > Key: GSHELL-89 > URL: https://issues.apache.org/jira/browse/GSHELL-89 > Project: GShell > Issue Type: Task > Security Level: public(Regular issues) > Components: Core >Reporter: Jarek Gawor > Assignee: Jason Dillon > Fix For: 1.0-alpha-2 > > > Some integrated tools such as wsgen and wsimport insist on outputting stuff > directly to System.out and System.err. So the only way to capture their > output is to install System.err/System.out adapters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GSHELL-89) Install thread specific System.out and System.err adapters
[ https://issues.apache.org/jira/browse/GSHELL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon reassigned GSHELL-89: -- Assignee: Jason Dillon > Install thread specific System.out and System.err adapters > -- > > Key: GSHELL-89 > URL: https://issues.apache.org/jira/browse/GSHELL-89 > Project: GShell > Issue Type: Task > Security Level: public(Regular issues) > Components: Core >Reporter: Jarek Gawor > Assignee: Jason Dillon > Fix For: 1.0-alpha-2 > > > Some integrated tools such as wsgen and wsimport insist on outputting stuff > directly to System.out and System.err. So the only way to capture their > output is to install System.err/System.out adapters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GSHELL-101) Implement command context
[ https://issues.apache.org/jira/browse/GSHELL-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated GSHELL-101: Component/s: (was: Support - CLP) Core Fix Version/s: (was: 1.0-alpha-3) > Implement command context > - > > Key: GSHELL-101 > URL: https://issues.apache.org/jira/browse/GSHELL-101 > Project: GShell > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.0-alpha-2, 1.0-alpha-3 >Reporter: Jason Warner >Assignee: Jason Dillon > Fix For: 1.0-alpha-2 > > Attachments: GShell-101.patch > > > Gshell current lacks the ability to change the context from which a command > is run. All commands default to running from a root directory. To be able > to launch a command without fully qualifying (i.e; /bsf/script), the command > search path must be used. It would be nice if we could also changed the > context such that we can run any bsf command (or other command group > commands) without having to modify the command search path. This will also > allow us to use relative command paths (../ and ./). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GSHELL-101) Implement command context
[ https://issues.apache.org/jira/browse/GSHELL-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon reassigned GSHELL-101: --- Assignee: Jason Dillon (was: Jason Warner) > Implement command context > - > > Key: GSHELL-101 > URL: https://issues.apache.org/jira/browse/GSHELL-101 > Project: GShell > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Support - CLP >Affects Versions: 1.0-alpha-2, 1.0-alpha-3 >Reporter: Jason Warner >Assignee: Jason Dillon > Fix For: 1.0-alpha-2, 1.0-alpha-3 > > Attachments: GShell-101.patch > > > Gshell current lacks the ability to change the context from which a command > is run. All commands default to running from a root directory. To be able > to launch a command without fully qualifying (i.e; /bsf/script), the command > search path must be used. It would be nice if we could also changed the > context such that we can run any bsf command (or other command group > commands) without having to modify the command search path. This will also > allow us to use relative command paths (../ and ./). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ActiveMQ 4.1.2? 4.2? ActiveIO 3.1? releases
When is G gonna upgrade to AMQ 5? --jason On Mar 26, 2008, at 12:28 PM, David Jencks wrote: On Mar 25, 2008, at 7:41 PM, Donald Woods wrote: Yep, I'd like to see those fixes in 2.1.1, but maybe an ActiveMQ 4.1.2 release that still supports Java 1.4 for existing stand-alone ActiveMQ users would be the best way to go for now. I didn't really consider moving to java 5 (which involves only replacing the backport-concurrent classes with the java.util.concurrent classes) until I picked up the activeio-3.1- SNAPSHOT fix which has already moved definitively to java 5. So I have no problem calling the activemq version 4.2 but keeping a java 1.4 compatibility for activemq won't let you use it on java 1.4 due to the activeio changes. I should have thought of and mentioned this in the original post... thanks david jencks -Donald Joe Bohn wrote: David Jencks wrote: Geronimo is still using ActiveMQ 4 and I've applied patches for or fixed a few bugs that are fairly important for getting MDBS working reliably and fixing other problems. So, I'd like to get a release out of the 4.x branch for the upcoming Geronimo 2.1.1 release. I agree ... it would be great to get those included in 2.1.1. I've looked through the jiras for 4.x and applied the patches for ones that I had a clue about. If anyone else wants something fixed in 4.x please speak up. ActiveIO trunk has a fix that we'd like (don't put non-strings in system properties) so I'd like to release ActiveIO 3.1 also. Since that requires java 5 I'd like to update activemq 4 to use java 5 also (I've tried and this is easy to do). What's the community feeling on this? Is this a real no-no? Would it be better to have the version 4.2 and preserve 4.1.x for java 1.4 work? I'm sure others have more informed opinions on this than I do. I personally can't think of a reason that we should need another java 1.4 release but it certainly is nice to have the option ... so I think it would make sense to do the java 5 work in a 4.2 branch. Although I have to admit that I'm getting a little nervous at all the moving parts for 2.1.1. I'd like to also update the poms to use more modern maven release procedures as well I haven't looked into this much yet and will post further when I do. thanks david jencks
GShell updates
Folks, over the next few days I'm going to be checking in some changes to GShell to move towards using the Maven Artifact library to pull down dependencies,. Have to redo some of the internal plumbing to make that work, so I might break gshell/trunk from time to time, though I'll try to avoid that where possible. --jason
Re: [jira] Created: (GSHELL-106) Problem when Geronimo 2.1 server is started using "start-server"
Are you sure it doesn't stop or that it just takes a while for the terminal to exit? --jason On Mar 21, 2008, at 1:33 PM, Vamsavardhana Reddy (JIRA) wrote: Problem when Geronimo 2.1 server is started using "start-server" Key: GSHELL-106 URL: https://issues.apache.org/jira/browse/GSHELL-106 Project: GShell Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 1.0-alpha-1 Environment: Win XP, G Tomcat 2.1 Reporter: Vamsavardhana Reddy Assignee: Jason Dillon On Windows XP, if I start a Geronimo Tomcat 2.1 server using bin \start-server from a command prompt, I am noticing that the server can not be shutdown using Control+C. So, I am using Admin Console to shutdown the server. But it does not return to command prompt unless I kill the java process from Windows Task Manager. Jarek says, "As a workaround, you can start gshell with -T false option and then control-c worked fine while running the server in foreground." See http://www.mail-archive.com/dev@geronimo.apache.org/msg57308.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
