You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Joe Bohn <jo...@earthlink.net> on 2008/03/11 16:53:35 UTC
[DISCUSS] Geronimo 2.1.1 release
I think it's about time we got a 2.1.1 release out. The main motivation
is to deliver a fix for the PortletSecurityException when using https on
the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855).
but there are a lot of other fixes that have been integrated as well.
The TCK looked good with a recent run ... so I think that should not be
an issue.
As far as snapshots go, it looks like we're now pulling in a snapshot
for javamail that we would need to resolve
(geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one.
Are there any other changes/fixes that we should be looking to include
prior to a release?
I am willing to get my feet wet as the release manager unless somebody
else wants to pick it up.
Joe
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by David Jencks <da...@yahoo.com>.
On Mar 12, 2008, at 8:04 AM, Joe Bohn wrote:
> David Jencks wrote:
>> There are a couple things I want to backport from trunk
>> - archetypes
>> - log4j app config gbean (would be good to find out if it works)
>> - ?
>> Also it would be great to use the genesis 1.4 if it ever gets
>> released. On the other hand this might be too big a change....
>> we'll have to experiment.
>
> I assume you mean just upgrading to genesis 1.4 and not attempting
> to release using the maven-release-plugin ... right? Is it a big
> change to move up to genesis 1.4 without changing the release process?
>
You get generated legal files included automatically unless you turn
them off (not sure how). I"m not sure how realistic it is for 2.1.1
to use genesis 1.4 but.... it turns out the car plugin is finicky and
tends to pull in genesis 1.3 or earlier unless you do something
tricky with profiles.
thanks
david jencks
> Joe
>
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Joe Bohn <jo...@earthlink.net>.
David Jencks wrote:
>
> There are a couple things I want to backport from trunk
> - archetypes
> - log4j app config gbean (would be good to find out if it works)
> - ?
>
> Also it would be great to use the genesis 1.4 if it ever gets released.
> On the other hand this might be too big a change.... we'll have to
> experiment.
I assume you mean just upgrading to genesis 1.4 and not attempting to
release using the maven-release-plugin ... right? Is it a big change to
move up to genesis 1.4 without changing the release process?
Joe
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by David Jencks <da...@yahoo.com>.
On Mar 11, 2008, at 8:53 AM, Joe Bohn wrote:
> I think it's about time we got a 2.1.1 release out. The main
> motivation is to deliver a fix for the PortletSecurityException
> when using https on the admin console (https://issues.apache.org/
> jira/browse/GERONIMO-3855). but there are a lot of other fixes that
> have been integrated as well.
>
> The TCK looked good with a recent run ... so I think that should
> not be an issue.
>
> As far as snapshots go, it looks like we're now pulling in a
> snapshot for javamail that we would need to resolve (geronimo-
> javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one.
>
> Are there any other changes/fixes that we should be looking to
> include prior to a release?
>
> I am willing to get my feet wet as the release manager unless
> somebody else wants to pick it up.
There are a couple things I want to backport from trunk
- archetypes
- log4j app config gbean (would be good to find out if it works)
- ?
Also it would be great to use the genesis 1.4 if it ever gets
released. On the other hand this might be too big a change.... we'll
have to experiment.
thanks
david jencks
>
> Joe
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Joe Bohn <jo...@earthlink.net>.
Vasily Zakharov wrote:
> Another question I can remind of is in G2.0.2 we had
> tranql-connector-derby-embed-xa version 1.4, and in G2.1 it's version
> 1.3. Probably this should be corrected for G2.1.1.
It looks like Donald updated these earlier this month. in branches/2.1
(2.1.1-SNAPSHOT). That did get me to check the other
tranql-connector-* dependencies though for mysql, oracle, and
postgresql. It looks to me like these are all now using the latest
versions available.
Thanks,
Joe
>
> Vasily
>
>
> On Tue, Mar 11, 2008 at 6:53 PM, Joe Bohn <jo...@earthlink.net> wrote:
>> I think it's about time we got a 2.1.1 release out. The main motivation
>> is to deliver a fix for the PortletSecurityException when using https on
>> the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855).
>> but there are a lot of other fixes that have been integrated as well.
>>
>> The TCK looked good with a recent run ... so I think that should not be
>> an issue.
>>
>> As far as snapshots go, it looks like we're now pulling in a snapshot
>> for javamail that we would need to resolve
>> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one.
>>
>> Are there any other changes/fixes that we should be looking to include
>> prior to a release?
>>
>> I am willing to get my feet wet as the release manager unless somebody
>> else wants to pick it up.
>>
>> Joe
>>
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Vasily Zakharov <vm...@apache.org>.
Another question I can remind of is in G2.0.2 we had
tranql-connector-derby-embed-xa version 1.4, and in G2.1 it's version
1.3. Probably this should be corrected for G2.1.1.
Vasily
On Tue, Mar 11, 2008 at 6:53 PM, Joe Bohn <jo...@earthlink.net> wrote:
> I think it's about time we got a 2.1.1 release out. The main motivation
> is to deliver a fix for the PortletSecurityException when using https on
> the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855).
> but there are a lot of other fixes that have been integrated as well.
>
> The TCK looked good with a recent run ... so I think that should not be
> an issue.
>
> As far as snapshots go, it looks like we're now pulling in a snapshot
> for javamail that we would need to resolve
> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one.
>
> Are there any other changes/fixes that we should be looking to include
> prior to a release?
>
> I am willing to get my feet wet as the release manager unless somebody
> else wants to pick it up.
>
> Joe
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Donald Woods <dw...@apache.org>.
We also need to update our pinned Yoko jars from the current 1.0-r633547
to at least 1.0-r643498, which includes a fix for some TCK failures on
Windows....
-Donald
Joe Bohn wrote:
> I think it's about time we got a 2.1.1 release out. The main motivation
> is to deliver a fix for the PortletSecurityException when using https on
> the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855).
> but there are a lot of other fixes that have been integrated as well.
>
> The TCK looked good with a recent run ... so I think that should not be
> an issue.
>
> As far as snapshots go, it looks like we're now pulling in a snapshot
> for javamail that we would need to resolve
> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only
> one.
>
> Are there any other changes/fixes that we should be looking to include
> prior to a release?
>
> I am willing to get my feet wet as the release manager unless somebody
> else wants to pick it up.
>
> Joe
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Hernan Cunico <hc...@gmail.com>.
Joe Bohn wrote:
>
> I created a wiki page to keep track of these items. You can find it
> here (at least until Hernan decides that it should be in a different
> location :-) ).
yah, could you move it 3/4 of an inch to the right and 7/8 down pls !? :P
Cheers!
Hernan
>
> http://cwiki.apache.org/GMOxPMGT/geronimo-211-release-work-items-status.html
>
>
> Joe
>
>
>
> Joe Bohn wrote:
>> I think it's about time we got a 2.1.1 release out. The main
>> motivation is to deliver a fix for the PortletSecurityException when
>> using https on the admin console
>> (https://issues.apache.org/jira/browse/GERONIMO-3855). but there are a
>> lot of other fixes that have been integrated as well.
>>
>> The TCK looked good with a recent run ... so I think that should not
>> be an issue.
>>
>> As far as snapshots go, it looks like we're now pulling in a snapshot
>> for javamail that we would need to resolve
>> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the
>> only one.
>>
>> Are there any other changes/fixes that we should be looking to include
>> prior to a release?
>>
>> I am willing to get my feet wet as the release manager unless somebody
>> else wants to pick it up.
>>
>> Joe
>>
>
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Joe Bohn <jo...@earthlink.net>.
I created a wiki page to keep track of these items. You can find it
here (at least until Hernan decides that it should be in a different
location :-) ).
http://cwiki.apache.org/GMOxPMGT/geronimo-211-release-work-items-status.html
Joe
Joe Bohn wrote:
> I think it's about time we got a 2.1.1 release out. The main motivation
> is to deliver a fix for the PortletSecurityException when using https on
> the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855).
> but there are a lot of other fixes that have been integrated as well.
>
> The TCK looked good with a recent run ... so I think that should not be
> an issue.
>
> As far as snapshots go, it looks like we're now pulling in a snapshot
> for javamail that we would need to resolve
> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only
> one.
>
> Are there any other changes/fixes that we should be looking to include
> prior to a release?
>
> I am willing to get my feet wet as the release manager unless somebody
> else wants to pick it up.
>
> Joe
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Kevan Miller <ke...@gmail.com>.
On Mar 11, 2008, at 11:53 AM, Joe Bohn wrote:
> I think it's about time we got a 2.1.1 release out. The main
> motivation is to deliver a fix for the PortletSecurityException when
> using https on the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855
> ). but there are a lot of other fixes that have been integrated as
> well.
>
> The TCK looked good with a recent run ... so I think that should not
> be an issue.
>
> As far as snapshots go, it looks like we're now pulling in a
> snapshot for javamail that we would need to resolve (geronimo-
> javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one.
>
> Are there any other changes/fixes that we should be looking to
> include prior to a release?
>
> I am willing to get my feet wet as the release manager unless
> somebody else wants to pick it up.
That'd be great, Joe.
I definitely think it's time to get rolling on 2.1.1.
I see David B has started a release vote for OpenEJB 3.0. I'd like to
pull that in, if possible (we'll want to get a TCK run using this
version, regardless).
--kevan
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Jason Warner <ja...@gmail.com>.
On Thu, Mar 13, 2008 at 11:56 PM, Jason Warner <ja...@gmail.com> wrote:
>
>
> On Thu, Mar 13, 2008 at 5:08 PM, Joe Bohn <jo...@earthlink.net> wrote:
>
> > Ok, so here is the list of things that I think were mentioned for
> > inclusion in a 2.1.1 release (those that were not already complete when
> > this discussion began).
> >
> > Am I missing anything from the required list or are there items that
> > should move up from the Optional list (or down from required)?
> >
> > My take is that once we have everything under "Required" completed we
> > can start the release process. Anything from the Optional list that can
> > make it in is gravy. We need to decide when to start to lock things
> > down, but in general I think we all know that we are getting close so
> > please be careful what goes into the 2.1 branch now.
> >
> >
> >
> > Required:
> > - GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. -
> > There are patches integrated for this. Is there more to be done? Joe
> > Leong
> > - GERONIMO-3871 archetypes for plugin and assembly. - David has already
> > completed this.
> > - GERONIMO-3898 log4j app config gbean. - David has already completed
> > this.
> > - GERONIMO-3902 start-server overrides. - Jason are you posting a patch
> > for this?
>
>
> I got a bit sidetracked Joe, but I'm back on it. I think I've got a
> solution and will get a patch up tomorrow once I've verified it.
>
>
Patch has been uploaded. Please see the patch comments for more detail in
regards to the fix.
> > - GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated
> > a fix - outstanding question by Jarek
> > - GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated
> > this ... not sure if there is more work remaining.
> > - GERONIMO-3858 start-server.bat fails if space in dir - no owner
> > - GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi
> > assigned, still open
> > - GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned. I'm
> > not convinced this is a "must-have".
> > - GERONIMO-3887 bad config install for plugin causes new installs to
> > fail. Joe Leong - are you planning to provide a patch? I'm not
> > convinced this is a "must-have"
> > - GERONIMO-3896 error processing HEAD method by default HttpServlet.
> > David has fixed this in the servlet spec and it's up for a vote. We
> > need to update 2.1.1 to use this spec when final.
> > - GERONIMO-3906 start-server uses hard-coded credentials. This seems
> > important. Is anybody working on this (nobody is assigned).
> > - GERONIMO-3918 upgrade to WADI 2.0-M9. Donald has already completed
> > this.
> >
> >
> >
> >
> > Optional:
> > - leverage genesis 1.4
> > - OpenEJB 3.0 - currently up for a vote - looks promising. I will give
> > it a try with 2.1.1-SNAPSHOT. I think this should possibly move up to
> > required (assuming no big issues are found).
> > - GERONIMO-3432 console wizard to generate openejb-jar.xml
> > - GERONIMO-3503 db pool wizard creates plans only for local-transactions
> > - GERONIMO-3719 monitoring agent uses sun classes
> > - GERONIMO-3759 tomcat clustering, no gbeans for adding static members
> > - GERONIMO-3783 mdb delivery problem - this seems kinda important -
> > should we move it up?
> > - GERONIMO-3806 extraneous warning messages for ejb resource-env-def
> > deploy
> > - GERONIMO-3811 ejb server portlet
> > - GERONIMO-3814 NPE in GBeanOverride
> > - GERONIMO-3819 updates to JMS resource portlet
> > - GERONIMO-3823 document the SystemPropertyGBean
> > - GERONIMO-3879 webaccess log viewer with multiple server instances has
> > issues.
> > - GERONIMO-3900 runtime support for non-Sun JVMs.
> > - GERONIMO-3901 security realms portlet missing encoding option
> >
> >
> > Joe
> >
>
>
>
> --
> ~Jason Warner
--
~Jason Warner
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Jason Warner <ja...@gmail.com>.
On Thu, Mar 13, 2008 at 5:08 PM, Joe Bohn <jo...@earthlink.net> wrote:
> Ok, so here is the list of things that I think were mentioned for
> inclusion in a 2.1.1 release (those that were not already complete when
> this discussion began).
>
> Am I missing anything from the required list or are there items that
> should move up from the Optional list (or down from required)?
>
> My take is that once we have everything under "Required" completed we
> can start the release process. Anything from the Optional list that can
> make it in is gravy. We need to decide when to start to lock things
> down, but in general I think we all know that we are getting close so
> please be careful what goes into the 2.1 branch now.
>
>
>
> Required:
> - GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. -
> There are patches integrated for this. Is there more to be done? Joe
> Leong
> - GERONIMO-3871 archetypes for plugin and assembly. - David has already
> completed this.
> - GERONIMO-3898 log4j app config gbean. - David has already completed
> this.
> - GERONIMO-3902 start-server overrides. - Jason are you posting a patch
> for this?
I got a bit sidetracked Joe, but I'm back on it. I think I've got a
solution and will get a patch up tomorrow once I've verified it.
> - GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated
> a fix - outstanding question by Jarek
> - GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated
> this ... not sure if there is more work remaining.
> - GERONIMO-3858 start-server.bat fails if space in dir - no owner
> - GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi
> assigned, still open
> - GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned. I'm
> not convinced this is a "must-have".
> - GERONIMO-3887 bad config install for plugin causes new installs to
> fail. Joe Leong - are you planning to provide a patch? I'm not
> convinced this is a "must-have"
> - GERONIMO-3896 error processing HEAD method by default HttpServlet.
> David has fixed this in the servlet spec and it's up for a vote. We
> need to update 2.1.1 to use this spec when final.
> - GERONIMO-3906 start-server uses hard-coded credentials. This seems
> important. Is anybody working on this (nobody is assigned).
> - GERONIMO-3918 upgrade to WADI 2.0-M9. Donald has already completed
> this.
>
>
>
>
> Optional:
> - leverage genesis 1.4
> - OpenEJB 3.0 - currently up for a vote - looks promising. I will give
> it a try with 2.1.1-SNAPSHOT. I think this should possibly move up to
> required (assuming no big issues are found).
> - GERONIMO-3432 console wizard to generate openejb-jar.xml
> - GERONIMO-3503 db pool wizard creates plans only for local-transactions
> - GERONIMO-3719 monitoring agent uses sun classes
> - GERONIMO-3759 tomcat clustering, no gbeans for adding static members
> - GERONIMO-3783 mdb delivery problem - this seems kinda important -
> should we move it up?
> - GERONIMO-3806 extraneous warning messages for ejb resource-env-def
> deploy
> - GERONIMO-3811 ejb server portlet
> - GERONIMO-3814 NPE in GBeanOverride
> - GERONIMO-3819 updates to JMS resource portlet
> - GERONIMO-3823 document the SystemPropertyGBean
> - GERONIMO-3879 webaccess log viewer with multiple server instances has
> issues.
> - GERONIMO-3900 runtime support for non-Sun JVMs.
> - GERONIMO-3901 security realms portlet missing encoding option
>
>
> Joe
>
--
~Jason Warner
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Joe Bohn <jo...@earthlink.net>.
Shiva Kumar H R wrote:
> "GERONIMO-3432 console wizard to generate openejb-jar.xml" will only be
> ready by G2.2. Sorry about that.
NP ... it was on the optional list anyway.
>
> I will fix "GERONIMO-3759 tomcat clustering, no gbeans for adding static
> members" by next week.
>
> I would like the following additional ones to get into "Required" list
> of G2.1.1. I will fix them utmost by next Friday! (or will it be too late?)
> 1) GERONIMO-3843 Plan creator fails to create plan and to deploy
> 2) GERONIMO-3850 Plan Creator suppresses exceptions rather than showing
> it to user
> 3) GERONIMO-3851 Plan Creator cannot recognize classes inside compressed
> JARs of WEB-INF/lib
These all sound like good things to fix. I think Friday should be ok.
We have a number of things to fix that will take probably about a week.
I think I'm going to make a wiki page to keep track of all the items for
2.1.1. In addition to what I listed earlier I think we need a build a
new private Tomcat image and eliminate the dependency on the
geronimo-javamail-1.4 snapshot by either releasing it or moving back to 1.3.
I think we should aim to branch on next Friday, 3/21 and shot to have
something to vote on my the following week.
Joe
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Shiva Kumar H R <sh...@gmail.com>.
GERONIMO-3843 (Plan creator fails to create plan and to deploy) &
GERONIMO-3850 (Plan Creator suppresses exceptions rather than showing it to
user) are fixed.
GERONIMO-3851 (Plan Creator cannot recognize classes inside compressed JARs
of WEB-INF/lib) involves lots of changes and I would like these to go into
G2.2 instead.
And I haven't been able to implement GERONIMO-3759 (tomcat clustering, no
gbeans for adding static members) - still facing some problems. Can someone
look into this?
--
Thanks,
Shiva
On Fri, Mar 14, 2008 at 6:08 PM, Shiva Kumar H R <sh...@gmail.com> wrote:
> "GERONIMO-3432 console wizard to generate openejb-jar.xml" will only be
> ready by G2.2. Sorry about that.
>
> I will fix "GERONIMO-3759 tomcat clustering, no gbeans for adding static
> members" by next week.
>
> I would like the following additional ones to get into "Required" list of
> G2.1.1. I will fix them utmost by next Friday! (or will it be too late?)
> 1) GERONIMO-3843 Plan creator fails to create plan and to deploy
> 2) GERONIMO-3850 Plan Creator suppresses exceptions rather than showing it
> to user
> 3) GERONIMO-3851 Plan Creator cannot recognize classes inside compressed
> JARs of WEB-INF/lib
>
> --
> Thanks,
> Shiva
>
> On Fri, Mar 14, 2008 at 2:38 AM, Joe Bohn <jo...@earthlink.net> wrote:
>
> > Ok, so here is the list of things that I think were mentioned for
> > inclusion in a 2.1.1 release (those that were not already complete when
> > this discussion began).
> >
> > Am I missing anything from the required list or are there items that
> > should move up from the Optional list (or down from required)?
> >
> > My take is that once we have everything under "Required" completed we
> > can start the release process. Anything from the Optional list that can
> > make it in is gravy. We need to decide when to start to lock things
> > down, but in general I think we all know that we are getting close so
> > please be careful what goes into the 2.1 branch now.
> >
> >
> >
> > Required:
> > - GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. -
> > There are patches integrated for this. Is there more to be done? Joe
> > Leong
> > - GERONIMO-3871 archetypes for plugin and assembly. - David has already
> > completed this.
> > - GERONIMO-3898 log4j app config gbean. - David has already completed
> > this.
> > - GERONIMO-3902 start-server overrides. - Jason are you posting a patch
> > for this?
> > - GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated
> > a fix - outstanding question by Jarek
> > - GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated
> > this ... not sure if there is more work remaining.
> > - GERONIMO-3858 start-server.bat fails if space in dir - no owner
> > - GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi
> > assigned, still open
> > - GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned. I'm
> > not convinced this is a "must-have".
> > - GERONIMO-3887 bad config install for plugin causes new installs to
> > fail. Joe Leong - are you planning to provide a patch? I'm not
> > convinced this is a "must-have"
> > - GERONIMO-3896 error processing HEAD method by default HttpServlet.
> > David has fixed this in the servlet spec and it's up for a vote. We
> > need to update 2.1.1 to use this spec when final.
> > - GERONIMO-3906 start-server uses hard-coded credentials. This seems
> > important. Is anybody working on this (nobody is assigned).
> > - GERONIMO-3918 upgrade to WADI 2.0-M9. Donald has already completed
> > this.
> >
> >
> >
> >
> > Optional:
> > - leverage genesis 1.4
> > - OpenEJB 3.0 - currently up for a vote - looks promising. I will give
> > it a try with 2.1.1-SNAPSHOT. I think this should possibly move up to
> > required (assuming no big issues are found).
> > - GERONIMO-3432 console wizard to generate openejb-jar.xml
> > - GERONIMO-3503 db pool wizard creates plans only for local-transactions
> > - GERONIMO-3719 monitoring agent uses sun classes
> > - GERONIMO-3759 tomcat clustering, no gbeans for adding static members
> > - GERONIMO-3783 mdb delivery problem - this seems kinda important -
> > should we move it up?
> > - GERONIMO-3806 extraneous warning messages for ejb resource-env-def
> > deploy
> > - GERONIMO-3811 ejb server portlet
> > - GERONIMO-3814 NPE in GBeanOverride
> > - GERONIMO-3819 updates to JMS resource portlet
> > - GERONIMO-3823 document the SystemPropertyGBean
> > - GERONIMO-3879 webaccess log viewer with multiple server instances has
> > issues.
> > - GERONIMO-3900 runtime support for non-Sun JVMs.
> > - GERONIMO-3901 security realms portlet missing encoding option
> >
> >
> > Joe
> >
>
>
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Shiva Kumar H R <sh...@gmail.com>.
"GERONIMO-3432 console wizard to generate openejb-jar.xml" will only be
ready by G2.2. Sorry about that.
I will fix "GERONIMO-3759 tomcat clustering, no gbeans for adding static
members" by next week.
I would like the following additional ones to get into "Required" list of
G2.1.1. I will fix them utmost by next Friday! (or will it be too late?)
1) GERONIMO-3843 Plan creator fails to create plan and to deploy
2) GERONIMO-3850 Plan Creator suppresses exceptions rather than showing it
to user
3) GERONIMO-3851 Plan Creator cannot recognize classes inside compressed
JARs of WEB-INF/lib
--
Thanks,
Shiva
On Fri, Mar 14, 2008 at 2:38 AM, Joe Bohn <jo...@earthlink.net> wrote:
> Ok, so here is the list of things that I think were mentioned for
> inclusion in a 2.1.1 release (those that were not already complete when
> this discussion began).
>
> Am I missing anything from the required list or are there items that
> should move up from the Optional list (or down from required)?
>
> My take is that once we have everything under "Required" completed we
> can start the release process. Anything from the Optional list that can
> make it in is gravy. We need to decide when to start to lock things
> down, but in general I think we all know that we are getting close so
> please be careful what goes into the 2.1 branch now.
>
>
>
> Required:
> - GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. -
> There are patches integrated for this. Is there more to be done? Joe
> Leong
> - GERONIMO-3871 archetypes for plugin and assembly. - David has already
> completed this.
> - GERONIMO-3898 log4j app config gbean. - David has already completed
> this.
> - GERONIMO-3902 start-server overrides. - Jason are you posting a patch
> for this?
> - GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated
> a fix - outstanding question by Jarek
> - GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated
> this ... not sure if there is more work remaining.
> - GERONIMO-3858 start-server.bat fails if space in dir - no owner
> - GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi
> assigned, still open
> - GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned. I'm
> not convinced this is a "must-have".
> - GERONIMO-3887 bad config install for plugin causes new installs to
> fail. Joe Leong - are you planning to provide a patch? I'm not
> convinced this is a "must-have"
> - GERONIMO-3896 error processing HEAD method by default HttpServlet.
> David has fixed this in the servlet spec and it's up for a vote. We
> need to update 2.1.1 to use this spec when final.
> - GERONIMO-3906 start-server uses hard-coded credentials. This seems
> important. Is anybody working on this (nobody is assigned).
> - GERONIMO-3918 upgrade to WADI 2.0-M9. Donald has already completed
> this.
>
>
>
>
> Optional:
> - leverage genesis 1.4
> - OpenEJB 3.0 - currently up for a vote - looks promising. I will give
> it a try with 2.1.1-SNAPSHOT. I think this should possibly move up to
> required (assuming no big issues are found).
> - GERONIMO-3432 console wizard to generate openejb-jar.xml
> - GERONIMO-3503 db pool wizard creates plans only for local-transactions
> - GERONIMO-3719 monitoring agent uses sun classes
> - GERONIMO-3759 tomcat clustering, no gbeans for adding static members
> - GERONIMO-3783 mdb delivery problem - this seems kinda important -
> should we move it up?
> - GERONIMO-3806 extraneous warning messages for ejb resource-env-def
> deploy
> - GERONIMO-3811 ejb server portlet
> - GERONIMO-3814 NPE in GBeanOverride
> - GERONIMO-3819 updates to JMS resource portlet
> - GERONIMO-3823 document the SystemPropertyGBean
> - GERONIMO-3879 webaccess log viewer with multiple server instances has
> issues.
> - GERONIMO-3900 runtime support for non-Sun JVMs.
> - GERONIMO-3901 security realms portlet missing encoding option
>
>
> Joe
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Hernan Cunico <hc...@gmail.com>.
I would like add to the *Required* having a little bit more complete v2.1 documentation.
There are still a lot of topics to cover (from scratch) and to verify carried over content from previous releases.
Cheers!
Hernan
Joe Bohn wrote:
> Ok, so here is the list of things that I think were mentioned for
> inclusion in a 2.1.1 release (those that were not already complete when
> this discussion began).
>
> Am I missing anything from the required list or are there items that
> should move up from the Optional list (or down from required)?
>
> My take is that once we have everything under "Required" completed we
> can start the release process. Anything from the Optional list that can
> make it in is gravy. We need to decide when to start to lock things
> down, but in general I think we all know that we are getting close so
> please be careful what goes into the 2.1 branch now.
>
>
>
> Required:
> - GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. -
> There are patches integrated for this. Is there more to be done? Joe
> Leong
> - GERONIMO-3871 archetypes for plugin and assembly. - David has already
> completed this.
> - GERONIMO-3898 log4j app config gbean. - David has already completed this.
> - GERONIMO-3902 start-server overrides. - Jason are you posting a patch
> for this?
> - GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated
> a fix - outstanding question by Jarek
> - GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated
> this ... not sure if there is more work remaining.
> - GERONIMO-3858 start-server.bat fails if space in dir - no owner
> - GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi
> assigned, still open
> - GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned. I'm
> not convinced this is a "must-have".
> - GERONIMO-3887 bad config install for plugin causes new installs to
> fail. Joe Leong - are you planning to provide a patch? I'm not
> convinced this is a "must-have"
> - GERONIMO-3896 error processing HEAD method by default HttpServlet.
> David has fixed this in the servlet spec and it's up for a vote. We
> need to update 2.1.1 to use this spec when final.
> - GERONIMO-3906 start-server uses hard-coded credentials. This seems
> important. Is anybody working on this (nobody is assigned).
> - GERONIMO-3918 upgrade to WADI 2.0-M9. Donald has already completed this.
>
>
>
>
> Optional:
> - leverage genesis 1.4
> - OpenEJB 3.0 - currently up for a vote - looks promising. I will give
> it a try with 2.1.1-SNAPSHOT. I think this should possibly move up to
> required (assuming no big issues are found).
> - GERONIMO-3432 console wizard to generate openejb-jar.xml
> - GERONIMO-3503 db pool wizard creates plans only for local-transactions
> - GERONIMO-3719 monitoring agent uses sun classes
> - GERONIMO-3759 tomcat clustering, no gbeans for adding static members
> - GERONIMO-3783 mdb delivery problem - this seems kinda important -
> should we move it up?
> - GERONIMO-3806 extraneous warning messages for ejb resource-env-def deploy
> - GERONIMO-3811 ejb server portlet
> - GERONIMO-3814 NPE in GBeanOverride
> - GERONIMO-3819 updates to JMS resource portlet
> - GERONIMO-3823 document the SystemPropertyGBean
> - GERONIMO-3879 webaccess log viewer with multiple server instances has
> issues.
> - GERONIMO-3900 runtime support for non-Sun JVMs.
> - GERONIMO-3901 security realms portlet missing encoding option
>
>
> Joe
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by David Jencks <da...@yahoo.com>.
On Mar 13, 2008, at 2:08 PM, Joe Bohn wrote:
> Ok, so here is the list of things that I think were mentioned for
> inclusion in a 2.1.1 release (those that were not already complete
> when this discussion began).
>
> Am I missing anything from the required list or are there items
> that should move up from the Optional list (or down from required)?
>
> My take is that once we have everything under "Required" completed
> we can start the release process. Anything from the Optional list
> that can make it in is gravy. We need to decide when to start to
> lock things down, but in general I think we all know that we are
> getting close so please be careful what goes into the 2.1 branch now.
>
>
>
> Required:
> - GERONIMO-3781 PluginInstaller CRSF when installing a new plugin.
> - There are patches integrated for this. Is there more to be
> done? Joe Leong
> - GERONIMO-3871 archetypes for plugin and assembly. - David has
> already completed this.
> - GERONIMO-3898 log4j app config gbean. - David has already
> completed this.
> - GERONIMO-3902 start-server overrides. - Jason are you posting a
> patch for this?
> - GERONIMO-3833 monitoring hard coded gbean names. - Viet has
> integrated a fix - outstanding question by Jarek
> - GERONIMO-3837 configure allowLinking attribute - Vamsi has
> integrated this ... not sure if there is more work remaining.
> - GERONIMO-3858 start-server.bat fails if space in dir - no owner
> - GERONIMO-3875 Derby authentication breaks DB viewer portlet. -
> Vamsi assigned, still open
> - GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned.
> I'm not convinced this is a "must-have".
Not a must have but very nice. I thought he'd pretty much figured
out how to do it -- if he's run out of time I can give some hints or
do it myself.
> - GERONIMO-3887 bad config install for plugin causes new installs
> to fail. Joe Leong - are you planning to provide a patch? I'm not
> convinced this is a "must-have"
I'm not sure it's practical to fix this without a big change in the
plugin mechanism. I don't think it's a must-have.
> - GERONIMO-3896 error processing HEAD method by default
> HttpServlet. David has fixed this in the servlet spec and it's up
> for a vote. We need to update 2.1.1 to use this spec when final.
> - GERONIMO-3906 start-server uses hard-coded credentials. This
> seems important. Is anybody working on this (nobody is assigned).
> - GERONIMO-3918 upgrade to WADI 2.0-M9. Donald has already
> completed this.
>
>
>
>
> Optional:
> - leverage genesis 1.4
> - OpenEJB 3.0 - currently up for a vote - looks promising. I will
> give it a try with 2.1.1-SNAPSHOT. I think this should possibly
> move up to required (assuming no big issues are found).
> - GERONIMO-3432 console wizard to generate openejb-jar.xml
> - GERONIMO-3503 db pool wizard creates plans only for local-
> transactions
> - GERONIMO-3719 monitoring agent uses sun classes
> - GERONIMO-3759 tomcat clustering, no gbeans for adding static members
> - GERONIMO-3783 mdb delivery problem - this seems kinda important -
> should we move it up?
It's not clear yet that this one is a bug. There is https://
issues.apache.org/activemq/browse/AMQ-1618 which I'm going to try to
get into amq shortly, but getting a release out may not be too quick.
>
> - GERONIMO-3806 extraneous warning messages for ejb resource-env-
> def deploy
> - GERONIMO-3811 ejb server portlet
> - GERONIMO-3814 NPE in GBeanOverride
> - GERONIMO-3819 updates to JMS resource portlet
> - GERONIMO-3823 document the SystemPropertyGBean
> - GERONIMO-3879 webaccess log viewer with multiple server instances
> has issues.
> - GERONIMO-3900 runtime support for non-Sun JVMs.
> - GERONIMO-3901 security realms portlet missing encoding option
>
Thanks very much for tracking this!
david jencks
>
> Joe
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Joe Bohn <jo...@earthlink.net>.
Ok, so here is the list of things that I think were mentioned for
inclusion in a 2.1.1 release (those that were not already complete when
this discussion began).
Am I missing anything from the required list or are there items that
should move up from the Optional list (or down from required)?
My take is that once we have everything under "Required" completed we
can start the release process. Anything from the Optional list that can
make it in is gravy. We need to decide when to start to lock things
down, but in general I think we all know that we are getting close so
please be careful what goes into the 2.1 branch now.
Required:
- GERONIMO-3781 PluginInstaller CRSF when installing a new plugin. -
There are patches integrated for this. Is there more to be done? Joe Leong
- GERONIMO-3871 archetypes for plugin and assembly. - David has already
completed this.
- GERONIMO-3898 log4j app config gbean. - David has already completed this.
- GERONIMO-3902 start-server overrides. - Jason are you posting a patch
for this?
- GERONIMO-3833 monitoring hard coded gbean names. - Viet has integrated
a fix - outstanding question by Jarek
- GERONIMO-3837 configure allowLinking attribute - Vamsi has integrated
this ... not sure if there is more work remaining.
- GERONIMO-3858 start-server.bat fails if space in dir - no owner
- GERONIMO-3875 Derby authentication breaks DB viewer portlet. - Vamsi
assigned, still open
- GERONIMO-3876 allow configuring JMX over SSL. - Vamsi assigned. I'm
not convinced this is a "must-have".
- GERONIMO-3887 bad config install for plugin causes new installs to
fail. Joe Leong - are you planning to provide a patch? I'm not
convinced this is a "must-have"
- GERONIMO-3896 error processing HEAD method by default HttpServlet.
David has fixed this in the servlet spec and it's up for a vote. We
need to update 2.1.1 to use this spec when final.
- GERONIMO-3906 start-server uses hard-coded credentials. This seems
important. Is anybody working on this (nobody is assigned).
- GERONIMO-3918 upgrade to WADI 2.0-M9. Donald has already completed this.
Optional:
- leverage genesis 1.4
- OpenEJB 3.0 - currently up for a vote - looks promising. I will give
it a try with 2.1.1-SNAPSHOT. I think this should possibly move up to
required (assuming no big issues are found).
- GERONIMO-3432 console wizard to generate openejb-jar.xml
- GERONIMO-3503 db pool wizard creates plans only for local-transactions
- GERONIMO-3719 monitoring agent uses sun classes
- GERONIMO-3759 tomcat clustering, no gbeans for adding static members
- GERONIMO-3783 mdb delivery problem - this seems kinda important -
should we move it up?
- GERONIMO-3806 extraneous warning messages for ejb resource-env-def deploy
- GERONIMO-3811 ejb server portlet
- GERONIMO-3814 NPE in GBeanOverride
- GERONIMO-3819 updates to JMS resource portlet
- GERONIMO-3823 document the SystemPropertyGBean
- GERONIMO-3879 webaccess log viewer with multiple server instances has
issues.
- GERONIMO-3900 runtime support for non-Sun JVMs.
- GERONIMO-3901 security realms portlet missing encoding option
Joe
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Joe Bohn <jo...@earthlink.net>.
Jason Warner wrote:
> I just opened https://issues.apache.org/jira/browse/GERONIMO-3902 the
> other day. I'd like to get a patch up for that and get it in. It's not
> really crucial as long as we note what the issue is, though.
I agree that it would be good to include a fix for this.
Joe
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Jason Warner <ja...@gmail.com>.
I just opened https://issues.apache.org/jira/browse/GERONIMO-3902 the other
day. I'd like to get a patch up for that and get it in. It's not really
crucial as long as we note what the issue is, though.
On Tue, Mar 11, 2008 at 12:12 PM, Vasily Zakharov <vm...@apache.org> wrote:
> Is there a chance OpenEJB 3.0 release will make it to 2.1.1?
>
> Vasily
>
>
> On Tue, Mar 11, 2008 at 6:53 PM, Joe Bohn <jo...@earthlink.net> wrote:
> > I think it's about time we got a 2.1.1 release out. The main motivation
> > is to deliver a fix for the PortletSecurityException when using https
> on
> > the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855
> ).
> > but there are a lot of other fixes that have been integrated as well.
> >
> > The TCK looked good with a recent run ... so I think that should not be
> > an issue.
> >
> > As far as snapshots go, it looks like we're now pulling in a snapshot
> > for javamail that we would need to resolve
> > (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only
> one.
> >
> > Are there any other changes/fixes that we should be looking to include
> > prior to a release?
> >
> > I am willing to get my feet wet as the release manager unless somebody
> > else wants to pick it up.
> >
> > Joe
> >
>
--
~Jason Warner
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Joe Bohn <jo...@earthlink.net>.
Vasily Zakharov wrote:
> Is there a chance OpenEJB 3.0 release will make it to 2.1.1?
It would be great if we could pick up an openejb 3.0 release (which
would include fixes for some issues recently discussed on this list).
Does anybody know the target for a 3.0 release of OpenEjb?
Joe
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Vasily Zakharov <vm...@apache.org>.
Is there a chance OpenEJB 3.0 release will make it to 2.1.1?
Vasily
On Tue, Mar 11, 2008 at 6:53 PM, Joe Bohn <jo...@earthlink.net> wrote:
> I think it's about time we got a 2.1.1 release out. The main motivation
> is to deliver a fix for the PortletSecurityException when using https on
> the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855).
> but there are a lot of other fixes that have been integrated as well.
>
> The TCK looked good with a recent run ... so I think that should not be
> an issue.
>
> As far as snapshots go, it looks like we're now pulling in a snapshot
> for javamail that we would need to resolve
> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one.
>
> Are there any other changes/fixes that we should be looking to include
> prior to a release?
>
> I am willing to get my feet wet as the release manager unless somebody
> else wants to pick it up.
>
> Joe
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Donald Woods <dw...@apache.org>.
Some JIRAs that I'd like to see in 2.l.1 -
3781, 3833, 3837, 3858, 3875, 3876, 3887, 3896, 3898, 3902, 3906
Nice to haves -
3432, 3503, 3719, 3759, 3783, 3806, 3811, 3814, 3819, 3823, 3871,
3879, 3900, 3901
-Donald
Joe Bohn wrote:
> I think it's about time we got a 2.1.1 release out. The main motivation
> is to deliver a fix for the PortletSecurityException when using https on
> the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855).
> but there are a lot of other fixes that have been integrated as well.
>
> The TCK looked good with a recent run ... so I think that should not be
> an issue.
>
> As far as snapshots go, it looks like we're now pulling in a snapshot
> for javamail that we would need to resolve
> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only
> one.
>
> Are there any other changes/fixes that we should be looking to include
> prior to a release?
>
> I am willing to get my feet wet as the release manager unless somebody
> else wants to pick it up.
>
> Joe
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by David Jencks <da...@yahoo.com>.
On Apr 3, 2008, at 9:02 AM, Joe Bohn wrote:
> Donald Woods wrote:
>> Also, it seems that we need an updated tranql-connector-db2-xa-1.2
>> build, to fix a known problem with the trace file setting.
>> See http://www.nabble.com/forum/ViewPost.jtp?
>> post=16404097&framed=y&skin=134
>
> Thanks Donald.
>
> I asked on that thread if updating to the newer connector actually
> resolved the issue.
>
> Does anybody happen to know if there is a release planned in the
> near future for this connector should it prove to be the solution
> for this issue? If not, how hard would it be to add create one (I
> guess that's a question for you David)? Also, I'm not sure how
> these connectors are typically released ... would we upgrade all of
> the connectors or just the db2-xa connector?
Just that one. I'll try for today or tomorrow. IIRC we haven't been
having votes on tranql stuff so I think I just need to review the
build state and release it.
thanks
david jencks
>
> Perhaps it would suffice to just include documentation on how to
> upgrade the connector to resolve the issue and deliver the released
> connector in 2.1.2 and/or 2.2.
>
> Joe
>
>> -Donald
>> Joe Bohn wrote:
>>> I think it's about time we got a 2.1.1 release out. The main
>>> motivation is to deliver a fix for the PortletSecurityException
>>> when using https on the admin console (https://issues.apache.org/
>>> jira/browse/GERONIMO-3855). but there are a lot of other fixes
>>> that have been integrated as well.
>>>
>>> The TCK looked good with a recent run ... so I think that should
>>> not be an issue.
>>>
>>> As far as snapshots go, it looks like we're now pulling in a
>>> snapshot for javamail that we would need to resolve (geronimo-
>>> javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one.
>>>
>>> Are there any other changes/fixes that we should be looking to
>>> include prior to a release?
>>>
>>> I am willing to get my feet wet as the release manager unless
>>> somebody else wants to pick it up.
>>>
>>> Joe
>>>
>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Joe Bohn <jo...@earthlink.net>.
Donald Woods wrote:
> Also, it seems that we need an updated tranql-connector-db2-xa-1.2
> build, to fix a known problem with the trace file setting.
>
> See
> http://www.nabble.com/forum/ViewPost.jtp?post=16404097&framed=y&skin=134
>
Thanks Donald.
I asked on that thread if updating to the newer connector actually
resolved the issue.
Does anybody happen to know if there is a release planned in the near
future for this connector should it prove to be the solution for this
issue? If not, how hard would it be to add create one (I guess that's a
question for you David)? Also, I'm not sure how these connectors are
typically released ... would we upgrade all of the connectors or just
the db2-xa connector?
Perhaps it would suffice to just include documentation on how to upgrade
the connector to resolve the issue and deliver the released connector in
2.1.2 and/or 2.2.
Joe
>
> -Donald
>
> Joe Bohn wrote:
>> I think it's about time we got a 2.1.1 release out. The main
>> motivation is to deliver a fix for the PortletSecurityException when
>> using https on the admin console
>> (https://issues.apache.org/jira/browse/GERONIMO-3855). but there are a
>> lot of other fixes that have been integrated as well.
>>
>> The TCK looked good with a recent run ... so I think that should not
>> be an issue.
>>
>> As far as snapshots go, it looks like we're now pulling in a snapshot
>> for javamail that we would need to resolve
>> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the
>> only one.
>>
>> Are there any other changes/fixes that we should be looking to include
>> prior to a release?
>>
>> I am willing to get my feet wet as the release manager unless somebody
>> else wants to pick it up.
>>
>> Joe
>>
Re: [DISCUSS] Geronimo 2.1.1 release
Posted by Donald Woods <dw...@apache.org>.
Also, it seems that we need an updated tranql-connector-db2-xa-1.2
build, to fix a known problem with the trace file setting.
See http://www.nabble.com/forum/ViewPost.jtp?post=16404097&framed=y&skin=134
-Donald
Joe Bohn wrote:
> I think it's about time we got a 2.1.1 release out. The main motivation
> is to deliver a fix for the PortletSecurityException when using https on
> the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855).
> but there are a lot of other fixes that have been integrated as well.
>
> The TCK looked good with a recent run ... so I think that should not be
> an issue.
>
> As far as snapshots go, it looks like we're now pulling in a snapshot
> for javamail that we would need to resolve
> (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only
> one.
>
> Are there any other changes/fixes that we should be looking to include
> prior to a release?
>
> I am willing to get my feet wet as the release manager unless somebody
> else wants to pick it up.
>
> Joe
>