Geronimo Revision: 603843 built with tests included
See the full build-0200.log file at
http://people.apache.org/~prasad/binaries/2.0/20071213/build-0200.log
Download the binaries from
http://people.apache.org/~prasad/binaries/2.0/20071213
[INFO] BUILD SUCCESSFUL
[INFO
[
https://issues.apache.org/jira/browse/GERONIMO-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551451
]
Rick McGuire commented on GERONIMO-3703:
I think using a default context is probably a good idea. Most
OpenEJB trunk at 603843
Geronimo Revision: 603850 built with tests included
See the full build-0300.log file at
http://people.apache.org/~prasad/binaries/trunk/20071213/build-0300.log
Download the binaries from
http://people.apache.org/~prasad/binaries/trunk/20071213
[INFO] BUILD SUCCESSFUL
[
https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551464
]
Rick McGuire commented on GERONIMO-3638:
I'm not sure I understand the rationale for using US-ASCII as
[
https://issues.apache.org/jira/browse/GERONIMO-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-3703.
Resolution: Fixed
Committed revision 603885.
I've committed this patch, but there's
If GShell would be targeted at more servers than G then I think these
commands should be under geronimo. If not, then I think a flat
structure makes sense.
On Dec 11, 2007, at 10:04 AM, Kevan Miller wrote:
We currently have the following structure for Geronimo GShell
commands:
I was running monitoring console on G(portoffset=10) and the agent
on default G instance. I saw this trace on the screen at a later time.
So I can not describe what exactly I was doing.. This can probably be
fixed by ordering the sql operations correctly.
Thanks
Anita
14:48:27,968 ERROR
[
https://issues.apache.org/jira/browse/GERONIMO-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed GERONIMO-3704.
--
Resolution: Fixed
Committed revision 603928.
Convert the activation and javamail
Convert the activation and javamail dependencies to non-snapshot versions.
--
Key: GERONIMO-3704
URL: https://issues.apache.org/jira/browse/GERONIMO-3704
Project: Geronimo
Geronimo Revision: 603911 built with tests included
See the full build-0800.log file at
http://people.apache.org/~prasad/binaries/2.0/20071213/build-0800.log
Download the binaries from
http://people.apache.org/~prasad/binaries/2.0/20071213
[INFO] BUILD SUCCESSFUL
[INFO
OpenEJB trunk at 603914
Geronimo Revision: 603921 built with tests included
See the full build-0900.log file at
http://people.apache.org/~prasad/binaries/trunk/20071213/build-0900.log
Download the binaries from
http://people.apache.org/~prasad/binaries/trunk/20071213
[INFO] BUILD SUCCESSFUL
On Dec 12, 2007 8:27 PM, David Jencks [EMAIL PROTECTED] wrote:
I must be missing something... how does the prerequisite system work
better than dependencies here? I'm not 100% sure of what currently
happens when you try to install a plugin that has an unavailable
dependency, but it certainly
Thanks Aaron for the thorough explanation. I agree that the prereq
relationship provides useful information and functionality beyond
what the dependency relationship provides. The plugins portlet in
the admin console will currently inspect the prerequisites for the
plugins listed in a
[
https://issues.apache.org/jira/browse/GERONIMO-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551589
]
Sangjin Lee commented on GERONIMO-3703:
---
It should be OK, because sessions are reused for the specific host
[
https://issues.apache.org/jira/browse/GERONIMO-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3703:
--
Attachment: test.patch
added a unit test that tests connection reuse with SSL sockets
[
https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551592
]
Sangjin Lee commented on GERONIMO-3638:
---
Yes, I agree the default for URL encoding should be UTF-8. I also
[
https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3638:
--
Attachment: (was: 3638.patch)
should allow URL encoding with custom encoding charset
[
https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3638:
--
Attachment: 3638.patch
a revised patch
should allow URL encoding with custom encoding
Hi,
I am trying to add a few custom entries into the app specific JNDI
space. Is it possible to get a handle to the componentContext during
the deployment of a J2EE app so that it can be modified. It becomes
immutable after the application starts as per the spec so i need to do
it during
[
https://issues.apache.org/jira/browse/GERONIMO-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551600
]
Rick McGuire commented on GERONIMO-3703:
Good test to add. Thanks!
Committed revision 604016.
should
[
https://issues.apache.org/jira/browse/GERONIMO-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire resolved GERONIMO-3638.
Resolution: Fixed
Assignee: Rick McGuire
Committed revision 604018.
This last
Joe Bohn wrote:
It looks like the size of our images is increasing dramatically (nearly
2x).
For example, the geronimo-jetty6-minimal snapshots have been growing
like this (these image sizes are from the snapshot repo):
16604006 Jul 26 18:54
[
https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GSHELL-20:
--
Assignee: Jason Dillon (was: Jason Warner)
`set foo=bar` does not work as expected
[
https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-20:
---
Affects Version/s: (was: 0.0.1)
1.0-alpha-1
Fix Version/s:
[
https://issues.apache.org/jira/browse/GSHELL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-20.
--
Resolution: Fixed
Thanks :-)
`set foo=bar` does not work as expected
OK, so I agree the prereq feature is useful so I'll stop trying to
remove it :-)
However I ***really*** don't think it should be used for assuring the
correct web server. I want to being install a plugin such as the web
console and have it install the web server as a dependency. To me
A really long time ago Dain made the server work without gbean
proxies in gbean references, but we didn't enable this by default
because it broke the admin console. While waiting for a build I had
a look and think I've fixed the admin console it still seems to
work.
I expect to
I will just conclude by saying it's not my feeling that we currently
have the best possible solution -- I just want to make sure things
don't move backward. It would be possible to provide special handling
for Tomcat/Jetty at the level of JVM versions and take that issue out
of the picture. It
Wow! Either you're pretty sharp or you really need a faster machine! :)
I think the main issue was that the console expected to be able to
cast GBean references to some helper interface in order to start and
stop individual GBeans and get a GBean's name and things like that.
And the proxies
On Dec 13, 2007, at 3:20 PM, Aaron Mulder wrote:
Wow! Either you're pretty sharp or you really need a faster
machine! :)
or the solution was really simple :-)
I think the main issue was that the console expected to be able to
cast GBean references to some helper interface in order to
On Dec 11, 2007, at 4:58 AM, Jason Dillon wrote:
Folks, a small change to Genesis was made to support a custom legal
resource bundle for the GShell release. I'd like to get this out so
we can get GShell out too.
+1 -Release it
+0 -Eh, whatever
-1 -Um, no no no no no...
+1
On Dec 13, 2007, at 6:15 PM, David Jencks wrote:
A really long time ago Dain made the server work without gbean
proxies in gbean references, but we didn't enable this by default
because it broke the admin console. While waiting for a build I had
a look and think I've fixed the admin
Jason,
Can you give a reason for this change? I might have to update a few machines.
Thanks,
Jarek
On Dec 13, 2007 5:41 PM, [EMAIL PROTECTED] wrote:
Author: jdillon
Date: Thu Dec 13 14:41:50 2007
New Revision: 604053
URL: http://svn.apache.org/viewvc?rev=604053view=rev
Log:
Require
We can remove some of the gshell bloat by not using the gshell-
embedable jar which contains xstream, jexl, log4j-diet, jline and some
other bits which are already in the repository. Might drop things
down by 1 or 2m.
Also we can make a diet version of groovy and ant, containing on the
Aye.
--jason
On Dec 13, 2007, at 5:13 PM, Jay D. McHugh wrote:
I believe that the build will crash if you use Maven 2.0.8
That is probably why Jason forced the maven version.
Jay
Jarek Gawor wrote:
Jason,
Can you give a reason for this change? I might have to update a few
machines.
I believe that the build will crash if you use Maven 2.0.8
That is probably why Jason forced the maven version.
Jay
Jarek Gawor wrote:
Jason,
Can you give a reason for this change? I might have to update a few machines.
Thanks,
Jarek
On Dec 13, 2007 5:41 PM, [EMAIL PROTECTED] wrote:
Ok, sure but doesn't that cut off 2.0.5 and 2.0.6 users?
Jarek
On Dec 13, 2007 8:28 PM, Jason Dillon [EMAIL PROTECTED] wrote:
Aye.
--jason
On Dec 13, 2007, at 5:13 PM, Jay D. McHugh wrote:
I believe that the build will crash if you use Maven 2.0.8
That is probably why Jason forced
I suppose 2.0.6 should work. We can include that.
--jason
-Original Message-
From: Jarek Gawor [EMAIL PROTECTED]
Date: Thu, 13 Dec 2007 20:49:10
To:dev@geronimo.apache.org
Subject: Re: svn commit: r604053 - /geronimo/server/trunk/pom.xml
Ok, sure but doesn't that cut off 2.0.5 and
[
https://issues.apache.org/jira/browse/GSHELL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551671
]
Jason Dillon commented on GSHELL-97:
Usage of the shade plugin is making this more of a pain to use a static or
Maven 2.0.8 causes build problems
-
Key: GERONIMO-3705
URL: https://issues.apache.org/jira/browse/GERONIMO-3705
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
40 matches
Mail list logo