[
https://issues.apache.org/jira/browse/GSHELL-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602182#action_12602182
]
Jason Dillon commented on GSHELL-118:
-
This is really 2 related problems. The last one
[
https://issues.apache.org/jira/browse/GSHELL-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602183#action_12602183
]
Jason Dillon commented on GSHELL-118:
-
BTW, for reports like this it would be *very
[
https://issues.apache.org/jira/browse/GSHELL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-89.
--
Resolution: Fixed
Install thread specific System.out and System.err adapters
[
https://issues.apache.org/jira/browse/GSHELL-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-118:
Fix Version/s: (was: 1.0-alpha-2)
1.0-alpha-3
The inter-operation
[
https://issues.apache.org/jira/browse/GERONIMO-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601820#action_12601820
]
Jason Dillon commented on GERONIMO-4093:
I sent email about this a while ago
[
https://issues.apache.org/jira/browse/GSHELL-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reopened GSHELL-112:
-
Assignee: Jason Dillon (was: Jason Warner)
Can not evaluate a variable followed
[
https://issues.apache.org/jira/browse/GSHELL-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601833#action_12601833
]
Jason Dillon commented on GSHELL-112:
-
I'm not sure this is the best fix, not sure why
Ugh... don't know how I messed up this commit so badly :-(
--jason
On May 30, 2008, at 8:44 PM, [EMAIL PROTECTED] wrote:
Author: jdillon
Date: Fri May 30 06:44:33 2008
New Revision: 661717
URL: http://svn.apache.org/viewvc?rev=661717view=rev
Log:
Add gshell-command-support
Added:
Getting constant spam from cron while updating the website again.
--jason
Begin forwarded message:
From: [EMAIL PROTECTED] (Cron Daemon)
Date: May 30, 2008 3:09:58 PM GMT+07:00
To: [EMAIL PROTECTED]
Subject: Cron [EMAIL PROTECTED] /home/jdillon/ws/site/bin/sync
chmod:
messages which contain string concatenation.
--jason
On May 30, 2008, at 8:30 PM, Jason Warner wrote:
How so?
On Fri, May 30, 2008 at 12:22 AM, Jason Dillon [EMAIL PROTECTED]
wrote:
Its unnecessary to guard these log statements.
--jason
On May 29, 2008, at 9:59 PM, [EMAIL PROTECTED
[
https://issues.apache.org/jira/browse/GSHELL-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12601006#action_12601006
]
Jason Dillon commented on GSHELL-117:
-
Does it work with the windows path in quotes
[
https://issues.apache.org/jira/browse/GSHELL-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-117:
Fix Version/s: (was: 1.0-alpha-2)
GShell doesn't support \ in the path in Widnows platform
jvm-version should probably be allowed to contain some range expression.
--jason
On May 29, 2008, at 12:02 PM, Jarek Gawor wrote:
Hi,
While looking at https://issues.apache.org/jira/browse/GERONIMO-4089
one of the problems I discovered was that all of our plugins require
Java 1.5 at runtime
Its unnecessary to guard these log statements.
--jason
On May 29, 2008, at 9:59 PM, [EMAIL PROTECTED] wrote:
Author: jawarner
Date: Thu May 29 07:59:43 2008
New Revision: 661343
URL: http://svn.apache.org/viewvc?rev=661343view=rev
Log:
GERONIMO-4087: Improve usability of gshell commands
[
https://issues.apache.org/jira/browse/GERONIMO-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12600474#action_12600474
]
Jason Dillon commented on GERONIMO-4087:
This should probably just report
- IO
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.
: public (Regular issues)
Components: Core
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.
[
https://issues.apache.org/jira/browse/GSHELL-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-115.
---
Resolution: Fixed
Add Terminal access to IO
-
Key
[
https://issues.apache.org/jira/browse/GSHELL-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-116.
---
Resolution: Fixed
Drop IOLookup, EnvironmentLookup and TerminalFactory
[
https://issues.apache.org/jira/browse/GSHELL-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-45.
--
Resolution: Fixed
This was mainly due to plexus including junit as a compile dependency (for its
[
https://issues.apache.org/jira/browse/GSHELL-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-50.
--
Resolution: Won't Fix
This is now handled by the application/plugin models, so the layout loader has
[
https://issues.apache.org/jira/browse/GSHELL-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-76.
--
Resolution: Won't Fix
layout.xml is no more, replaced by application/plugin model.
Full and minimal
[
https://issues.apache.org/jira/browse/GSHELL-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-39.
--
Resolution: Fixed
The application.xml and plugin.xml support flexible dependency configuration.
Add
[
https://issues.apache.org/jira/browse/GSHELL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-62.
--
Resolution: Fixed
Have primitive support for user tweakable bits in settings.xml
Add settings.xml
[
https://issues.apache.org/jira/browse/GSHELL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599343#action_12599343
]
Jason Dillon commented on GSHELL-89:
Use this one instead:
*
https://svn.codehaus.org
[
https://issues.apache.org/jira/browse/GERONIMO-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GERONIMO-4074:
--
Assignee: Jason Dillon
Testsuite for commands
[
https://issues.apache.org/jira/browse/GERONIMO-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599364#action_12599364
]
Jason Dillon commented on GERONIMO-4074:
What tree was this patch generated from
[
https://issues.apache.org/jira/browse/GERONIMO-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599365#action_12599365
]
Jason Dillon commented on GERONIMO-4074:
by tree I mean branch (or trunk
then, so it gets exercised by at least
Geronimo?
-Donald
Jason Dillon wrote:
Yes, once I fix the mess I made with the logging stuff in server/
trunk.
--jason
On May 6, 2008, at 6:10 PM, Guillaume Nodet wrote:
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599366#action_12599366
]
Jason Dillon commented on GERONIMODEVTOOLS-344:
---
I just meant
[
https://issues.apache.org/jira/browse/GSHELL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-109:
Component/s: (was: CLI)
Support - IO
JLine
Fix
[
https://issues.apache.org/jira/browse/GSHELL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-111:
Component/s: (was: CLI)
Support - IO
JLine
Fix
[
https://issues.apache.org/jira/browse/GSHELL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-107:
Component/s: (was: Core)
Support - IO
Fix Version/s: 1.0-alpha-3
[
https://issues.apache.org/jira/browse/GSHELL-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-99:
---
Component/s: Website
Fix Version/s: 1.0-alpha-3
Show how to run gshell from java service
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599088#action_12599088
]
Jason Dillon commented on GERONIMODEVTOOLS-344:
---
probably would
[
https://issues.apache.org/jira/browse/GSHELL-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598576#action_12598576
]
Jason Dillon commented on GSHELL-113:
-
Um, that is very odd... as the xstream 1.3
+1
--jason
On May 20, 2008, at 7:22 PM, Joe Bohn wrote:
If we are to take this proposal forward to the ASF Infrastructure
team, they want assurance that the Geronimo PMC is behind the
recommendation and supports the intended use of the systems. I
think it also bodes well to demonstrate
[
https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597490#action_12597490
]
Jason Dillon commented on GERONIMO-4011:
Aye, the mutli-line paste stuff
eh, might as well pull the kids out now... not sure what to do with
them, but eh, at the least sell them on ebay and buy me a beer.
:-P
--jason
On May 17, 2008, at 1:47 AM, David Blevins wrote:
On May 15, 2008, at 8:31 AM, Matt Hogstrom wrote:
Well, you can't donate to 'Geronimo' per se
[
https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597019#action_12597019
]
Jason Dillon commented on GERONIMO-4011:
Are there other issues to be fixed
to do for me. Is there a way to do it now?
Jarek
On Fri, May 9, 2008 at 8:44 AM, Jason Dillon [EMAIL PROTECTED]
wrote:
Folks, I've finished cleaning up some of the testsuite, a few
issues that I
see remain, like splitting those ear|war modules up to remove the
need for
extra maven configuration
[
https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GERONIMO-4011:
---
Attachment: jline-0.9.95-SNAPSHOT.jar
See if the attached {{jline-0.9.95-SNAPSHOT.jar
On May 16, 2008, at 2:17 AM, Jarek Gawor wrote:
Jason,
Can you explain why?
Seems like I have to give this speech several times each year. I have
already sent numerous emails on the subject and spent a lot of time
trying to get rid of these properties, which I'm sad to see slowly
On May 16, 2008, at 2:40 AM, Donald Woods wrote:
Disagree, as using properties makes it easier to read and maintain
the versions, especially when the TCK relies on the server pom for
versions and if you create samples or plugins that want to rely on
the same versions as the server
I
/stop-server are working
If all looks well after a few more tests, I'll commit the
changes into trunk for everyone to review before we spend the
time pulling it into 2.1.2.
-Donald
Jason Dillon wrote:
On May 13, 2008, at 1:14 AM, David Jencks wrote:
So including the dependencies you
[
https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596769#action_12596769
]
Jason Dillon commented on GERONIMO-4011:
But why do we need a private build. We
On May 14, 2008, at 3:23 AM, Donald Woods wrote:
Well, changes were already checked into trunk about 20 miins. before
your email
The changes need to also go into branches/2.1, because right now we
have different/duplicate versions of some depends included in
Geronimo 2.1.x and 2.2, due
On May 14, 2008, at 3:23 AM, Donald Woods wrote:
I'm against the continued usage of the gshell-embeddable jar, as it
hides the fact that we are including other depends in our server
assemblies and will just likely cause more version conflicts and
duplicate depends in the future. Maybe if
On May 14, 2008, at 2:29 AM, Joe Bohn wrote:
I'm not sure where those are at but I'm sure we can track them down.
Another bit of criteria that I learned for ASF hosted machines is
that they must be rack-mountable and have lights-out management
LOMs. Is that the case for your apartment
On May 14, 2008, at 2:35 AM, Kevan Miller wrote:
On May 13, 2008, at 1:25 PM, Jason Dillon wrote:
What happened to the AMD systems which were heating up my apartment
last year? 2 4x (dual core) 16g machines with nice RAID cards,
etc... ?
Those machines are owned by IBM. IBM would be happy
[
https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596776#action_12596776
]
Jason Dillon commented on GERONIMO-4011:
Jason (aka ME) == jline commiter
[
https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596786#action_12596786
]
Jason Dillon commented on GERONIMO-4011:
The latter
{{https://sourceforge.net
Oh, folks actually looking at that stuff na... ?
I think some bits need to be flipped to make that happy... though I am
still thinking there is a better solution to the testsuite reporting.
Thanks for the heads up... will see what I can do about it.
--jason
On May 15, 2008, at 12:08 AM,
On May 13, 2008, at 1:14 AM, David Jencks wrote:
So including the dependencies you need for gshell in the
boilerplate's pom would get them into the geronimo repo. As I said
transitive dependencies don't result in inclusion at the moment for
rather good reasons. I don't know what the
[
https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596438#action_12596438
]
Jason Dillon commented on GERONIMO-4011:
Patch it with what?
Need private
Ya, probs a good idea.
--jason
On May 13, 2008, at 9:18 PM, Jarek Gawor wrote:
Should we require maven 2.0.8+ for trunk? Today I've noticed that the
version of maven-javadoc-plugin specified in the root pom requires
maven 2.0.8:
[INFO] Error resolving version for
On May 13, 2008, at 10:42 PM, Joe Bohn wrote:
Right I was running 2 very beefy machines manually in a dedicated
fashion with no automation. If we want something to share, multiple
VM images, and multiple concurrent tests then it would need to be a
bit more robust than what I was using. So
I'm re-exporting the space now, dunno what happened to it though. But
the export site looks okay:
http://cwiki.apache.org/GMOxSITE/
Should sync up in a while.
--jason
On May 12, 2008, at 8:09 AM, YunFeng Ma wrote:
The left menu in Geronimo home page(http://geronimo.apache.org/)
[
https://issues.apache.org/jira/browse/GERONIMO-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595999#action_12595999
]
Jason Dillon commented on GERONIMO-4000:
Does this sample work with the other
What is the command-line you are using to invoke these builds?
--jason
On May 12, 2008, at 3:29 AM, [EMAIL PROTECTED] wrote:
Geronimo Revision: 655356 built with tests included
See the full build-1500.log file at
[
https://issues.apache.org/jira/browse/GERONIMO-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12596008#action_12596008
]
Jason Dillon commented on GERONIMO-3994:
Dropped in branches/2.1 as well
[
https://issues.apache.org/jira/browse/GERONIMO-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GERONIMO-3994:
---
Fix Version/s: 2.1.x
2.1.2
GShell command remote-control/server
I'm trying to remove the use of the gshell-embeddable artifact, which
includes some duplicates (like jline, xstream, slf4j, etc)... but I
can't figure out how the new assembly bits are used to get stuff into
the repository/*.
I can hack something up (with the assembly + antrun plugins) but
It just occured to me that once I finish the maven-artifact
integration into gshell... that Geronimo's repository/* will need to
include pom details for our artifacts so that it can properly resolve
transitive dependencies.
Not sure yet how/when I'm gonna do this, but just a heads up...
I'm not sure we want to do that... as we move closer to using the
maven-artifact library to handle the repository bits, these files will
be critical to include... to avoid misleading warnings.
--jason
On May 12, 2008, at 7:09 PM, Rick McGuire wrote:
This is an issue that came up with the
Aighty.
--jason
On May 13, 2008, at 12:29 AM, Jarek Gawor wrote:
Something like:
cd testsuite
mvn -B -Pheadless,default -Dcolor=false -DassemblyId=$CONTAINER
-DexcludeTest=$EXCLUDE_TESTS
Jarek
On Mon, May 12, 2008 at 4:16 AM, Jason Dillon [EMAIL PROTECTED]
wrote:
What is the command
Yup, will do was waiting to hear how you invoked the tests first.
--jason
On May 13, 2008, at 12:23 AM, Jarek Gawor wrote:
Jason,
Can you please restore that excludeTest functionality (unless you are
planning to put in a workaround for that soon)? This is being used by
the automatic tests
Um, the boilerplate does not put anything into the repository/* so
how do they get in there? Or is that figured out when the boilerplate
is applied to an assembly or something?
--jason
On May 13, 2008, at 12:26 AM, David Jencks wrote:
On May 12, 2008, at 4:20 AM, Jason Dillon wrote
This should be functional again. You don't need to specify -
DexcludeTest= anymore, just set the -DassemblyId to either jetty or
tomcat and the excludes will configure appropriately.
--jason
On May 13, 2008, at 12:23 AM, Jarek Gawor wrote:
Jason,
Can you please restore that excludeTest
message says). However, the test case is executed properly if I add
testng.xml file but that should not be necessary and used to work fine
without it. Any ideas on this problem?
Jarek
On Wed, May 7, 2008 at 6:42 AM, Jason Dillon [EMAIL PROTECTED]
wrote:
FYI, I changed the top-level testsuite module
[
https://issues.apache.org/jira/browse/GSHELL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reopened GSHELL-109:
-
Looks like this is related to GSHELL-111
GShell fails to retrieve the previous commands
Folks, I've finished cleaning up some of the testsuite, a few issues
that I see remain, like splitting those ear|war modules up to remove
the need for extra maven configuration in modules to run the tests.
Looks like there are some legitimate failures in the console-
testsuite, which I've
+1
--jason
On May 8, 2008, at 8:11 PM, Rick McGuire wrote:
All,
I've prepared a release candidate of Geronimo Yoko ORB 1.0 for your
review and vote.
The source for the Yoko ORB release currently resides here:
https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.0
This will also
, then Jason you will have to plug-in native gshell
support before 2.1.2.
Thanks,
Gianny
On 06/05/2008, at 7:25 PM, Jason Dillon wrote:
Aliases where never intended to be invoked via a command,
instead alias, as they work in Bash, simply become a new
command
If that is the case, then why don't we add support to auto-generate
this for each build and stuff the required bits into the maven
repository?
--jason
On Thu, May 8, 2008 at 12:44 AM, Joe Bohn [EMAIL PROTECTED] wrote:
Donald Woods wrote:
Seems that we need a unique plugin repo for each
[
https://issues.apache.org/jira/browse/GERONIMO-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595783#action_12595783
]
Jason Dillon commented on GERONIMO-3858:
Doh, it didn't occur to me
[
https://issues.apache.org/jira/browse/GERONIMO-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595784#action_12595784
]
Jason Dillon commented on GERONIMO-3858:
Actually looks like they might have
case itself is not executed at all (despite what the error
message says). However, the test case is executed properly if I add
testng.xml file but that should not be necessary and used to work fine
without it. Any ideas on this problem?
Jarek
On Wed, May 7, 2008 at 6:42 AM, Jason Dillon [EMAIL
FYI, I changed the top-level testsuite module to use the shitty-maven-
plugin to invoke the children *-testsuite modules, which forks off
another mvn process for each and seems to hang less due to weird ant/
maven/groovy/whatever gremlins.
I'm also doing a test now of using just one
[
https://issues.apache.org/jira/browse/GERONIMO-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594970#action_12594970
]
Jason Dillon commented on GERONIMO-3980:
Because the maven-maven-plugin from
All of the Geronimo-specific alias commands were dropped from trunk,
pending native GShell alias and unalias commands.
--jason
On May 6, 2008, at 10:15 AM, YunFeng Ma wrote:
There is a gshell command execute-alias in G v2.1.1, but it
disappeared in V2.1.2. Should we no longer provide it
You might want to flip off the color for these automated builds, mvn -
Dcolor=false or something.
--jason
On May 6, 2008, at 3:46 PM, [EMAIL PROTECTED] wrote:
Geronimo Revision: 653691 built with tests included
See the full build-0300.log file at
Feng
--- On Tue, 5/6/08, Jason Dillon [EMAIL PROTECTED] wrote:
From: Jason Dillon [EMAIL PROTECTED]
Subject: Re: No longer provide gshell command execute-alias in
Geronimo v2.1.2?
To: dev@geronimo.apache.org
Date: Tuesday, May 6, 2008, 12:15 AM
All of the Geronimo-specific alias commands were
Will SLF4J's Logger get vararg methods soon? Please?
--jason
On May 6, 2008, at 4:15 PM, Ceki Gulcu wrote:
Jason Dillon [EMAIL PROTECTED] writes:
The other option, is to create our own SLF4J implementation, which
provides this serialization muck... which may also allow us to add
some
Yes, once I fix the mess I made with the logging stuff in server/trunk.
--jason
On May 6, 2008, at 6:10 PM, Guillaume Nodet wrote:
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
[
https://issues.apache.org/jira/browse/GERONIMO-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GERONIMO-3980.
--
Resolution: Fixed
Fix Version/s: 2.2
Replace maven-maven-plugin usage with shitty
and at the same time continue to
update the code to use static loggers.
Jarek
On Sun, May 4, 2008 at 10:44 AM, Jason Dillon [EMAIL PROTECTED]
wrote:
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
[
https://issues.apache.org/jira/browse/GERONIMO-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594301#action_12594301
]
Jason Dillon commented on GERONIMO-3989:
How to reproduce?
gshell - infinite
[
https://issues.apache.org/jira/browse/GERONIMO-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GERONIMO-3989:
--
Assignee: Jason Dillon
gshell - infinite loop
: buildsystem
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.
this problem with
seralization will bite us again. So I think we will need a way for a
logger to serialize/deserlialize ok and at the same time continue to
update the code to use static loggers.
Jarek
On Sun, May 4, 2008 at 10:44 AM, Jason Dillon [EMAIL PROTECTED]
wrote:
I think this is related
Yes, this is intentional. SLF4J has some optimized code to deal with
{} strings for substitution.
--jason
On May 6, 2008, at 3:46 AM, Jacek Laskowski wrote:
On Mon, May 5, 2008 at 10:34 PM, [EMAIL PROTECTED] wrote:
Author: jdillon
Date: Mon May 5 13:34:06 2008
New Revision: 653588
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
[
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
[
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
[
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
[
https://issues.apache.org/jira/browse/GSHELL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594098#action_12594098
]
Jason Dillon commented on GSHELL-111:
-
Um, gsh commands work only with one line... so
[
https://issues.apache.org/jira/browse/GSHELL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-107:
Component/s: Core
Make IO an interface instead of a class
[
https://issues.apache.org/jira/browse/GSHELL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594111#action_12594111
]
Jason Dillon commented on GSHELL-111:
-
And how does it behave with the terminal set
[
https://issues.apache.org/jira/browse/GSHELL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594114#action_12594114
]
Jason Dillon commented on GSHELL-111:
-
Aighty, its a bug w/Jline then... I'll
301 - 400 of 3782 matches
Mail list logo
