All,
I've updated the versions in branches/2.0.2 from 2.0.2-SNAPSHOT to
2.0.2. No code changes should be going into 2.0.2.
I'm going to be finalizing the release notes and building binaries
later tonight.
The ibiblio repo is having problems this afternoon. To build
successfully, I had
Kevan Miller wrote:
All,
I've created a 2.0.2 release branch --
https://svn.apache.org/repos/asf/geronimo/server/branches/2.0.2
And have updated the branches/2.0 version to be 2.0.3-SNAPSHOT (with a
helping hand from Donald :)
Vamsi is working on an update to the CA Helper in the
On Oct 10, 2007, at 6:16 AM, Joe Bohn wrote:
Kevan Miller wrote:
All,
I've created a 2.0.2 release branch -- https://svn.apache.org/
repos/asf/geronimo/server/branches/2.0.2
And have updated the branches/2.0 version to be 2.0.3-SNAPSHOT
(with a helping hand from Donald :)
Vamsi is
Hi Vamsi,
can you summarize what are the updates on the CA Helper so we can add it to the
2.0.2 release notes
http://cwiki.apache.org/GMOxDOC20/release-notes-202txt.html
There have also been some updates on MEJB and JNDI. For those of you folks who
worked directly on these areas could you
I just set the default ThreadPool size back to 500, so the Jetty problem
should be solved.
-Donald
Kevan Miller wrote:
All,
I've created a 2.0.2 release branch --
https://svn.apache.org/repos/asf/geronimo/server/branches/2.0.2
And have updated the branches/2.0 version to be
All,
I've created a 2.0.2 release branch -- https://svn.apache.org/repos/
asf/geronimo/server/branches/2.0.2
And have updated the branches/2.0 version to be 2.0.3-SNAPSHOT (with
a helping hand from Donald :)
Vamsi is working on an update to the CA Helper in the console.
Joe B is working
On 10/8/07, Kevan Miller [EMAIL PROTECTED] wrote:
All,
I've created a 2.0.2 release branch -- https://svn.apache.org/repos/
asf/geronimo/server/branches/2.0.2
And have updated the branches/2.0 version to be 2.0.3-SNAPSHOT (with
a helping hand from Donald :)
Vamsi is working on an update
Kevan,
I just verified that the tranql mysql wrapper works at least a little
bit and published it. Could you update a couple pom versions before
branching?
Index: pom.xml
===
--- pom.xml (revision 580497)
+++ pom.xml
What's the plan for creating a 2.0.2 branch in preparation of closing down the
release?
-Donald
Kevan Miller wrote:
All,
I think it's time to start rolling out a 2.0.2 release. There have been
a number of fixes in response to user issues, since 2.0.1. Time, I
think, to make these available
Can the following be removed from the JEE5 config.xml files, now that we have
the MEJB fix in?
!-- See GERONIMO-3461 for why this is disabled by default --
gbean load=false name=ejb/mgmt/MEJB/
-Donald
Kevan Miller wrote:
All,
I think it's time to start rolling out a 2.0.2
On Oct 5, 2007, at 8:42 AM, Donald Woods wrote:
What's the plan for creating a 2.0.2 branch in preparation of
closing down the release?
Matt sent a note earlier today, while I was in a jet-lagged impose
slumber... I'll plan on creating a branches/2.0.2 for finalizing
release activity on
go for it..
Anita
--- Donald Woods [EMAIL PROTECTED] wrote:
Can the following be removed from the JEE5 config.xml files, now that
we have
the MEJB fix in?
!-- See GERONIMO-3461 for why this is disabled by default
--
gbean load=false name=ejb/mgmt/MEJB/
-Donald
Done.
Anita Kulshreshtha wrote:
go for it..
Anita
--- Donald Woods [EMAIL PROTECTED] wrote:
Can the following be removed from the JEE5 config.xml files, now that
we have
the MEJB fix in?
!-- See GERONIMO-3461 for why this is disabled by default
--
gbean load=false
On Oct 2, 2007, at 7:02 PM, David Blevins wrote:
Ok, I made the following changes:
- Set the deployment id format to {appId}/{moduleId}/{ejbName}
(fixes GERONIMO-3199)
- Set jndiname format to {ejbName}{interfaceType.annotationName}
(this MUST go in the release notes as it will be a
On Oct 1, 2007, at 4:24 PM, David Jencks wrote:
I talked with david a bit on irc and he tells me there is a flag so
we can set it so if there is a non-javaee jndi name conflict we log
an error instead of throwing an exception.
I'm happy with a simple default format for non-javaee jndi ejb
On Sep 29, 2007, at 3:06 PM, David Blevins wrote:
On Sep 29, 2007, at 12:31 AM, David Jencks wrote:
On Sep 28, 2007, at 8:40 PM, David Blevins wrote:
On Sep 25, 2007, at 3:40 PM, David Blevins wrote:
On Sep 25, 2007, at 7:38 AM, Kevan Miller wrote:
One thing I've noticed -- the
On Sep 28, 2007, at 8:40 PM, David Blevins wrote:
On Sep 25, 2007, at 3:40 PM, David Blevins wrote:
On Sep 25, 2007, at 7:38 AM, Kevan Miller wrote:
One thing I've noticed -- the default JNDI name for EJB's has
been changed in OpenEJB. So, there is a compatibility issue with
2.0.1. We
On Sep 29, 2007, at 12:31 AM, David Jencks wrote:
On Sep 28, 2007, at 8:40 PM, David Blevins wrote:
On Sep 25, 2007, at 3:40 PM, David Blevins wrote:
On Sep 25, 2007, at 7:38 AM, Kevan Miller wrote:
One thing I've noticed -- the default JNDI name for EJB's has
been changed in
On Sep 25, 2007, at 3:40 PM, David Blevins wrote:
On Sep 25, 2007, at 7:38 AM, Kevan Miller wrote:
One thing I've noticed -- the default JNDI name for EJB's has been
changed in OpenEJB. So, there is a compatibility issue with 2.0.1.
We might be able to configure how OpenEJB generates
On Sep 26, 2007, at 7:30 PM, Kevan Miller wrote:
On Sep 25, 2007, at 4:08 PM, Donald Woods wrote:
OK, I'm done updating the 2.0.x closed issues (sorry for all the
JIRA emails.)
The only one I couldn't figure out, was:
https://issues.apache.org/jira/browse/GERONIMO-3423
Donald,
On Sep 26, 2007, at 4:01 PM, Kevan Miller wrote:
On Sep 25, 2007, at 6:40 PM, David Blevins wrote:
On Sep 25, 2007, at 7:38 AM, Kevan Miller wrote:
One thing I've noticed -- the default JNDI name for EJB's has
been changed in OpenEJB. So, there is a compatibility issue with
2.0.1. We
On Sep 27, 2007, at 4:13 PM, Kevan Miller wrote:
On Sep 26, 2007, at 7:30 PM, Kevan Miller wrote:
On Sep 25, 2007, at 4:08 PM, Donald Woods wrote:
OK, I'm done updating the 2.0.x closed issues (sorry for all the
JIRA emails.)
The only one I couldn't figure out, was:
On Sep 25, 2007, at 6:40 PM, David Blevins wrote:
On Sep 25, 2007, at 7:38 AM, Kevan Miller wrote:
One thing I've noticed -- the default JNDI name for EJB's has been
changed in OpenEJB. So, there is a compatibility issue with 2.0.1.
We might be able to configure how OpenEJB generates
On Sep 25, 2007, at 4:08 PM, Donald Woods wrote:
OK, I'm done updating the 2.0.x closed issues (sorry for all the
JIRA emails.)
The only one I couldn't figure out, was:
https://issues.apache.org/jira/browse/GERONIMO-3423
Donald,
Thanks a bunch for going through all of those Jiras!
I've committed to branches/2.0 also.
thanks
david jencks
On Sep 25, 2007, at 1:47 AM, David Jencks wrote:
On Sep 24, 2007, at 8:52 AM, Anita Kulshreshtha wrote:
--- Kevan Miller [EMAIL PROTECTED] wrote:
On Sep 20, 2007, at 8:38 AM, Donald Woods wrote:
I see that Anita has attached
On Sep 25, 2007, at 8:51 AM, David Jencks wrote:
I've committed to branches/2.0 also.
Thanks David!
I think this leaves us with:
* integration of the MEJB code itself
* release of OpenEJB 3.0-Beta
One thing I've noticed -- the default JNDI name for EJB's has been
changed in OpenEJB. So,
BTW - I'm going through JIRA today and updating any Fix For: 2.0.x
closed/resolved issues to use the correct release attribute, so we can
generate a valid list of fixes for the 2.0.2 release notes
-Donald
Kevan Miller wrote:
All,
I think it's time to start rolling out a 2.0.2 release.
OK, I'm done updating the 2.0.x closed issues (sorry for all the JIRA emails.)
The only one I couldn't figure out, was:
https://issues.apache.org/jira/browse/GERONIMO-3423
-Donald
Donald Woods wrote:
BTW - I'm going through JIRA today and updating any Fix For: 2.0.x
I guess it is rev 570242 in trunk.
Vamsi
On 9/26/07, Donald Woods [EMAIL PROTECTED] wrote:
OK, I'm done updating the 2.0.x closed issues (sorry for all the JIRA
emails.)
The only one I couldn't figure out, was:
https://issues.apache.org/jira/browse/GERONIMO-3423
-Donald
Donald
On Sep 25, 2007, at 7:38 AM, Kevan Miller wrote:
One thing I've noticed -- the default JNDI name for EJB's has been
changed in OpenEJB. So, there is a compatibility issue with 2.0.1.
We might be able to configure how OpenEJB generates this default to
maintain backward compatibility.
--- Kevan Miller [EMAIL PROTECTED] wrote:
On Sep 20, 2007, at 8:38 AM, Donald Woods wrote:
I see that Anita has attached some patches for the MEJB problem. We
need to get some eyes on these...
David J's changes to openejb and geronimo-openejb-builder [1] are
required for MEJB
On Sep 24, 2007, at 8:52 AM, Anita Kulshreshtha wrote:
--- Kevan Miller [EMAIL PROTECTED] wrote:
On Sep 20, 2007, at 8:38 AM, Donald Woods wrote:
I see that Anita has attached some patches for the MEJB problem. We
need to get some eyes on these...
David J's changes to openejb and
Donald Woods wrote:
Agree.
There are some recent fixes in txmanager and javamail which we should
also try to include. The Genesis project should also be updated, as
it sets maven-compiler-plugin to 1.4 for the JDK src and targets.
Are you referring to the javamail changes I checked in over
OK, thanks for the clarification. Guess it can wait for a future release when
there are more updates included.
-Donald
Rick McGuire wrote:
Donald Woods wrote:
Agree.
There are some recent fixes in txmanager and javamail which we should
also try to include. The Genesis project should also
Also, the changes in txmanager aren't enough to warrant another components
release. The txmanager change was only to fix a misspelling in an exception
message...
-Donald
Donald Woods wrote:
Agree.
There are some recent fixes in txmanager and javamail which we should
also try to include.
On Sep 20, 2007, at 8:38 AM, Donald Woods wrote:
Also, the changes in txmanager aren't enough to warrant another
components release. The txmanager change was only to fix a
misspelling in an exception message...
Ya. However, there was a Transaction Recovery jira opened. I'm going
to
Agree.
There are some recent fixes in txmanager and javamail which we should also try
to include. The Genesis project should also be updated, as it sets
maven-compiler-plugin to 1.4 for the JDK src and targets.
I've got one or two patches that I'd like to get in, which I'm not going to
get
Can we also get an updated TranQL release, to pickup Lin's updated Oracle fix
in GERONIMO-2188 and finally release the DB2 vendor files? I'd be glad to
help with those, too.
-Donald
Kevan Miller wrote:
All,
I think it's time to start rolling out a 2.0.2 release. There have been
a number of
I thought of verifying whether 2.0.2 will have the fix for
https://issues.apache.org/jira/browse/GERONIMO-3380
(Derby embedded database pool created from console doesn't work) but I am
getting too late.
Thanks,
Shiva
On 9/14/07, Kevan Miller [EMAIL PROTECTED] wrote:
All,
I think it's time to
On Sep 14, 2007, at 2:55 AM, Kevan Miller wrote:
All,
I think it's time to start rolling out a 2.0.2 release. There have
been a number of fixes in response to user issues, since 2.0.1.
Time, I think, to make these available in a release. We'd also be
able to make use of released versions
+1 on the release
+1 on Kevan as RM
Also, I'd like to help out on TCK testing. I've never done it before
but I have sent in my NDA.
Matt Hogstrom wrote:
On Sep 14, 2007, at 2:55 AM, Kevan Miller wrote:
All,
I think it's time to start rolling out a 2.0.2 release. There have
been a number
Moved from another mail thread...
On 9/17/07, David Jencks [EMAIL PROTECTED] wrote:
I'm starting to wonder what the goal for 2.0.2 is. I kinda thought
that a x.y.z where z 0 was a bugfix-only release of x.y.z-1 but I
think some new features are going into 2.0.2... IIUC Vamsi is
applying an
All,
I think it's time to start rolling out a 2.0.2 release. There have
been a number of fixes in response to user issues, since 2.0.1. Time,
I think, to make these available in a release. We'd also be able to
make use of released versions of OpenJPA, Axis2, and hopefully
OpenEjb,
On 9/14/07, Kevan Miller [EMAIL PROTECTED] wrote:
All,
I think it's time to start rolling out a 2.0.2 release. There have
been a number of fixes in response to user issues, since 2.0.1. Time,
I think, to make these available in a release. We'd also be able to
make use of released versions of
Kevan,
I have one remaining task to do for 2.0.2. I would like to update the
version of CXF to 2.0.1 (or 2.0.2 if it is released really soon). Just
need to verify first if it is all good from TCK standpoint.
Jarek
On 9/14/07, Kevan Miller [EMAIL PROTECTED] wrote:
All,
I think it's time to
Kevan Miller wrote:
All,
I think it's time to start rolling out a 2.0.2 release. There have been
a number of fixes in response to user issues, since 2.0.1. Time, I
think, to make these available in a release. We'd also be able to make
use of released versions of OpenJPA, Axis2, and hopefully
46 matches
Mail list logo
