Re: [VOTE] M3 pre ApacheCon
On 8/11/2004 8:19 AM, David Jencks wrote:
I'm not exactly ready to vote -1, but I think we should resolve these
issues before M3:
1. http://issues.apache.org/jira/browse/GERONIMO-386 Make cmp work
with derby. Prove it with the itests
I had a look to this one. I have committed a partial implementation and
switched itests to Derby.
As far as I know, these CMP EJBs are not portable as they are using an
auto-generated primary key by the DB. In other words, additional vendor
specific configurations are to be provided to map them to such a table.
The identity of these EJBs have been declared as auto-generated by the
GBean AutoIncrementTablePrimaryKeyGeneratorWrapper. This latter uses
JDBC3.0 to return auto-generated table primary keys.
More accurately, it inserts a dummy record into the entity table via
INSERT INTO entity (first_name) VALUES ('MOCK') and retrieves the
auto-generated primary key. This works; yet I will revisit the
implementation to get ride of this query to be manually specified.
Thanks,
Gianny
Re: [VOTE] M3 pre ApacheCon
+1 Gianny On 4/11/2004 3:48 AM, Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release?
Re: [VOTE] M3 pre ApacheCon
Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release? Here's my +1
Re: [VOTE] M3 pre ApacheCon
On Wed, 3 Nov 2004, Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release? +1 (for a release pre ApacheCon) (I'm also willing to help create/test it) Aaron
Re: [VOTE] M3 pre ApacheCon
+1 -dain On Nov 3, 2004, at 9:03 AM, Aaron Mulder wrote: On Wed, 3 Nov 2004, Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release? +1 (for a release pre ApacheCon) (I'm also willing to help create/test it) Aaron
Re: [VOTE] M3 pre ApacheCon
+1 What's in it? On Nov 3, 2004, at 8:48 AM, Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release? -- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED]
Re: [VOTE] M3 pre ApacheCon
Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release? +1 And I'm willing to help create this release. Maybe Aaron and I could work together on it. Is any of the release work automated in the build yet? Bruce -- perl -e 'print unpack(u30,0G)[EMAIL PROTECTED]5R\\F9EG)E=\\$\\!FFEI+F-O;0\\`\\`);' The Castor Project http://www.castor.org/ Apache Geronimo http://geronimo.apache.org/
Re: [VOTE] M3 pre ApacheCon
I think the package modules/assembly/target/geronimo-xyz.jar is basically what we need to distribute, though I guess we want to wait for Dain to resolve the issue with a hardcoded directory location saved in the ServerInfo. I'm assuming most of the work is in assembling the release notes and stuff. Aaron On Wed, 3 Nov 2004, Bruce Snyder wrote: Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release? +1 And I'm willing to help create this release. Maybe Aaron and I could work together on it. Is any of the release work automated in the build yet? Bruce -- perl -e 'print unpack(u30,0G)[EMAIL PROTECTED]5R\\F9EG)E=\\$\\!FFEI+F-O;0\\`\\`);' The Castor Project http://www.castor.org/ Apache Geronimo http://geronimo.apache.org/
Re: [VOTE] M3 pre ApacheCon
Aaron Mulder wrote: I think the package modules/assembly/target/geronimo-xyz.jar is basically what we need to distribute, though I guess we want to wait for Dain to resolve the issue with a hardcoded directory location saved in the ServerInfo. I'm assuming most of the work is in assembling the release notes and stuff. I'm referring to the creation of the zip and tarball archives, copying them to the right server, etc. Bruce -- perl -e 'print unpack(u30,0G)[EMAIL PROTECTED]5R\\F9EG)E=\\$\\!FFEI+F-O;0\\`\\`);' The Castor Project http://www.castor.org/ Apache Geronimo http://geronimo.apache.org/
Re: [VOTE] M3 pre ApacheCon
+1 from me. -- dims On Wed, 3 Nov 2004 12:03:07 -0500 (EST), Aaron Mulder [EMAIL PROTECTED] wrote: On Wed, 3 Nov 2004, Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release? +1 (for a release pre ApacheCon) (I'm also willing to help create/test it) Aaron -- Davanum Srinivas - http://webservices.apache.org/~dims/
Re: [VOTE] M3 pre ApacheCon
+1 Hiram Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release?
Re: [VOTE] M3 pre ApacheCon
+1 -David On Nov 3, 2004, at 8:48 AM, Jeremy Boynes wrote: On the belief we need to formally vote on making a release, should we produce a M3 release?
Re: [VOTE] M3 pre ApacheCon
On Nov 3, 2004, at 1:02 PM, Aaron Mulder wrote: I think the package modules/assembly/target/geronimo-xyz.jar is basically what we need to distribute, though I guess we want to wait for Dain to resolve the issue with a hardcoded directory location saved in the ServerInfo. I'm assuming most of the work is in assembling the release notes and stuff. If you guys can help cleanup the Jira for creation of the release notes, that would be incredibly helpful. Most the time is spent there. Here are some instructions: http://thread.gmane.org/gmane.comp.java.geronimo.devel/6459 Additionally, no item should have it's Affects Version and it's Fix Version as the same. We treat Affects Version as Where the problem exists and Fix Version as Where the problem was fixed. The Affects Version should be the release id in which the problem first existed (M1, M2). The biggest thing is there is typically a lot of scm activity that isn't reflected in our Jira, so people should go through that add items for anything that was checked in but not added to Jira. -David
