Move to OpenJPA 1.0.1
-
Key: GERONIMO-3631
URL: https://issues.apache.org/jira/browse/GERONIMO-3631
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Reporter: Joe Bohn
[
https://issues.apache.org/jira/browse/GERONIMO-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn updated GERONIMO-3631:
---
Affects Version/s: 2.1
Move to OpenJPA 1.0.1
-
Key:
[
https://issues.apache.org/jira/browse/GERONIMO-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen closed GERONIMO-3595.
--
Resolution: Invalid
Fix Version/s: 2.1
This violates the JSR 77 spec. There
Does anybody have thoughts on this or know how this should work?
Jarek
On Nov 19, 2007 11:07 PM, Jarek Gawor [EMAIL PROTECTED] wrote:
I've looked at this a bit and here's my current understanding of the
problem. First, we are dealing with two different web application
contexts (/console and
Geronimo Revision: 597960 built with tests included
See the full build-0300.log file at
http://people.apache.org/~prasad/binaries/2.0/20071125/build-0300.log
Download the binaries from
http://people.apache.org/~prasad/binaries/2.0/20071125
[INFO] BUILD SUCCESSFUL
[INFO]
Thanks Kevan,
can checkout content again, though found out the comma is actually accepted (I
guess I need a bigger keyboard ;-) )
Cheers!
Hernan
Kevan Miller wrote:
On Nov 20, 2007, at 1:48 PM, Hernan Cunico wrote:
yeah, the comma is also a problem.
Cheers!
Hernan
Vamsavardhana Reddy
Thanks Kevan,
can checkout content again, though found out the comma is actually accepted (I
guess I need a bigger keyboard ;-) )
Cheers!
Hernan
Kevan Miller wrote:
On Nov 20, 2007, at 1:48 PM, Hernan Cunico wrote:
yeah, the comma is also a problem.
Cheers!
Hernan
Vamsavardhana Reddy
I was just looking in the root pom. It seems there are a number of
snapshot dependencies that we would need to eliminate prior to a 2.1
release (or make private builds). I'll start working my way through
those that have released. We'll need to start pushing for some releases
of those that
I'd like to find some time to test the geronimo trunk with the latest set of
specs that i've modified to make them OSGi friendly, but I doubt I will have
much time this week. It would be a good test to make sure there is no
regression caused by the change in the packaging mechanism...
On Nov 26,
The javamail version can be made into a release. It has a dependency on
the latest spec version, so we'd need to release that one too.
For yoko, I suspect we'll just need to do what we did for 2.0 and have a
known version in the Geronimo repository.
Rick
Joe Bohn wrote:
I was just looking
monitoring client needs to have jetty and tomcat plugin
---
Key: GERONIMO-3632
URL: https://issues.apache.org/jira/browse/GERONIMO-3632
Project: Geronimo
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/GERONIMO-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viet Hung Nguyen updated GERONIMO-3632:
---
Attachment: geronimo-3632.patch
monitoring client needs to have jetty and tomcat
[
https://issues.apache.org/jira/browse/GERONIMO-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks reassigned GERONIMO-3609:
--
Assignee: David Jencks
JNDI lookup problem on fowarded calls in Jetty
[
https://issues.apache.org/jira/browse/GERONIMO-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545548
]
David Jencks commented on GERONIMO-3609:
Proposed fix will work but I think it introduces duplication
[
https://issues.apache.org/jira/browse/GERONIMO-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545565
]
Erik B. Craig commented on GERONIMO-3632:
-
Applied in rev 598392.
Thanks viet.
monitoring client needs
On Nov 26, 2007, at 11:29 AM, Joe Bohn wrote:
I was just looking in the root pom. It seems there are a number of
snapshot dependencies that we would need to eliminate prior to a 2.1
release (or make private builds). I'll start working my way through
those that have released. We'll need
Geronimo Revision: 598385 built with tests included
See the full build-1500.log file at
http://people.apache.org/~prasad/binaries/2.0/20071126/build-1500.log
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
apache-snapshots (http://people.apache.org/repo/m2
On Nov 26, 2007, at 2:36 PM, Kevan Miller wrote:
On Nov 26, 2007, at 11:29 AM, Joe Bohn wrote:
Pluto 1.2.0-SNAPSHOT
Has anybody pinged their list?
Joe and I have pinged their list, no response yet.
myfaces1.2.1-SNAPSHOT
Has anybody pinged
Kevan Miller wrote:
On Nov 26, 2007, at 11:29 AM, Joe Bohn wrote:
I was just looking in the root pom. It seems there are a number of
snapshot dependencies that we would need to eliminate prior to a 2.1
release (or make private builds). I'll start working my way through
those that have
[
https://issues.apache.org/jira/browse/GERONIMO-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545572
]
Jarek Gawor commented on GERONIMO-3609:
---
Ok, thanks. I just checked in a test case for this issue under
Kevan Miller wrote:
On Nov 26, 2007, at 11:29 AM, Joe Bohn wrote:
I was just looking in the root pom. It seems there are a number of
snapshot dependencies that we would need to eliminate prior to a 2.1
release (or make private builds). I'll start working my way through
those that have
[
https://issues.apache.org/jira/browse/GERONIMO-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3609.
--
Resolution: Fixed
Fix Version/s: 2.1
Fixed in rev 598410 with solution from patch
On Nov 26, 2007, at 7:13 AM, Jarek Gawor wrote:
Does anybody have thoughts on this or know how this should work?
Your proposed fix in GERONIMO-3609 is basically correct but it
results in duplicating the jndi setting during a normal request. I
eliminated this and committed the change.
Hi, all,
Geronimo v2.0.2 uses XStream 1.1.3, while the latest version is 1.2.2.
I'd like to ask, are there any plans for moving to a newer version?
I'm trying to run Geronimo Unit Test v2.0.2 on Apache Harmony, and
encounter errors like these:
http://jira.codehaus.org/browse/XSTR-189,
Zakharov, Vasily M wrote:
Hi, all,
Geronimo v2.0.2 uses XStream 1.1.3, while the latest version is 1.2.2.
I'd like to ask, are there any plans for moving to a newer version?
Yes, Geronimo trunk (2.1-SNAPSHOT) is currently using XStream 1.2.2.
Joe
Joe Bohn wrote:
Are there other components that we should upgrade as well?
I recall hearing some discussion about moving to Dojo 1.0. Has anybody
looked into this further? Is this something we should do for Geronimo 2.1?
Joe
VM arguments are reverted to default ones after starting the server
---
Key: GERONIMODEVTOOLS-252
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252
Project:
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Szczepanik updated GERONIMODEVTOOLS-252:
--
Environment: Ubuntu Linux 7.10 (i386), Eclipse 3.3.1, Java
Great, thanks!
Vasily
-Original Message-
From: Joe Bohn [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 27, 2007 12:08 AM
To: dev@geronimo.apache.org
Subject: Re: XStream/Harmony problem
Zakharov, Vasily M wrote:
Hi, all,
Geronimo v2.0.2 uses XStream 1.1.3, while the latest
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545657
]
Kan Ogawa commented on GERONIMODEVTOOLS-252:
Piotr,
Set VM arguments value to the Server VM
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kan Ogawa updated GERONIMODEVTOOLS-252:
---
Attachment: ServerVMArguments.jpg
VM arguments are reverted to default
[
https://issues.apache.org/jira/browse/GERONIMO-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545673
]
Sangjin Lee commented on GERONIMO-3615:
---
I am working on code changes that achieves this and also aids the
Hey Geronimos,
How did we do the xsd schemas that they're available at the shorter
URL? I'd like to introduce it to openejb, but am wondering how I shall
do it. Was it a one-shot task?
Jacek
-- Forwarded message --
From: Jacek Laskowski [EMAIL PROTECTED]
Date: Nov 27, 2007 8:02
33 matches
Mail list logo
