Geronimo Revision: 601648 built with tests included
See the full build-0300.log file at
http://people.apache.org/~prasad/binaries/2.0/20071206/build-0300.log
Building Geronimo branches/2.0 at Revision: 601648
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO
On Dec 6, 2007 5:43 AM, Anita Kulshreshtha [EMAIL PROTECTED] wrote:
Don't I get 24 hours to respond :)
Yes, you *did* ;-) It passed.
Seriously, I'm in favor releasing what we've got so far as that's the
best way to get people (end users and us) engaged in the development
process of the
On Dec 5, 2007, at 8:26 AM, Shiva Kumar H R wrote:
I am currently working on an Admin Console wizard to auto-generate
openejb-jar.xml http://issues.apache.org/jira/browse/GERONIMO-3432
and one problem where I am currently stuck is given an EJB jar how
do I get it's meta-data complete
[
https://issues.apache.org/jira/browse/GERONIMO-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548961
]
Hirohsi.T commented on GERONIMO-3653:
-
Thanks,
I downloaded Geronimo 2.0.2, checked MD5 hash again. but got
On Dec 6, 2007, at 12:50 AM, [EMAIL PROTECTED] wrote:
Author: dblevins
Date: Thu Dec 6 00:50:16 2007
New Revision: 601659
URL: http://svn.apache.org/viewvc?rev=601659view=rev
Log:
rolling back the change. can't seem to get it to build.
Modified:
--- Viet Nguyen [EMAIL PROTECTED] wrote:
On Dec 5, 2007 11:36 PM, Anita Kulshreshtha [EMAIL PROTECTED]
wrote:
Eric,
For this discussion I will use MC for monitoring console (aka
client), and agent for mrc-server. It is possible to use 3 G
instances
(I used this method until
Montitoring console should display 'available statistics' in a more organized
way
-
Key: GERONIMO-3679
URL: https://issues.apache.org/jira/browse/GERONIMO-3679
Project:
Thanks for the hints Jon.
On Dec 6, 2007 4:48 AM, Jonathan Gallimore [EMAIL PROTECTED] wrote:
Shiva,
I don't know if this is any help, but I'm currently working on some code
to generate annotations based on a JAXB tree generated from an ejb-jar.xml.
As I understand it, OpenEJB does all its
The Monitoring agent should optimize DB activity
Key: GERONIMO-3680
URL: https://issues.apache.org/jira/browse/GERONIMO-3680
Project: Geronimo
Issue Type: Improvement
Security Level:
[
https://issues.apache.org/jira/browse/GERONIMO-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anita Kulshreshtha updated GERONIMO-3680:
-
Attachment: view4.jpg
This graph was drawn with Monitoring console running
[
https://issues.apache.org/jira/browse/GERONIMO-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anita Kulshreshtha updated GERONIMO-3681:
-
Summary: The Monitoring Console should allow the type of graph to be chosen
The Monitoring Console should keep information about Stats available from a
managed object
--
Key: GERONIMO-3682
URL: https://issues.apache.org/jira/browse/GERONIMO-3682
The Monitoring Console should all the type of graph to be chosen
Key: GERONIMO-3681
URL: https://issues.apache.org/jira/browse/GERONIMO-3681
Project: Geronimo
Issue Type:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put this to a vote. The full proposal from Matt Hogstrom
is attached at the end, but the basic proposal we're voting on
implementing in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 Implement the Yoko ORB subproject in Geronimo as proposed above.
Rick McGuire wrote:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put
+1
david jencks
On Dec 6, 2007, at 6:43 AM, Rick McGuire wrote:
The discussion thread has been out there long enough for comment,
and those who have responded appear positive about the prospect. I
think it's time to put this to a vote. The full proposal from Matt
Hogstrom is attached
+1
Rick McGuire wrote:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put this to a vote. The full proposal from Matt Hogstrom
is attached at the end, but the basic proposal we're voting
My +1
Rick McGuire wrote:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put this to a vote. The full proposal from Matt Hogstrom
is attached at the end, but the basic proposal we're
+1
On Dec 6, 2007, at 9:43 AM, Rick McGuire wrote:
The discussion thread has been out there long enough for comment,
and those who have responded appear positive about the prospect. I
think it's time to put this to a vote. The full proposal from Matt
Hogstrom is attached at the end, but
+1
Anita
--- Rick McGuire [EMAIL PROTECTED] wrote:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put this to a vote. The full proposal from Matt
Hogstrom
is attached at the end,
I installed a plugin using 'plugins' portlet in the admin console.
It worked as expected. After the plugin is uninstalled it leaves its
dependent cars and ears behind. I have tried it from both command line
and console. Next time I install the plugin using 'plugins' I get old
dependencies. I
[
https://issues.apache.org/jira/browse/GERONIMO-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen resolved GERONIMO-3676.
Resolution: Fixed
Fix Version/s: 2.1
monitoring client throws an error
Kevan Miller wrote:
On Dec 3, 2007, at 8:04 PM, Gianny Damour wrote:
On 04/12/2007, at 11:45 AM, Jason Dillon wrote:
On Dec 2, 2007, at 5:10 PM, Kevan Miller wrote:
A bit harder to apples-to-apples compare the longer term growth.
lib/gshell accounts for a 5 meg growth (unpacked). So,
+1
Joe
Rick McGuire wrote:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put this to a vote. The full proposal from Matt Hogstrom
is attached at the end, but the basic proposal we're
I have noticed this irksome behavior too. AFAIK, there isn't a better
way. For now, this is a gaping hole in our plugin design.
Seems like when a plugin is uninstalled, we'll have to uninstall all
the child components recursively.
Cheers
Prasad
On Dec 6, 2007 10:04 AM, Anita Kulshreshtha [EMAIL
I agree. We should make GShell flexible like our Geronimo server.
I don't know if this makes sense but I'll just think aloud. At it's
core should be the most basic features like start/stop and
deploy/undeploy. Since Groovy is the culprit, can Groovy sit this one
out ? I believe we use goals from
+1
Regards,
Alan
On Dec 6, 2007, at 6:43 AM, Rick McGuire wrote:
The discussion thread has been out there long enough for comment,
and those who have responded appear positive about the prospect. I
think it's time to put this to a vote. The full proposal from Matt
Hogstrom is attached
A related question.
We currently have a dependency in Geronimo 2.1 on Yoko
1.0-incubating-SNAPSHOT. We need to eliminate that snapshot dependency
(and several others) before we can ship Geronimo 2.1.
Assuming that active VOTE passes would is the possibility of
releasing a 1.0 version
+1
Cheers
Prasad
On Dec 6, 2007 9:43 AM, Rick McGuire [EMAIL PROTECTED] wrote:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put this to a vote. The full proposal from Matt Hogstrom
is
Anita Kulshreshtha wrote:
I installed a plugin using 'plugins' portlet in the admin console.
It worked as expected. After the plugin is uninstalled it leaves its
dependent cars and ears behind. I have tried it from both command line
and console. Next time I install the plugin using
On Dec 6, 2007, at 8:05 AM, Joe Bohn wrote:
A related question.
We currently have a dependency in Geronimo 2.1 on Yoko 1.0-
incubating-SNAPSHOT. We need to eliminate that snapshot dependency
(and several others) before we can ship Geronimo 2.1.
Assuming that active VOTE passes
I personally think we should go the local build route. Until the
subproject's been integrated in Geronimo, it's still bound by the
incubating release rules. I suspect getting a 1.0 release actually
approved and out the door in time for 2.1 given the current state of the
community is not
[
https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen updated GERONIMO-3678:
---
Attachment: geronimo-3678.patch
Monitoring console should accept a port no for
[
https://issues.apache.org/jira/browse/GERONIMO-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549085
]
Jarek Gawor commented on GERONIMO-3653:
---
Where (what directory) did you install Geronimo? Try installing it
--- Joe Bohn [EMAIL PROTECTED] wrote:
Anita Kulshreshtha wrote:
..
I'm not sure why you would have to edit config.xml. You should be
able
to uninstall the dependencies manually via command line or the
console
without the need to modify
Unable to view the installed geronimo plugins
-
Key: GERONIMO-3683
URL: https://issues.apache.org/jira/browse/GERONIMO-3683
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular
[
https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen reassigned GERONIMO-3678:
--
Assignee: Viet Hung Nguyen
Monitoring console should accept a port no for
I am still unsure of why having the monitoring plugin in trunk is such
a bad thing. It is in no way a perfect solution, but once it's in
trunk we can engage users and other devs to better it. I do not see
any dominating issues that should keep this plugin outside of trunk.
Should we vote for this?
On Dec 5, 2007, at 11:43 PM, Anita Kulshreshtha wrote:
Anita, can you please technically show why this is not ready or
should
not be released? Can you explain/show where the graphs are wrong?
This
may help move things along.
Jeff
Don't I get 24 hours to respond :)
We've got lot's of
On Dec 6, 2007, at 12:01 PM, Viet Nguyen wrote:
I am still unsure of why having the monitoring plugin in trunk is such
a bad thing. It is in no way a perfect solution, but once it's in
trunk we can engage users and other devs to better it. I do not see
any dominating issues that should keep
On Dec 6, 2007, at 1:27 AM, Viet Nguyen wrote:
On Dec 5, 2007 9:23 PM, Kevan Miller [EMAIL PROTECTED] wrote:
On Dec 5, 2007, at 9:07 PM, David Jencks wrote:
On Dec 5, 2007, at 4:29 PM, Anita Kulshreshtha wrote:
Viet,
Thanks for working on the monitoring console. A lot still remains
to
Yes, with the current implementation we have, OpenEJB is a
prerequisite. JMX is a good solution too, but I wanted to follow the
JSR 77 spec, which tells us to communicate with the server through the
usage of MEJB, which is why OpenEJB is needed in this case.
--Viet
Isn't the JSR 77 spec JMX based?
Jeff
Viet Nguyen wrote:
Yes, with the current implementation we have, OpenEJB is a
prerequisite. JMX is a good solution too, but I wanted to follow the
JSR 77 spec, which tells us to communicate with the server through the
usage of MEJB, which is why OpenEJB
[
https://issues.apache.org/jira/browse/GERONIMO-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen reassigned GERONIMO-3679:
--
Assignee: Viet Hung Nguyen
Montitoring console should display 'available
Never mind...yes looks like MEJB is a requirement.
Jeff
Jeff Genender wrote:
Isn't the JSR 77 spec JMX based?
Jeff
Viet Nguyen wrote:
Yes, with the current implementation we have, OpenEJB is a
prerequisite. JMX is a good solution too, but I wanted to follow the
JSR 77 spec, which tells
So I think we are kind of caught in a catch 22 here...
The issue is, the server is pluggable for the most part. People may/may
not want EJB, but definitely want the management capabilities.
Whats your thought on an adapter interface that provides for full JSR-77
compatibility, thus requiring
[
https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549105
]
Erik B. Craig commented on GERONIMO-3678:
-
Patch Committed revision 601793.
Thanks Viet.
Monitoring
On Dec 6, 2007, at 7:38 AM, Anita Kulshreshtha wrote:
--- Viet Nguyen [EMAIL PROTECTED] wrote:
On Dec 5, 2007 11:36 PM, Anita Kulshreshtha [EMAIL PROTECTED]
wrote:
Eric,
For this discussion I will use MC for monitoring console (aka
client), and agent for mrc-server. It is possible to use
Whats your thought on an adapter interface that provides for full JSR-77
compatibility, thus requiring EJB, or a switch that allows for pure JMX
remoting? This would allow for compliance or be able to leverage the
management without EJB if so desired.
Thoughts?
There are goods and bads to
I certainly believe it deserves a spot in trunk...this is an enhancement
to what we don't have before. That's progress...and its pretty darn
cool too ;-)
I definitely don't want my ideas to hold up its movement...just food for
thought for down the road.
Jeff
Viet Nguyen wrote:
Whats your
On Dec 6, 2007, at 10:06 AM, Paul McMahan wrote:
On Dec 6, 2007, at 12:45 PM, Kevan Miller wrote:
1. Are we ready to move monitoring plugin out of sandbox?
+1
2. If yes, then where should we move it to? Should it be in server/
trunk/plugins or should the monitoring plugin be a
On Dec 6, 2007, at 12:45 PM, Kevan Miller wrote:
1. Are we ready to move monitoring plugin out of sandbox?
+1
2. If yes, then where should we move it to? Should it be in server/
trunk/plugins or should the monitoring plugin be a subproject.
I would vote for server/trunk/plugins, if for no
+1
David
On Dec 6, 2007, at 6:43 AM, Rick McGuire wrote:
The discussion thread has been out there long enough for comment,
and those who have responded appear positive about the prospect. I
think it's time to put this to a vote. The full proposal from Matt
Hogstrom is attached at the
+1
Jay
Rick McGuire wrote:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put this to a vote. The full proposal from Matt Hogstrom
is attached at the end, but the basic proposal we're
On Dec 6, 2007, at 9:43 AM, Rick McGuire wrote:
The discussion thread has been out there long enough for comment,
and those who have responded appear positive about the prospect. I
think it's time to put this to a vote. The full proposal from Matt
Hogstrom is attached at the end, but
[
https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen resolved GERONIMO-3678.
Resolution: Fixed
Fix Version/s: 2.1
Monitoring console should accept a
[
https://issues.apache.org/jira/browse/GERONIMO-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549143
]
Sangjin Lee commented on GERONIMO-3617:
---
I have a patch ready that addresses this issue and also
+1
Thanks,
Erik B. Craig
[EMAIL PROTECTED]
Rick McGuire wrote:
The discussion thread has been out there long enough for comment, and
those who have responded appear positive about the prospect. I think
it's time to put this to a vote. The full proposal from Matt Hogstrom
is attached at
[
https://issues.apache.org/jira/browse/GERONIMO-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549144
]
Sangjin Lee commented on GERONIMO-3616:
---
I have a patch ready that addresses this issue and also
[
https://issues.apache.org/jira/browse/GERONIMO-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3615:
--
Attachment: patch.zip
a suggested patch
AsyncHttpClient.sendRequest() should return a
[
https://issues.apache.org/jira/browse/GERONIMO-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3616:
--
Attachment: patch.zip
a suggested patch
AsyncHttpClient should support a batch invocation
[
https://issues.apache.org/jira/browse/GERONIMO-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3617:
--
Comment: was deleted
AsyncHttpClient should support retries on connection failures
[
https://issues.apache.org/jira/browse/GERONIMO-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549144
]
sjlee0 edited comment on GERONIMO-3616 at 12/6/07 11:17 AM:
-
I have a patch ready
[
https://issues.apache.org/jira/browse/GERONIMO-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549147
]
Sangjin Lee commented on GERONIMO-3615:
---
I have a patch ready that addresses this issue and also
[
https://issues.apache.org/jira/browse/GERONIMO-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549168
]
Jeff Genender commented on GERONIMO-3615:
-
Sangjin...thanks for the patch...
Could you do a svn diff
[
https://issues.apache.org/jira/browse/GERONIMO-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender closed GERONIMO-3615.
---
Resolution: Fixed
Never mind the last comment, I manually applied this patch, but the
[
https://issues.apache.org/jira/browse/GERONIMO-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Genender closed GERONIMO-3616.
---
Resolution: Fixed
Patch applied from GERONIMO-3615.
AsyncHttpClient should support a
Anita Kulshreshtha wrote:
--- Joe Bohn [EMAIL PROTECTED] wrote:
Anita Kulshreshtha wrote:
..
I'm not sure why you would have to edit config.xml. You should be
able
to uninstall the dependencies manually via command line or the
console
without
[
https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reassigned GERONIMO-3528:
-
Assignee: Jarek Gawor
Cannot lookup JNDI context inside some servlet event
Upgrade Monitoring Client to use Dojo 1.0.1
---
Key: GERONIMO-3684
URL: https://issues.apache.org/jira/browse/GERONIMO-3684
Project: Geronimo
Issue Type: Improvement
Security Level: public
+1
Thanks,
Gianny
On 07/12/2007, at 1:43 AM, Rick McGuire wrote:
The discussion thread has been out there long enough for comment,
and those who have responded appear positive about the prospect. I
think it's time to put this to a vote. The full proposal from Matt
Hogstrom is attached
+1
--jason
On Dec 6, 2007, at 6:43 AM, Rick McGuire wrote:
The discussion thread has been out there long enough for comment,
and those who have responded appear positive about the prospect. I
think it's time to put this to a vote. The full proposal from Matt
Hogstrom is attached at
Release plexus-component-annotations
Key: GSHELL-91
URL: https://issues.apache.org/jira/browse/GSHELL-91
Project: GShell
Issue Type: Sub-task
Security Level: public (Regular issues)
[
https://issues.apache.org/jira/browse/GSHELL-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GSHELL-91:
--
Assignee: Jason Dillon
Release plexus-component-annotations
[
https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549197
]
Jarek Gawor commented on GERONIMO-3528:
---
Committed fixes to trunk (revision 601860).
Cannot lookup JNDI
[
https://issues.apache.org/jira/browse/GSHELL-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-91:
---
Summary: Upgrade to plexus-component-annotations 1.0-alpha-1 (was: Release
[
https://issues.apache.org/jira/browse/GSHELL-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-91:
---
Component/s: Build
Fix Version/s: 1.0-alpha-1
Upgrade to plexus-component-annotations
[
https://issues.apache.org/jira/browse/GSHELL-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-83:
---
Summary: Upgrade to plexus-cdc-anno 1.0-alpha-9 (was: Upgrade to
plexus-cdc-anno 1.0-alpha-1)
[
https://issues.apache.org/jira/browse/GSHELL-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-83.
--
Resolution: Fixed
Upgrade to plexus-cdc-anno 1.0-alpha-9
--
[
https://issues.apache.org/jira/browse/GSHELL-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-91.
--
Resolution: Fixed
Upgrade to plexus-component-annotations 1.0-alpha-1
[
https://issues.apache.org/jira/browse/GERONIMO-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-3528.
---
Resolution: Fixed
Fix Version/s: 2.1
2.0.x
Committed fix to
[
https://issues.apache.org/jira/browse/GSHELL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549206
]
Jason Dillon commented on GSHELL-77:
This is needed for the javacc-m-p
Upgrade Groovy+Maven integreation to
[
https://issues.apache.org/jira/browse/GERONIMO-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen updated GERONIMO-3679:
---
Attachment: geronimo-3679.patch
Montitoring console should display 'available
On Dec 6, 2007, at 12:55 AM, David Blevins wrote:
On Dec 6, 2007, at 12:50 AM, [EMAIL PROTECTED] wrote:
Author: dblevins
Date: Thu Dec 6 00:50:16 2007
New Revision: 601659
URL: http://svn.apache.org/viewvc?rev=601659view=rev
Log:
rolling back the change. can't seem to get it to build.
[
https://issues.apache.org/jira/browse/GERONIMO-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549227
]
Sangjin Lee commented on GERONIMO-3615:
---
Thanks. I'll do that from now on...
Aside from the legal bits and few itty-bitty things GShell is ready
for a release. Will try to wrap this up tonight.
--jason
On Nov 30, 2007, at 8:42 AM, Kevan Miller wrote:
On Nov 29, 2007, at 3:18 AM, Jason Dillon wrote:
Folks, I've halted any significant changes to GShell so we can
[
https://issues.apache.org/jira/browse/GSHELL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed GSHELL-77.
--
Resolution: Fixed
Upgrade Groovy+Maven integration to 1.0-beta-3
[
https://issues.apache.org/jira/browse/GSHELL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GSHELL-77:
---
Summary: Upgrade Groovy+Maven integration to 1.0-beta-3 (was: Upgrade
Groovy+Maven integreation to
All,
Currently the monitoring client is using Dojo 0.4.3 charting, which does
not necessarily behave as expected on Firefox/Safari on a mac, or on IE6
on Windows.
I consider this to be a shortcoming, and given the new version of Dojo
available (1.0.1), began investigating migrating the
OpenEJB trunk at 601816
Geronimo Revision: 601958 built with tests included
See the full build-2100.log file at
http://people.apache.org/~prasad/binaries/trunk/20071206/build-2100.log
[INFO] Surefire report directory:
/home/prasad/geronimo/trunk/plugins/activemq/geronimo-activemq/target
[
https://issues.apache.org/jira/browse/GERONIMO-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549288
]
Erik B. Craig commented on GERONIMO-3679:
-
Patch Committed revision 601966.
Thanks Viet!
Montitoring
On Dec 6, 2007, at 9:29 PM, Erik B. Craig wrote:
All,
Currently the monitoring client is using Dojo 0.4.3 charting, which
does not necessarily behave as expected on Firefox/Safari on a mac,
or on IE6 on Windows.
I consider this to be a shortcoming, and given the new version of
Dojo
On Dec 6, 2007, at 10:35 PM, Kevan Miller wrote:
On Dec 6, 2007, at 9:29 PM, Erik B. Craig wrote:
All,
Currently the monitoring client is using Dojo 0.4.3 charting, which
does not necessarily behave as expected on Firefox/Safari on a mac,
or on IE6 on Windows.
I consider this to be a
On Dec 6, 2007, at 9:29 PM, Erik B. Craig wrote:
Personally, I think it would be really cool if we could use the
Timeplot graphing libraries, as it is all BSD licensed and therefore
friendly I believe (right, Kevan?)...
K. License-wise, there's no problem with Timeplot. It's a straight
On Dec 6, 2007, at 9:29 PM, Erik B. Craig wrote:
All,
Currently the monitoring client is using Dojo 0.4.3 charting, which
does not necessarily behave as expected on Firefox/Safari on a mac,
or on IE6 on Windows.
Errmmm, I stand corrected by myself, it looks like in 0.4.3 things are
Erik B. Craig wrote:
All,
Currently the monitoring client is using Dojo 0.4.3 charting, which does
not necessarily behave as expected on Firefox/Safari on a mac, or on IE6
on Windows.
I consider this to be a shortcoming, and given the new version of Dojo
available (1.0.1), began
I agree with Joe. I think having the x/y axis labels are very
important, especially if we wish to allow the admin to customize these
graphs. It will be rather confusing without them (unless we can write
an extension for Simile to add this feature). Also, I like the curved
lines.
--Viet
+100 for simile.
IMO the curved lines in dojo 0.4.3 are really bogus and basically lie
about how much data you have. I'd recommend you not use them if
possible.
The mouse-over feature is very useful, you can easily read actual
numbers off the graph
multi-series display is pretty much
98 matches
Mail list logo
