+1
On Dec 6, 2007 3:43 PM, 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
+1
On Dec 7, 2007 1:01 PM, Rick McGuire [EMAIL PROTECTED] wrote:
[ ] +1 - Release the jars
[ ] 0 - No opinion
[ ] -1 - Do not release the jars
We're voting on the following which are required for the Geronimo 2.1
release:
1) Release 1.0.0 of the activation 1.1 spec API. The artifact
[
https://issues.apache.org/jira/browse/GERONIMO-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549989
]
Hirohsi.T commented on GERONIMO-3653:
-
Yes, I install Geronimo c:\geronimo-tomcat6-jee5-2.0.2 and Geronimo
Kevan,
Your fix might have made the problem go way, but I think there's
something else here that might merit a a second look. Look at the stack
trace for the finalizer thread. Why is the finalizer calling the
transform() method on the object getting finalized? I'm not even
certain I
The proposal to incorporate the Yoko core orb as a subproject of
Geronimo has passed with 20 +1 votes and no 0 or -1 votes. Lars Kuhne,
Alexey Petrenko, and Darren Middlemen will be extended invitations to
become Geronimo commiters.
Work to get the code moved into the Geronimo build tree
Unable to create Geronimo as a Windows Service using wrapper.exe
Key: GERONIMO-3691
URL: https://issues.apache.org/jira/browse/GERONIMO-3691
Project: Geronimo
Issue Type: Bug
--- Matt Hogstrom [EMAIL PROTECTED] wrote:
On Dec 7, 2007, at 9:11 AM, Anita Kulshreshtha wrote:
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 was thinking of plugins..
I'm not sure it
I'm with Matt on this. Since it is not perfect to everybody's
satisfaction, let us move it to the /plugins tree (at least for now).
Sandbox is definitely not the place for it.
Erik, contrary to your belief, the /plugins tree does not contain only
those plugins that work independent of G. It
On Dec 10, 2007, at 8:25 AM, Anita Kulshreshtha wrote:
I see Monitoring Console as a tool, a standard J2EE Application,
that has been packaged for a convenient installation in Geronimo. It
talks to a geronimo specific agent to discover and monitor a geronimo
instance running elsewhere. I
Matt Hogstrom wrote:
I think the correct decision would be what do
the users want in terms of it being an integral part of what they do
they would prefer to not go and install it but have it as part of the
base install. I'd be ok with either approach. Most AppServers that I
know of do
Anita Kulshreshtha wrote:
I see Monitoring Console as a tool, a standard J2EE Application,
that has been packaged for a convenient installation in Geronimo. It
talks to a geronimo specific agent to discover and monitor a geronimo
instance running elsewhere. I do not see it as an
Replace yoko snapshot version with known version from repository.
-
Key: GERONIMO-3692
URL: https://issues.apache.org/jira/browse/GERONIMO-3692
Project: Geronimo
Issue Type:
Congrats Jay, welcome aboard!
Cheers!
Hernan
Kevan Miller wrote:
All,
Please join us in congratulating Jay McHugh as the newest member of the
Geronimo PMC. It's been great to have Jay working with us as a committer
on Geronimo. Even better to have him join us in providing oversight of
the
[
https://issues.apache.org/jira/browse/GERONIMO-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550138
]
Jarek Gawor commented on GERONIMO-3605:
---
Added wrappers for install-library, deploy, distribute, and
monitoring client does not perform operations correctly
---
Key: GERONIMO-3693
URL: https://issues.apache.org/jira/browse/GERONIMO-3693
Project: Geronimo
Issue Type: Bug
Security
[
https://issues.apache.org/jira/browse/GERONIMO-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen updated GERONIMO-3693:
---
Attachment: geronimo-3693.patch
monitoring client does not perform operations
[
https://issues.apache.org/jira/browse/GERONIMO-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed GERONIMO-3692.
--
Resolution: Fixed
Committed revision 603021.
Replace yoko snapshot version with known
[
https://issues.apache.org/jira/browse/GERONIMO-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550186
]
Jarek Gawor commented on GERONIMO-3605:
---
Added wrapper for plugin-install command. Also improved
[
https://issues.apache.org/jira/browse/GERONIMO-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3686:
--
Attachment: 3686.patch
A suggested patch. It implements the features mentioned in the
[
https://issues.apache.org/jira/browse/GERONIMO-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550221
]
Erik B. Craig commented on GERONIMO-3693:
-
Patch Committed revision 603080.
Thanks Viet.
monitoring
[
https://issues.apache.org/jira/browse/GSHELL-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GSHELL-46:
--
Assignee: Jason Dillon (was: Jason Warner)
Add flag to show exception stacktraces
Jarek found a startup ordering issue in the minimal servers that I
solved by explicitly specifying the property editor for the
defaultEnvironment attributes. Rev. 603109.
thanks
david jencks
Thanks for fixing this David!
Jarek
On Dec 10, 2007 9:14 PM, David Jencks [EMAIL PROTECTED] wrote:
Jarek found a startup ordering issue in the minimal servers that I
solved by explicitly specifying the property editor for the
defaultEnvironment attributes. Rev. 603109.
thanks
david jencks
[
https://issues.apache.org/jira/browse/GERONIMO-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550276
]
Hirohsi.T commented on GERONIMO-3653:
-
The problem was that wrapper.conf was incorrect.
I added all jar-files
[
https://issues.apache.org/jira/browse/GERONIMO-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hirohsi.T closed GERONIMO-3653.
---
Resolution: Invalid
Getting java.lang.NoClassDefFoundError while starting geronimo as windows
[
https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550278
]
Anita Kulshreshtha commented on GERONIMO-3678:
--
This patch does not work. There is SQL error in
[
https://issues.apache.org/jira/browse/GERONIMO-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550287
]
Viet Hung Nguyen commented on GERONIMO-3678:
those sql statements should be deleted actually, that
Hi,
Thanks for having fixed this problem David. I may have introduced
this bug while working on the property editor stuff. So, I will have
a look at it and see if we can avoid this explicit registration of
property editors.
Thanks,
Gianny
On 11/12/2007, at 1:14 PM, David Jencks wrote:
gsh script in javaee5 server assemblies is not marked executable
-
Key: GERONIMO-3694
URL: https://issues.apache.org/jira/browse/GERONIMO-3694
Project: Geronimo
Issue Type:
[
https://issues.apache.org/jira/browse/GERONIMO-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550318
]
Kevan Miller commented on GERONIMO-3694:
oops. that wasn't quite accurate
Permissions are a problem if
[
https://issues.apache.org/jira/browse/GERONIMO-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon reassigned GERONIMO-3694:
--
Assignee: Jason Dillon
gsh script in javaee5 server assemblies is not marked
jaxws-tools (jar file, shell and bath files) disappeared from javaee assemblies
---
Key: GERONIMO-3695
URL: https://issues.apache.org/jira/browse/GERONIMO-3695
Project:
32 matches
Mail list logo
