You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Matt Hogstrom <ma...@hogstrom.org> on 2005/12/18 09:03:19 UTC
Release 1.0 New Build Available
I have rebuilt the 1.0 server with the following JIRA's incorporated and this
was at Committed revision 357442 of subversion.
The server started successfully on my system (Mac OS) for both Tomcat and Jetty.
I wiped out my Maven repo before rebuilding so to the best of my knowledge it
works on my system and should work on yours.
The images are available at http://people.apache.org/~hogstrom/geronimo-1.0
The files are:
geronimo-tomcat-j2ee-1.0-20051218.tar.gz
geronimo-tomcat-j2ee-1.0-20051218.zip
geronimo-jetty-j2ee-1.0-20051218.tar.gz
geronimo-jetty-j2ee-1.0-20051218.zip
Note: These files extract into ./geronimo-1.0 which is different than the file
name. Please ensure that any previous release of Geronimo installed in that
directory tree has been removed.
Please take time to download and run through the images and verify they start
and stop without errors (there are some known ActiveMQ errors at shutdown around
connection problems. I believe these can safely be ignored and will be fixed in
a near term release.)
Post comments back to the list and we'll incorporate the changes quickly and
keep the train moving.
I have not had time to download and retest these images to make sure they made
it up correctly. Any problems reply back to this thread.
Mr. Blevins and Mr. Jencks, I hate to impose on you but can you start a TCK run
on this build and barring any major issues this might be it so it would be good
to have verification of the build.
Thanks
- Matt
Here is the list of defects incorporated into this build.
Completed
GERONIMO-1363 - DayTrader still using old geronimo-spec files - applied by Matt
GERONIMO-1364 - update welcome pages to point at HTTP redirects in the
geronimo.apache.org site
GERONIMO-1372 - Exception during startup - TradeEJB - Fixed per Dain
GERONIMO-1373 - DB info portlet not working correctly - Applied by Matt
GERONIMO-1375 - Invalid login to console should not produce stack trace
GERONIMO-1377 - Startup Warning on tomcat - unknown default host. - Fixed by Jeff
Deferring to 1.1
GERONIMO-1371 - Geronimo startup/shutdown issues
Re: Release 1.0 New Build Available
Posted by Dave Colasurdo <da...@earthlink.net>.
Looks like the redirect at
http://geronimo.apache.org/redirects/additionalSamples.html needs to be
updated to the new location of the samples. A link to the new location
is shown on the old page.
Matt Hogstrom wrote:
> I have rebuilt the 1.0 server with the following JIRA's incorporated and
> this was at Committed revision 357442 of subversion.
>
> The server started successfully on my system (Mac OS) for both Tomcat
> and Jetty. I wiped out my Maven repo before rebuilding so to the best
> of my knowledge it works on my system and should work on yours.
>
> The images are available at http://people.apache.org/~hogstrom/geronimo-1.0
>
> The files are:
>
> geronimo-tomcat-j2ee-1.0-20051218.tar.gz
> geronimo-tomcat-j2ee-1.0-20051218.zip
>
> geronimo-jetty-j2ee-1.0-20051218.tar.gz
> geronimo-jetty-j2ee-1.0-20051218.zip
>
> Note: These files extract into ./geronimo-1.0 which is different than
> the file name. Please ensure that any previous release of Geronimo
> installed in that directory tree has been removed.
>
> Please take time to download and run through the images and verify they
> start and stop without errors (there are some known ActiveMQ errors at
> shutdown around connection problems. I believe these can safely be
> ignored and will be fixed in a near term release.)
>
> Post comments back to the list and we'll incorporate the changes quickly
> and keep the train moving.
>
> I have not had time to download and retest these images to make sure
> they made it up correctly. Any problems reply back to this thread.
>
> Mr. Blevins and Mr. Jencks, I hate to impose on you but can you start a
> TCK run on this build and barring any major issues this might be it so
> it would be good to have verification of the build.
>
> Thanks
>
> - Matt
>
> Here is the list of defects incorporated into this build.
>
> Completed
> GERONIMO-1363 - DayTrader still using old geronimo-spec files - applied
> by Matt
> GERONIMO-1364 - update welcome pages to point at HTTP redirects in the
> geronimo.apache.org site
> GERONIMO-1372 - Exception during startup - TradeEJB - Fixed per Dain
> GERONIMO-1373 - DB info portlet not working correctly - Applied by Matt
> GERONIMO-1375 - Invalid login to console should not produce stack trace
> GERONIMO-1377 - Startup Warning on tomcat - unknown default host. -
> Fixed by Jeff
>
> Deferring to 1.1
> GERONIMO-1371 - Geronimo startup/shutdown issues
>
>
>
Re: Realmless security. Was: Release 1.0 New Build Available
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
So after some IRC discussion, it looks like this is not on the table
for 1.0 (instead, we're looking at a simpler fix to reject deployments
on Jetty which have web.xml security but not geronimo-web.xml
security).
I tried for the fix described below and I could not get it to work in
the time I spent on it. I changed JettyWebAppContext to set a
JettyJAASRealm pointing to a non-existant Geronimo realm, and also to
construct a generic DefaultPrincipal. Then I had to change
SecurityContextBeforeAfter.obtainUser to not blow up if there was no
set of checked and excluded permissions specified. But it still ended
up generating a 403 for a web app with no security at all in
SecurityContextBeforeAfter.checkSecurityConstraints when it called
AccessControlContext.checkPermissions. So I think probably
JettyModuleBuilder needs to change to apply the right JACC stuff even
if no Geronimo security information is provided. But that's as far as
I got, so I'm not really sure.
If you can come up with a patch for this (for 1.0.1) that would be great.
Thanks,
Aaron
On 12/18/05, Greg Wilkins <gr...@mortbay.com> wrote:
> Aaron Mulder wrote:
> > Well it appears that Tomcat and Jetty handle this situation
> > differently (Tomcat: all secure pages locked down, Jetty: all secure
> > pages accessible to anybody), which is *definitely* a bug...
>
> If Jetty is not given a realm, but is given security constraints for a
> resources, it returns a "500 configuration error". So the Jetty plugin
> must either be giving Jetty a realm or not giving it the security
> constraints.
>
> From a quick look at JettyModuleBuilder, I think the security
> constraints are not being built if there is no security realm name.
>
> > But really, if the user put security settings in their web.xml, then
> > clearly they're expecting security to be applied. If we disable all
> > security because they missed a deployment plan or a deployment plan
> > setting, then I think that's a huge security problem. Gnerally
> > speaking, I think it's always best to fail to a more secure state, not
> > to fail to an "anybody authorized for anything" state. That's
> > certainly the behavior you'd expect from your bank.
>
> I agree - but then 1.0 is not going to be a real production release.
> I really think it should be called a 1.0RC.
>
> But anyway... I'm out for a few hours and if David has not fixed this by then,
> I'll work on a fix for trunk and we can then decide if that makes it for 1.0
>
> cheers
>
Realmless security. Was: Release 1.0 New Build Available
Posted by Greg Wilkins <gr...@mortbay.com>.
Aaron Mulder wrote:
> Well it appears that Tomcat and Jetty handle this situation
> differently (Tomcat: all secure pages locked down, Jetty: all secure
> pages accessible to anybody), which is *definitely* a bug...
If Jetty is not given a realm, but is given security constraints for a
resources, it returns a "500 configuration error". So the Jetty plugin
must either be giving Jetty a realm or not giving it the security
constraints.
>From a quick look at JettyModuleBuilder, I think the security
constraints are not being built if there is no security realm name.
> But really, if the user put security settings in their web.xml, then
> clearly they're expecting security to be applied. If we disable all
> security because they missed a deployment plan or a deployment plan
> setting, then I think that's a huge security problem. Gnerally
> speaking, I think it's always best to fail to a more secure state, not
> to fail to an "anybody authorized for anything" state. That's
> certainly the behavior you'd expect from your bank.
I agree - but then 1.0 is not going to be a real production release.
I really think it should be called a 1.0RC.
But anyway... I'm out for a few hours and if David has not fixed this by then,
I'll work on a fix for trunk and we can then decide if that makes it for 1.0
cheers
Re: Release 1.0 New Build Available
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Well it appears that Tomcat and Jetty handle this situation
differently (Tomcat: all secure pages locked down, Jetty: all secure
pages accessible to anybody), which is *definitely* a bug...
But really, if the user put security settings in their web.xml, then
clearly they're expecting security to be applied. If we disable all
security because they missed a deployment plan or a deployment plan
setting, then I think that's a huge security problem. Gnerally
speaking, I think it's always best to fail to a more secure state, not
to fail to an "anybody authorized for anything" state. That's
certainly the behavior you'd expect from your bank.
Thanks,
Aaron
On 12/18/05, David Jencks <da...@yahoo.com> wrote:
> I always thought this was a feature rather than a bug. I believe
> that what determines if you get security is whether there is a role-
> principal mapping in the geronimo plan, not the existence of the
> geronimo plan. I believe the same applies to ejbs.
>
> I'm a bit nervous about changing this stable behavior this close to a
> release.
>
> david jencks
>
> On Dec 18, 2005, at 11:04 AM, Aaron Mulder wrote:
>
> > Another major problem:
> >
> > If you deploy a WAR with security settings an no geronimo-web.xml, all
> > supposedly secure content is unprotected! Try deploying this with no
> > plan: http://cvs.apache.org/repository/geronimo/wars/geronimo-ldap-
> > demo-1.0-SNAPSHOT.war
> > and then visiting
> > http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and clicking the
> > links to "secure" and "forbidden". Both links work, with no login
> > prompt. Instead, IMO, you should get a login prompt and (since no
> > realm was configured) all logins should fail.
> >
> > -1 to releasing without the fix. :) I'm sorry, this is the stuff
> > that's supposed to be flushed out during the "release candidate"
> > phase. We never had one since we were trying to get 1.0 out the door
> > in 30 seconds or less, but now we're having one, and I think we ought
> > to use it. I'd rather release a solid 1.0 in a week instead of a
> > broken one now.
> >
> > Aaron
> >
> > On 12/18/05, Dain Sundstrom <da...@iq80.com> wrote:
> >> -1 to all "fixes"
> >>
> >> We're never going to get this release out at this rate. Let's list
> >> these as known issues and plan for a 1.0.1 release in two weeks.
> >>
> >> -dain
> >>
> >> On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
> >>
> >>> Cool...I have a clustering GBean fix...so since we need to rebuild I
> >>> would like to slide mine in too.
> >>>
> >>> Aaron Mulder wrote:
> >>>> I'd like to put one more fix in here -- sorry, but I just got
> >>>> back to
> >>>> my internet connection. Right now if you put a username or
> >>>> password
> >>>> of blank in the database pool portlet, the deployment fails.
> >>>> This is
> >>>> of course required for connections to the embedded Derby instance,
> >>>> and
> >>>> I have the fix ready.
> >>>>
> >>>> Thanks,
> >>>> Aaron
> >>>>
> >>>> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
> >>>>> Can we also address part 2 (shutdown error) of GERONIMO-1371? It
> >>>>> fails
> >>>>> consistently when issuing a startup followed by a shutdown..
> >>>>> Anyone have any insight here? If we don't fix it, we should add
> >>>>> this to
> >>>>> the Release notes as a "known issue".
> >>>>>
> >>>>> BTW, looking through the release notes... I assume "Specific
> >>>>> Issues,
> >>>>> Features and Improvements for Version 1.0" is a list of things
> >>>>> that
> >>>>> already have been fixed in 1.0. We may want to make this a bit
> >>>>> clearer.
> >>>>> "Specific Issues, Features and Improvements *fixed* for Version
> >>>>> 1.0"
> >>>>>
> >>>>> Hmm.. Should there be a section in the release notes for common
> >>>>> known
> >>>>> issues (JIRAs) or do you feel that a link to JIRA is sufficient?
> >>>>> The
> >>>>> "Significant Missing Features" section info is much broader and
> >>>>> not at a
> >>>>> JIRA granularity.
> >>>>>
> >>>>>
> >>>>> Thanks
> >>>>> -Dave-
> >>>>>
> >>>>> Dave Colasurdo wrote:
> >>>>>> Matt Hogstrom wrote:
> >>>>>>
> >>>>>>> Deferring to 1.1
> >>>>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
> >>>>>>>
> >>>>>> Any chance of incorporating part 1 of JIRA 1371? It is simply
> >>>>>> adding an
> >>>>>> @echo off to startup.bat (and a "launching new window"
> >>>>>> message).
> >>>>>>
> >>>>>> While not a functional problem, it sure will make a big
> >>>>>> difference as to a user's first impression of geronimo..
> >>>>>>
> >>>>>> Have attached the patch to the JIRA..
> >>>>>>
> >>>>>> Here is the output with the fix:
> >>>>>>
> >>>>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
> >>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> >>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> >>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> >>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
> >>>>>>
> >>>>>> Launching Geronimo in a new window
> >>>>>>
> >>>>>>
> >>>>>> Here is the output Without the fix:
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
> >>>>>> "Windows_NT"
> >>>>>> setlocal
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
> >>>>>> CURRENT_DIR=c:\matt_spin_121805\geronim
> >>>>>> o-1.0\bin
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
> >>>>>> GERONIMO_HOME=c:\matt_spin_121805\geron
> >>>>>> imo-1.0\bin
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
> >>>>>> "c:\matt_spin_121805\geronimo-1.0\
> >>>>>> bin\bin\geronimo.bat" goto okHome
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0>set
> >>>>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
> >>>>>> 1.0
> >>>>>>
> >>>>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
> >>>>>> \geronimo-1.0\bin
> >>>>>>
> >>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> >>>>>> "c:\matt_spin_121805\geronimo-1.0\
> >>>>>> bin\geronimo.bat" goto okHome
> >>>>>>
> >>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set
> >>>>>> EXECUTABLE=c:\matt_spin_121805\geronimo
> >>>>>> -1.0\bin\geronimo.bat
> >>>>>>
> >>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> >>>>>> "c:\matt_spin_121805\geronimo-1.0\
> >>>>>> bin\geronimo.bat" goto okExec
> >>>>>>
> >>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
> >>>>>>
> >>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
> >>>>>> doneSetArgs
> >>>>>>
> >>>>>> C:\matt_spin_121805\geronimo-1.0\bin>call
> >>>>>> "c:\matt_spin_121805\geronimo-1.0\bin\
> >>>>>> geronimo.bat" start
> >>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> >>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> >>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> >>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>
> >>
>
>
Re: Release 1.0 New Build Available
Posted by David Jencks <da...@yahoo.com>.
I always thought this was a feature rather than a bug. I believe
that what determines if you get security is whether there is a role-
principal mapping in the geronimo plan, not the existence of the
geronimo plan. I believe the same applies to ejbs.
I'm a bit nervous about changing this stable behavior this close to a
release.
david jencks
On Dec 18, 2005, at 11:04 AM, Aaron Mulder wrote:
> Another major problem:
>
> If you deploy a WAR with security settings an no geronimo-web.xml, all
> supposedly secure content is unprotected! Try deploying this with no
> plan: http://cvs.apache.org/repository/geronimo/wars/geronimo-ldap-
> demo-1.0-SNAPSHOT.war
> and then visiting
> http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and clicking the
> links to "secure" and "forbidden". Both links work, with no login
> prompt. Instead, IMO, you should get a login prompt and (since no
> realm was configured) all logins should fail.
>
> -1 to releasing without the fix. :) I'm sorry, this is the stuff
> that's supposed to be flushed out during the "release candidate"
> phase. We never had one since we were trying to get 1.0 out the door
> in 30 seconds or less, but now we're having one, and I think we ought
> to use it. I'd rather release a solid 1.0 in a week instead of a
> broken one now.
>
> Aaron
>
> On 12/18/05, Dain Sundstrom <da...@iq80.com> wrote:
>> -1 to all "fixes"
>>
>> We're never going to get this release out at this rate. Let's list
>> these as known issues and plan for a 1.0.1 release in two weeks.
>>
>> -dain
>>
>> On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
>>
>>> Cool...I have a clustering GBean fix...so since we need to rebuild I
>>> would like to slide mine in too.
>>>
>>> Aaron Mulder wrote:
>>>> I'd like to put one more fix in here -- sorry, but I just got
>>>> back to
>>>> my internet connection. Right now if you put a username or
>>>> password
>>>> of blank in the database pool portlet, the deployment fails.
>>>> This is
>>>> of course required for connections to the embedded Derby instance,
>>>> and
>>>> I have the fix ready.
>>>>
>>>> Thanks,
>>>> Aaron
>>>>
>>>> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>>>> Can we also address part 2 (shutdown error) of GERONIMO-1371? It
>>>>> fails
>>>>> consistently when issuing a startup followed by a shutdown..
>>>>> Anyone have any insight here? If we don't fix it, we should add
>>>>> this to
>>>>> the Release notes as a "known issue".
>>>>>
>>>>> BTW, looking through the release notes... I assume "Specific
>>>>> Issues,
>>>>> Features and Improvements for Version 1.0" is a list of things
>>>>> that
>>>>> already have been fixed in 1.0. We may want to make this a bit
>>>>> clearer.
>>>>> "Specific Issues, Features and Improvements *fixed* for Version
>>>>> 1.0"
>>>>>
>>>>> Hmm.. Should there be a section in the release notes for common
>>>>> known
>>>>> issues (JIRAs) or do you feel that a link to JIRA is sufficient?
>>>>> The
>>>>> "Significant Missing Features" section info is much broader and
>>>>> not at a
>>>>> JIRA granularity.
>>>>>
>>>>>
>>>>> Thanks
>>>>> -Dave-
>>>>>
>>>>> Dave Colasurdo wrote:
>>>>>> Matt Hogstrom wrote:
>>>>>>
>>>>>>> Deferring to 1.1
>>>>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
>>>>>>>
>>>>>> Any chance of incorporating part 1 of JIRA 1371? It is simply
>>>>>> adding an
>>>>>> @echo off to startup.bat (and a "launching new window"
>>>>>> message).
>>>>>>
>>>>>> While not a functional problem, it sure will make a big
>>>>>> difference as to a user's first impression of geronimo..
>>>>>>
>>>>>> Have attached the patch to the JIRA..
>>>>>>
>>>>>> Here is the output with the fix:
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>
>>>>>> Launching Geronimo in a new window
>>>>>>
>>>>>>
>>>>>> Here is the output Without the fix:
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
>>>>>> "Windows_NT"
>>>>>> setlocal
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>> CURRENT_DIR=c:\matt_spin_121805\geronim
>>>>>> o-1.0\bin
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>> GERONIMO_HOME=c:\matt_spin_121805\geron
>>>>>> imo-1.0\bin
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>> bin\bin\geronimo.bat" goto okHome
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0>set
>>>>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
>>>>>> 1.0
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
>>>>>> \geronimo-1.0\bin
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>> bin\geronimo.bat" goto okHome
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>> EXECUTABLE=c:\matt_spin_121805\geronimo
>>>>>> -1.0\bin\geronimo.bat
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>> bin\geronimo.bat" goto okExec
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
>>>>>> doneSetArgs
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>call
>>>>>> "c:\matt_spin_121805\geronimo-1.0\bin\
>>>>>> geronimo.bat" start
>>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>
>>
Re: Release 1.0 New Build Available
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
Why *not* put up an RC that we can release (i.e. distribute for
people to work with rather than an unofficial candidate that we put
in some persons directory)?
Can you give a reason why you are against the RC? 1.0 is important
for the whole project. It's really a big accomplishment.
geir
On Dec 18, 2005, at 3:25 PM, Dain Sundstrom wrote:
> -1 to doing an rc
>
> Lets do 1.0.0 now and 1.0.1 in two weeks.
>
> -dain
>
> On Dec 18, 2005, at 12:16 PM, Geir Magnusson Jr. wrote:
>
>> +1
>>
>> Do an RC and publicize it. We'll get a surge of interest. Let
>> people beat the tar out of it. Having a 1.0 would have been a
>> nice tie-in to ApacheCon, but that's over now.
>>
>> Maybe let the RC process run over the holiday season, and hit the
>> world with a 1.0 right after New Year as people get back to work,
>> recharged, saws sharpened and ready to do new things. Lets make a
>> splash then - go into the New Year on all cylinders...
>>
>> geir
>>
>>
>> On Dec 18, 2005, at 2:04 PM, Aaron Mulder wrote:
>>
>>> Another major problem:
>>>
>>> If you deploy a WAR with security settings an no geronimo-
>>> web.xml, all
>>> supposedly secure content is unprotected! Try deploying this
>>> with no
>>> plan: http://cvs.apache.org/repository/geronimo/wars/geronimo-
>>> ldap-demo-1.0-SNAPSHOT.war
>>> and then visiting
>>> http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and
>>> clicking the
>>> links to "secure" and "forbidden". Both links work, with no login
>>> prompt. Instead, IMO, you should get a login prompt and (since no
>>> realm was configured) all logins should fail.
>>>
>>> -1 to releasing without the fix. :) I'm sorry, this is the stuff
>>> that's supposed to be flushed out during the "release candidate"
>>> phase. We never had one since we were trying to get 1.0 out the
>>> door
>>> in 30 seconds or less, but now we're having one, and I think we
>>> ought
>>> to use it. I'd rather release a solid 1.0 in a week instead of a
>>> broken one now.
>>>
>>> Aaron
>>>
>>> On 12/18/05, Dain Sundstrom <da...@iq80.com> wrote:
>>>> -1 to all "fixes"
>>>>
>>>> We're never going to get this release out at this rate. Let's list
>>>> these as known issues and plan for a 1.0.1 release in two weeks.
>>>>
>>>> -dain
>>>>
>>>> On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
>>>>
>>>>> Cool...I have a clustering GBean fix...so since we need to
>>>>> rebuild I
>>>>> would like to slide mine in too.
>>>>>
>>>>> Aaron Mulder wrote:
>>>>>> I'd like to put one more fix in here -- sorry, but I just got
>>>>>> back to
>>>>>> my internet connection. Right now if you put a username or
>>>>>> password
>>>>>> of blank in the database pool portlet, the deployment fails.
>>>>>> This is
>>>>>> of course required for connections to the embedded Derby
>>>>>> instance,
>>>>>> and
>>>>>> I have the fix ready.
>>>>>>
>>>>>> Thanks,
>>>>>> Aaron
>>>>>>
>>>>>> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>>>>>> Can we also address part 2 (shutdown error) of
>>>>>>> GERONIMO-1371? It
>>>>>>> fails
>>>>>>> consistently when issuing a startup followed by a shutdown..
>>>>>>> Anyone have any insight here? If we don't fix it, we should add
>>>>>>> this to
>>>>>>> the Release notes as a "known issue".
>>>>>>>
>>>>>>> BTW, looking through the release notes... I assume "Specific
>>>>>>> Issues,
>>>>>>> Features and Improvements for Version 1.0" is a list of
>>>>>>> things that
>>>>>>> already have been fixed in 1.0. We may want to make this a bit
>>>>>>> clearer.
>>>>>>> "Specific Issues, Features and Improvements *fixed* for
>>>>>>> Version
>>>>>>> 1.0"
>>>>>>>
>>>>>>> Hmm.. Should there be a section in the release notes for common
>>>>>>> known
>>>>>>> issues (JIRAs) or do you feel that a link to JIRA is sufficient?
>>>>>>> The
>>>>>>> "Significant Missing Features" section info is much broader and
>>>>>>> not at a
>>>>>>> JIRA granularity.
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>> -Dave-
>>>>>>>
>>>>>>> Dave Colasurdo wrote:
>>>>>>>> Matt Hogstrom wrote:
>>>>>>>>
>>>>>>>>> Deferring to 1.1
>>>>>>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
>>>>>>>>>
>>>>>>>> Any chance of incorporating part 1 of JIRA 1371? It is simply
>>>>>>>> adding an
>>>>>>>> @echo off to startup.bat (and a "launching new window"
>>>>>>>> message).
>>>>>>>>
>>>>>>>> While not a functional problem, it sure will make a big
>>>>>>>> difference as to a user's first impression of geronimo..
>>>>>>>>
>>>>>>>> Have attached the patch to the JIRA..
>>>>>>>>
>>>>>>>> Here is the output with the fix:
>>>>>>>>
>>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var
>>>>>>>> \temp
>>>>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>>>
>>>>>>>> Launching Geronimo in a new window
>>>>>>>>
>>>>>>>>
>>>>>>>> Here is the output Without the fix:
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
>>>>>>>> "Windows_NT"
>>>>>>>> setlocal
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>>> CURRENT_DIR=c:\matt_spin_121805\geronim
>>>>>>>> o-1.0\bin
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto
>>>>>>>> gotHome
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>>> GERONIMO_HOME=c:\matt_spin_121805\geron
>>>>>>>> imo-1.0\bin
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>>>> bin\bin\geronimo.bat" goto okHome
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0>set
>>>>>>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
>>>>>>>> 1.0
>>>>>>>>
>>>>>>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
>>>>>>>> \geronimo-1.0\bin
>>>>>>>>
>>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>>>> bin\geronimo.bat" goto okHome
>>>>>>>>
>>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>>> EXECUTABLE=c:\matt_spin_121805\geronimo
>>>>>>>> -1.0\bin\geronimo.bat
>>>>>>>>
>>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>>>> bin\geronimo.bat" goto okExec
>>>>>>>>
>>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>>>>>>>>
>>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
>>>>>>>> doneSetArgs
>>>>>>>>
>>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>call
>>>>>>>> "c:\matt_spin_121805\geronimo-1.0\bin\
>>>>>>>> geronimo.bat" start
>>>>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var
>>>>>>>> \temp
>>>>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>>
>>
>> --
>> Geir Magnusson Jr +1-203-665-6437
>> geirm@apache.org
>>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Release 1.0 New Build Available
Posted by Dain Sundstrom <da...@iq80.com>.
-1 to doing an rc
Lets do 1.0.0 now and 1.0.1 in two weeks.
-dain
On Dec 18, 2005, at 12:16 PM, Geir Magnusson Jr. wrote:
> +1
>
> Do an RC and publicize it. We'll get a surge of interest. Let
> people beat the tar out of it. Having a 1.0 would have been a nice
> tie-in to ApacheCon, but that's over now.
>
> Maybe let the RC process run over the holiday season, and hit the
> world with a 1.0 right after New Year as people get back to work,
> recharged, saws sharpened and ready to do new things. Lets make a
> splash then - go into the New Year on all cylinders...
>
> geir
>
>
> On Dec 18, 2005, at 2:04 PM, Aaron Mulder wrote:
>
>> Another major problem:
>>
>> If you deploy a WAR with security settings an no geronimo-web.xml,
>> all
>> supposedly secure content is unprotected! Try deploying this with no
>> plan: http://cvs.apache.org/repository/geronimo/wars/geronimo-ldap-
>> demo-1.0-SNAPSHOT.war
>> and then visiting
>> http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and clicking
>> the
>> links to "secure" and "forbidden". Both links work, with no login
>> prompt. Instead, IMO, you should get a login prompt and (since no
>> realm was configured) all logins should fail.
>>
>> -1 to releasing without the fix. :) I'm sorry, this is the stuff
>> that's supposed to be flushed out during the "release candidate"
>> phase. We never had one since we were trying to get 1.0 out the door
>> in 30 seconds or less, but now we're having one, and I think we ought
>> to use it. I'd rather release a solid 1.0 in a week instead of a
>> broken one now.
>>
>> Aaron
>>
>> On 12/18/05, Dain Sundstrom <da...@iq80.com> wrote:
>>> -1 to all "fixes"
>>>
>>> We're never going to get this release out at this rate. Let's list
>>> these as known issues and plan for a 1.0.1 release in two weeks.
>>>
>>> -dain
>>>
>>> On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
>>>
>>>> Cool...I have a clustering GBean fix...so since we need to
>>>> rebuild I
>>>> would like to slide mine in too.
>>>>
>>>> Aaron Mulder wrote:
>>>>> I'd like to put one more fix in here -- sorry, but I just got
>>>>> back to
>>>>> my internet connection. Right now if you put a username or
>>>>> password
>>>>> of blank in the database pool portlet, the deployment fails.
>>>>> This is
>>>>> of course required for connections to the embedded Derby instance,
>>>>> and
>>>>> I have the fix ready.
>>>>>
>>>>> Thanks,
>>>>> Aaron
>>>>>
>>>>> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>>>>> Can we also address part 2 (shutdown error) of GERONIMO-1371? It
>>>>>> fails
>>>>>> consistently when issuing a startup followed by a shutdown..
>>>>>> Anyone have any insight here? If we don't fix it, we should add
>>>>>> this to
>>>>>> the Release notes as a "known issue".
>>>>>>
>>>>>> BTW, looking through the release notes... I assume "Specific
>>>>>> Issues,
>>>>>> Features and Improvements for Version 1.0" is a list of things
>>>>>> that
>>>>>> already have been fixed in 1.0. We may want to make this a bit
>>>>>> clearer.
>>>>>> "Specific Issues, Features and Improvements *fixed* for Version
>>>>>> 1.0"
>>>>>>
>>>>>> Hmm.. Should there be a section in the release notes for common
>>>>>> known
>>>>>> issues (JIRAs) or do you feel that a link to JIRA is sufficient?
>>>>>> The
>>>>>> "Significant Missing Features" section info is much broader and
>>>>>> not at a
>>>>>> JIRA granularity.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> -Dave-
>>>>>>
>>>>>> Dave Colasurdo wrote:
>>>>>>> Matt Hogstrom wrote:
>>>>>>>
>>>>>>>> Deferring to 1.1
>>>>>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
>>>>>>>>
>>>>>>> Any chance of incorporating part 1 of JIRA 1371? It is simply
>>>>>>> adding an
>>>>>>> @echo off to startup.bat (and a "launching new window"
>>>>>>> message).
>>>>>>>
>>>>>>> While not a functional problem, it sure will make a big
>>>>>>> difference as to a user's first impression of geronimo..
>>>>>>>
>>>>>>> Have attached the patch to the JIRA..
>>>>>>>
>>>>>>> Here is the output with the fix:
>>>>>>>
>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>>
>>>>>>> Launching Geronimo in a new window
>>>>>>>
>>>>>>>
>>>>>>> Here is the output Without the fix:
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
>>>>>>> "Windows_NT"
>>>>>>> setlocal
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>> CURRENT_DIR=c:\matt_spin_121805\geronim
>>>>>>> o-1.0\bin
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto
>>>>>>> gotHome
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>> GERONIMO_HOME=c:\matt_spin_121805\geron
>>>>>>> imo-1.0\bin
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>>> bin\bin\geronimo.bat" goto okHome
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0>set
>>>>>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
>>>>>>> 1.0
>>>>>>>
>>>>>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
>>>>>>> \geronimo-1.0\bin
>>>>>>>
>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>>> bin\geronimo.bat" goto okHome
>>>>>>>
>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>> EXECUTABLE=c:\matt_spin_121805\geronimo
>>>>>>> -1.0\bin\geronimo.bat
>>>>>>>
>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>>> bin\geronimo.bat" goto okExec
>>>>>>>
>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>>>>>>>
>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
>>>>>>> doneSetArgs
>>>>>>>
>>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>call
>>>>>>> "c:\matt_spin_121805\geronimo-1.0\bin\
>>>>>>> geronimo.bat" start
>>>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>
>>>
>
> --
> Geir Magnusson Jr +1-203-665-6437
> geirm@apache.org
>
Re: Release 1.0 New Build Available
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
+1
Do an RC and publicize it. We'll get a surge of interest. Let
people beat the tar out of it. Having a 1.0 would have been a nice
tie-in to ApacheCon, but that's over now.
Maybe let the RC process run over the holiday season, and hit the
world with a 1.0 right after New Year as people get back to work,
recharged, saws sharpened and ready to do new things. Lets make a
splash then - go into the New Year on all cylinders...
geir
On Dec 18, 2005, at 2:04 PM, Aaron Mulder wrote:
> Another major problem:
>
> If you deploy a WAR with security settings an no geronimo-web.xml, all
> supposedly secure content is unprotected! Try deploying this with no
> plan: http://cvs.apache.org/repository/geronimo/wars/geronimo-ldap-
> demo-1.0-SNAPSHOT.war
> and then visiting
> http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and clicking the
> links to "secure" and "forbidden". Both links work, with no login
> prompt. Instead, IMO, you should get a login prompt and (since no
> realm was configured) all logins should fail.
>
> -1 to releasing without the fix. :) I'm sorry, this is the stuff
> that's supposed to be flushed out during the "release candidate"
> phase. We never had one since we were trying to get 1.0 out the door
> in 30 seconds or less, but now we're having one, and I think we ought
> to use it. I'd rather release a solid 1.0 in a week instead of a
> broken one now.
>
> Aaron
>
> On 12/18/05, Dain Sundstrom <da...@iq80.com> wrote:
>> -1 to all "fixes"
>>
>> We're never going to get this release out at this rate. Let's list
>> these as known issues and plan for a 1.0.1 release in two weeks.
>>
>> -dain
>>
>> On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
>>
>>> Cool...I have a clustering GBean fix...so since we need to rebuild I
>>> would like to slide mine in too.
>>>
>>> Aaron Mulder wrote:
>>>> I'd like to put one more fix in here -- sorry, but I just got
>>>> back to
>>>> my internet connection. Right now if you put a username or
>>>> password
>>>> of blank in the database pool portlet, the deployment fails.
>>>> This is
>>>> of course required for connections to the embedded Derby instance,
>>>> and
>>>> I have the fix ready.
>>>>
>>>> Thanks,
>>>> Aaron
>>>>
>>>> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>>>> Can we also address part 2 (shutdown error) of GERONIMO-1371? It
>>>>> fails
>>>>> consistently when issuing a startup followed by a shutdown..
>>>>> Anyone have any insight here? If we don't fix it, we should add
>>>>> this to
>>>>> the Release notes as a "known issue".
>>>>>
>>>>> BTW, looking through the release notes... I assume "Specific
>>>>> Issues,
>>>>> Features and Improvements for Version 1.0" is a list of things
>>>>> that
>>>>> already have been fixed in 1.0. We may want to make this a bit
>>>>> clearer.
>>>>> "Specific Issues, Features and Improvements *fixed* for Version
>>>>> 1.0"
>>>>>
>>>>> Hmm.. Should there be a section in the release notes for common
>>>>> known
>>>>> issues (JIRAs) or do you feel that a link to JIRA is sufficient?
>>>>> The
>>>>> "Significant Missing Features" section info is much broader and
>>>>> not at a
>>>>> JIRA granularity.
>>>>>
>>>>>
>>>>> Thanks
>>>>> -Dave-
>>>>>
>>>>> Dave Colasurdo wrote:
>>>>>> Matt Hogstrom wrote:
>>>>>>
>>>>>>> Deferring to 1.1
>>>>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
>>>>>>>
>>>>>> Any chance of incorporating part 1 of JIRA 1371? It is simply
>>>>>> adding an
>>>>>> @echo off to startup.bat (and a "launching new window"
>>>>>> message).
>>>>>>
>>>>>> While not a functional problem, it sure will make a big
>>>>>> difference as to a user's first impression of geronimo..
>>>>>>
>>>>>> Have attached the patch to the JIRA..
>>>>>>
>>>>>> Here is the output with the fix:
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>
>>>>>> Launching Geronimo in a new window
>>>>>>
>>>>>>
>>>>>> Here is the output Without the fix:
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
>>>>>> "Windows_NT"
>>>>>> setlocal
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>> CURRENT_DIR=c:\matt_spin_121805\geronim
>>>>>> o-1.0\bin
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>> GERONIMO_HOME=c:\matt_spin_121805\geron
>>>>>> imo-1.0\bin
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>> bin\bin\geronimo.bat" goto okHome
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0>set
>>>>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
>>>>>> 1.0
>>>>>>
>>>>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
>>>>>> \geronimo-1.0\bin
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>> bin\geronimo.bat" goto okHome
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>> EXECUTABLE=c:\matt_spin_121805\geronimo
>>>>>> -1.0\bin\geronimo.bat
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>>>> bin\geronimo.bat" goto okExec
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
>>>>>> doneSetArgs
>>>>>>
>>>>>> C:\matt_spin_121805\geronimo-1.0\bin>call
>>>>>> "c:\matt_spin_121805\geronimo-1.0\bin\
>>>>>> geronimo.bat" start
>>>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>
>>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Release 1.0 New Build Available
Posted by Davanum Srinivas <da...@gmail.com>.
Aaron, Dain,
It's the release manager's call, which ones to "sneak in" :)
thanks,
dims
On 12/18/05, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> Another major problem:
>
> If you deploy a WAR with security settings an no geronimo-web.xml, all
> supposedly secure content is unprotected! Try deploying this with no
> plan: http://cvs.apache.org/repository/geronimo/wars/geronimo-ldap-demo-1.0-SNAPSHOT.war
> and then visiting
> http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and clicking the
> links to "secure" and "forbidden". Both links work, with no login
> prompt. Instead, IMO, you should get a login prompt and (since no
> realm was configured) all logins should fail.
>
> -1 to releasing without the fix. :) I'm sorry, this is the stuff
> that's supposed to be flushed out during the "release candidate"
> phase. We never had one since we were trying to get 1.0 out the door
> in 30 seconds or less, but now we're having one, and I think we ought
> to use it. I'd rather release a solid 1.0 in a week instead of a
> broken one now.
>
> Aaron
>
> On 12/18/05, Dain Sundstrom <da...@iq80.com> wrote:
> > -1 to all "fixes"
> >
> > We're never going to get this release out at this rate. Let's list
> > these as known issues and plan for a 1.0.1 release in two weeks.
> >
> > -dain
> >
> > On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
> >
> > > Cool...I have a clustering GBean fix...so since we need to rebuild I
> > > would like to slide mine in too.
> > >
> > > Aaron Mulder wrote:
> > >> I'd like to put one more fix in here -- sorry, but I just got back to
> > >> my internet connection. Right now if you put a username or password
> > >> of blank in the database pool portlet, the deployment fails. This is
> > >> of course required for connections to the embedded Derby instance,
> > >> and
> > >> I have the fix ready.
> > >>
> > >> Thanks,
> > >> Aaron
> > >>
> > >> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
> > >>> Can we also address part 2 (shutdown error) of GERONIMO-1371? It
> > >>> fails
> > >>> consistently when issuing a startup followed by a shutdown..
> > >>> Anyone have any insight here? If we don't fix it, we should add
> > >>> this to
> > >>> the Release notes as a "known issue".
> > >>>
> > >>> BTW, looking through the release notes... I assume "Specific Issues,
> > >>> Features and Improvements for Version 1.0" is a list of things that
> > >>> already have been fixed in 1.0. We may want to make this a bit
> > >>> clearer.
> > >>> "Specific Issues, Features and Improvements *fixed* for Version
> > >>> 1.0"
> > >>>
> > >>> Hmm.. Should there be a section in the release notes for common
> > >>> known
> > >>> issues (JIRAs) or do you feel that a link to JIRA is sufficient?
> > >>> The
> > >>> "Significant Missing Features" section info is much broader and
> > >>> not at a
> > >>> JIRA granularity.
> > >>>
> > >>>
> > >>> Thanks
> > >>> -Dave-
> > >>>
> > >>> Dave Colasurdo wrote:
> > >>>> Matt Hogstrom wrote:
> > >>>>
> > >>>>> Deferring to 1.1
> > >>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
> > >>>>>
> > >>>> Any chance of incorporating part 1 of JIRA 1371? It is simply
> > >>>> adding an
> > >>>> @echo off to startup.bat (and a "launching new window"
> > >>>> message).
> > >>>>
> > >>>> While not a functional problem, it sure will make a big
> > >>>> difference as to a user's first impression of geronimo..
> > >>>>
> > >>>> Have attached the patch to the JIRA..
> > >>>>
> > >>>> Here is the output with the fix:
> > >>>>
> > >>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
> > >>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> > >>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> > >>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> > >>>> Using JRE_HOME: c:\j2sdk1.4.2_08
> > >>>>
> > >>>> Launching Geronimo in a new window
> > >>>>
> > >>>>
> > >>>> Here is the output Without the fix:
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
> > >>>> "Windows_NT"
> > >>>> setlocal
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0\bin>set
> > >>>> CURRENT_DIR=c:\matt_spin_121805\geronim
> > >>>> o-1.0\bin
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0\bin>set
> > >>>> GERONIMO_HOME=c:\matt_spin_121805\geron
> > >>>> imo-1.0\bin
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
> > >>>> "c:\matt_spin_121805\geronimo-1.0\
> > >>>> bin\bin\geronimo.bat" goto okHome
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0>set
> > >>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
> > >>>> 1.0
> > >>>>
> > >>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
> > >>>> \geronimo-1.0\bin
> > >>>>
> > >>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> > >>>> "c:\matt_spin_121805\geronimo-1.0\
> > >>>> bin\geronimo.bat" goto okHome
> > >>>>
> > >>>> C:\matt_spin_121805\geronimo-1.0\bin>set
> > >>>> EXECUTABLE=c:\matt_spin_121805\geronimo
> > >>>> -1.0\bin\geronimo.bat
> > >>>>
> > >>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> > >>>> "c:\matt_spin_121805\geronimo-1.0\
> > >>>> bin\geronimo.bat" goto okExec
> > >>>>
> > >>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
> > >>>>
> > >>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
> > >>>> doneSetArgs
> > >>>>
> > >>>> C:\matt_spin_121805\geronimo-1.0\bin>call
> > >>>> "c:\matt_spin_121805\geronimo-1.0\bin\
> > >>>> geronimo.bat" start
> > >>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> > >>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> > >>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> > >>>> Using JRE_HOME: c:\j2sdk1.4.2_08
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> >
> >
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Release 1.0 New Build Available
Posted by Jan Bartel <ja...@mortbay.com>.
I think a security issue is worth delaying a release for. It sounds like
it should be simple to fix.
Jan
Aaron Mulder wrote:
> Another major problem:
>
> If you deploy a WAR with security settings an no geronimo-web.xml, all
> supposedly secure content is unprotected! Try deploying this with no
> plan: http://cvs.apache.org/repository/geronimo/wars/geronimo-ldap-demo-1.0-SNAPSHOT.war
> and then visiting
> http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and clicking the
> links to "secure" and "forbidden". Both links work, with no login
> prompt. Instead, IMO, you should get a login prompt and (since no
> realm was configured) all logins should fail.
>
> -1 to releasing without the fix. :) I'm sorry, this is the stuff
> that's supposed to be flushed out during the "release candidate"
> phase. We never had one since we were trying to get 1.0 out the door
> in 30 seconds or less, but now we're having one, and I think we ought
> to use it. I'd rather release a solid 1.0 in a week instead of a
> broken one now.
>
> Aaron
>
> On 12/18/05, Dain Sundstrom <da...@public.gmane.org> wrote:
>
>>-1 to all "fixes"
>>
>>We're never going to get this release out at this rate. Let's list
>>these as known issues and plan for a 1.0.1 release in two weeks.
>>
>>-dain
>>
>>On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
>>
>>
>>>Cool...I have a clustering GBean fix...so since we need to rebuild I
>>>would like to slide mine in too.
>>>
>>>Aaron Mulder wrote:
>>>
>>>>I'd like to put one more fix in here -- sorry, but I just got back to
>>>>my internet connection. Right now if you put a username or password
>>>>of blank in the database pool portlet, the deployment fails. This is
>>>>of course required for connections to the embedded Derby instance,
>>>>and
>>>>I have the fix ready.
>>>>
>>>>Thanks,
>>>> Aaron
>>>>
>>>>On 12/18/05, Dave Colasurdo <da...@public.gmane.org> wrote:
>>>>
>>>>>Can we also address part 2 (shutdown error) of GERONIMO-1371? It
>>>>>fails
>>>>>consistently when issuing a startup followed by a shutdown..
>>>>>Anyone have any insight here? If we don't fix it, we should add
>>>>>this to
>>>>>the Release notes as a "known issue".
>>>>>
>>>>>BTW, looking through the release notes... I assume "Specific Issues,
>>>>>Features and Improvements for Version 1.0" is a list of things that
>>>>>already have been fixed in 1.0. We may want to make this a bit
>>>>>clearer.
>>>>> "Specific Issues, Features and Improvements *fixed* for Version
>>>>>1.0"
>>>>>
>>>>>Hmm.. Should there be a section in the release notes for common
>>>>>known
>>>>>issues (JIRAs) or do you feel that a link to JIRA is sufficient?
>>>>>The
>>>>>"Significant Missing Features" section info is much broader and
>>>>>not at a
>>>>>JIRA granularity.
>>>>>
>>>>>
>>>>>Thanks
>>>>>-Dave-
>>>>>
>>>>>Dave Colasurdo wrote:
>>>>>
>>>>>>Matt Hogstrom wrote:
>>>>>>
>>>>>>
>>>>>>>Deferring to 1.1
>>>>>>>GERONIMO-1371 - Geronimo startup/shutdown issues
>>>>>>>
>>>>>>
>>>>>>Any chance of incorporating part 1 of JIRA 1371? It is simply
>>>>>>adding an
>>>>>> @echo off to startup.bat (and a "launching new window"
>>>>>>message).
>>>>>>
>>>>>>While not a functional problem, it sure will make a big
>>>>>>difference as to a user's first impression of geronimo..
>>>>>>
>>>>>>Have attached the patch to the JIRA..
>>>>>>
>>>>>>Here is the output with the fix:
>>>>>>
>>>>>>C:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>>Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>>Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>>Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>>>>Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>
>>>>>>Launching Geronimo in a new window
>>>>>>
>>>>>>
>>>>>>Here is the output Without the fix:
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
>>>>>>"Windows_NT"
>>>>>>setlocal
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>CURRENT_DIR=c:\matt_spin_121805\geronim
>>>>>>o-1.0\bin
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>GERONIMO_HOME=c:\matt_spin_121805\geron
>>>>>>imo-1.0\bin
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>"c:\matt_spin_121805\geronimo-1.0\
>>>>>>bin\bin\geronimo.bat" goto okHome
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0>set
>>>>>>GERONIMO_HOME=c:\matt_spin_121805\geronimo-
>>>>>>1.0
>>>>>>
>>>>>>c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
>>>>>>\geronimo-1.0\bin
>>>>>>
>>>>>>C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>"c:\matt_spin_121805\geronimo-1.0\
>>>>>>bin\geronimo.bat" goto okHome
>>>>>>
>>>>>>C:\matt_spin_121805\geronimo-1.0\bin>set
>>>>>>EXECUTABLE=c:\matt_spin_121805\geronimo
>>>>>>-1.0\bin\geronimo.bat
>>>>>>
>>>>>>C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>>>>"c:\matt_spin_121805\geronimo-1.0\
>>>>>>bin\geronimo.bat" goto okExec
>>>>>>
>>>>>>C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>>>>>>
>>>>>>C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
>>>>>>doneSetArgs
>>>>>>
>>>>>>C:\matt_spin_121805\geronimo-1.0\bin>call
>>>>>>"c:\matt_spin_121805\geronimo-1.0\bin\
>>>>>>geronimo.bat" start
>>>>>>Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>>>>Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>>>>Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>>>>Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>
>>
>
Re: Release 1.0 New Build Available
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Another major problem:
If you deploy a WAR with security settings an no geronimo-web.xml, all
supposedly secure content is unprotected! Try deploying this with no
plan: http://cvs.apache.org/repository/geronimo/wars/geronimo-ldap-demo-1.0-SNAPSHOT.war
and then visiting
http://localhost:8080/geronimo-ldap-demo-1.0-SNAPSHOT and clicking the
links to "secure" and "forbidden". Both links work, with no login
prompt. Instead, IMO, you should get a login prompt and (since no
realm was configured) all logins should fail.
-1 to releasing without the fix. :) I'm sorry, this is the stuff
that's supposed to be flushed out during the "release candidate"
phase. We never had one since we were trying to get 1.0 out the door
in 30 seconds or less, but now we're having one, and I think we ought
to use it. I'd rather release a solid 1.0 in a week instead of a
broken one now.
Aaron
On 12/18/05, Dain Sundstrom <da...@iq80.com> wrote:
> -1 to all "fixes"
>
> We're never going to get this release out at this rate. Let's list
> these as known issues and plan for a 1.0.1 release in two weeks.
>
> -dain
>
> On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
>
> > Cool...I have a clustering GBean fix...so since we need to rebuild I
> > would like to slide mine in too.
> >
> > Aaron Mulder wrote:
> >> I'd like to put one more fix in here -- sorry, but I just got back to
> >> my internet connection. Right now if you put a username or password
> >> of blank in the database pool portlet, the deployment fails. This is
> >> of course required for connections to the embedded Derby instance,
> >> and
> >> I have the fix ready.
> >>
> >> Thanks,
> >> Aaron
> >>
> >> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
> >>> Can we also address part 2 (shutdown error) of GERONIMO-1371? It
> >>> fails
> >>> consistently when issuing a startup followed by a shutdown..
> >>> Anyone have any insight here? If we don't fix it, we should add
> >>> this to
> >>> the Release notes as a "known issue".
> >>>
> >>> BTW, looking through the release notes... I assume "Specific Issues,
> >>> Features and Improvements for Version 1.0" is a list of things that
> >>> already have been fixed in 1.0. We may want to make this a bit
> >>> clearer.
> >>> "Specific Issues, Features and Improvements *fixed* for Version
> >>> 1.0"
> >>>
> >>> Hmm.. Should there be a section in the release notes for common
> >>> known
> >>> issues (JIRAs) or do you feel that a link to JIRA is sufficient?
> >>> The
> >>> "Significant Missing Features" section info is much broader and
> >>> not at a
> >>> JIRA granularity.
> >>>
> >>>
> >>> Thanks
> >>> -Dave-
> >>>
> >>> Dave Colasurdo wrote:
> >>>> Matt Hogstrom wrote:
> >>>>
> >>>>> Deferring to 1.1
> >>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
> >>>>>
> >>>> Any chance of incorporating part 1 of JIRA 1371? It is simply
> >>>> adding an
> >>>> @echo off to startup.bat (and a "launching new window"
> >>>> message).
> >>>>
> >>>> While not a functional problem, it sure will make a big
> >>>> difference as to a user's first impression of geronimo..
> >>>>
> >>>> Have attached the patch to the JIRA..
> >>>>
> >>>> Here is the output with the fix:
> >>>>
> >>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
> >>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> >>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> >>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> >>>> Using JRE_HOME: c:\j2sdk1.4.2_08
> >>>>
> >>>> Launching Geronimo in a new window
> >>>>
> >>>>
> >>>> Here is the output Without the fix:
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
> >>>> "Windows_NT"
> >>>> setlocal
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0\bin>set
> >>>> CURRENT_DIR=c:\matt_spin_121805\geronim
> >>>> o-1.0\bin
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0\bin>set
> >>>> GERONIMO_HOME=c:\matt_spin_121805\geron
> >>>> imo-1.0\bin
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
> >>>> "c:\matt_spin_121805\geronimo-1.0\
> >>>> bin\bin\geronimo.bat" goto okHome
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0>set
> >>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
> >>>> 1.0
> >>>>
> >>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
> >>>> \geronimo-1.0\bin
> >>>>
> >>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> >>>> "c:\matt_spin_121805\geronimo-1.0\
> >>>> bin\geronimo.bat" goto okHome
> >>>>
> >>>> C:\matt_spin_121805\geronimo-1.0\bin>set
> >>>> EXECUTABLE=c:\matt_spin_121805\geronimo
> >>>> -1.0\bin\geronimo.bat
> >>>>
> >>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> >>>> "c:\matt_spin_121805\geronimo-1.0\
> >>>> bin\geronimo.bat" goto okExec
> >>>>
> >>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
> >>>>
> >>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
> >>>> doneSetArgs
> >>>>
> >>>> C:\matt_spin_121805\geronimo-1.0\bin>call
> >>>> "c:\matt_spin_121805\geronimo-1.0\bin\
> >>>> geronimo.bat" start
> >>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> >>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> >>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> >>>> Using JRE_HOME: c:\j2sdk1.4.2_08
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
>
>
Re: Release 1.0 New Build Available
Posted by Dain Sundstrom <da...@iq80.com>.
-1 to all "fixes"
We're never going to get this release out at this rate. Let's list
these as known issues and plan for a 1.0.1 release in two weeks.
-dain
On Dec 18, 2005, at 10:51 AM, Jeff Genender wrote:
> Cool...I have a clustering GBean fix...so since we need to rebuild I
> would like to slide mine in too.
>
> Aaron Mulder wrote:
>> I'd like to put one more fix in here -- sorry, but I just got back to
>> my internet connection. Right now if you put a username or password
>> of blank in the database pool portlet, the deployment fails. This is
>> of course required for connections to the embedded Derby instance,
>> and
>> I have the fix ready.
>>
>> Thanks,
>> Aaron
>>
>> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
>>> Can we also address part 2 (shutdown error) of GERONIMO-1371? It
>>> fails
>>> consistently when issuing a startup followed by a shutdown..
>>> Anyone have any insight here? If we don't fix it, we should add
>>> this to
>>> the Release notes as a "known issue".
>>>
>>> BTW, looking through the release notes... I assume "Specific Issues,
>>> Features and Improvements for Version 1.0" is a list of things that
>>> already have been fixed in 1.0. We may want to make this a bit
>>> clearer.
>>> "Specific Issues, Features and Improvements *fixed* for Version
>>> 1.0"
>>>
>>> Hmm.. Should there be a section in the release notes for common
>>> known
>>> issues (JIRAs) or do you feel that a link to JIRA is sufficient?
>>> The
>>> "Significant Missing Features" section info is much broader and
>>> not at a
>>> JIRA granularity.
>>>
>>>
>>> Thanks
>>> -Dave-
>>>
>>> Dave Colasurdo wrote:
>>>> Matt Hogstrom wrote:
>>>>
>>>>> Deferring to 1.1
>>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
>>>>>
>>>> Any chance of incorporating part 1 of JIRA 1371? It is simply
>>>> adding an
>>>> @echo off to startup.bat (and a "launching new window"
>>>> message).
>>>>
>>>> While not a functional problem, it sure will make a big
>>>> difference as to a user's first impression of geronimo..
>>>>
>>>> Have attached the patch to the JIRA..
>>>>
>>>> Here is the output with the fix:
>>>>
>>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>
>>>> Launching Geronimo in a new window
>>>>
>>>>
>>>> Here is the output Without the fix:
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" ==
>>>> "Windows_NT"
>>>> setlocal
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>> CURRENT_DIR=c:\matt_spin_121805\geronim
>>>> o-1.0\bin
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>>> GERONIMO_HOME=c:\matt_spin_121805\geron
>>>> imo-1.0\bin
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>> bin\bin\geronimo.bat" goto okHome
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0>set
>>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
>>>> 1.0
>>>>
>>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805
>>>> \geronimo-1.0\bin
>>>>
>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>> bin\geronimo.bat" goto okHome
>>>>
>>>> C:\matt_spin_121805\geronimo-1.0\bin>set
>>>> EXECUTABLE=c:\matt_spin_121805\geronimo
>>>> -1.0\bin\geronimo.bat
>>>>
>>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>>> "c:\matt_spin_121805\geronimo-1.0\
>>>> bin\geronimo.bat" goto okExec
>>>>
>>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>>>>
>>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto
>>>> doneSetArgs
>>>>
>>>> C:\matt_spin_121805\geronimo-1.0\bin>call
>>>> "c:\matt_spin_121805\geronimo-1.0\bin\
>>>> geronimo.bat" start
>>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>>
>>>>
>>>>
>>>>
>>>>
Re: Release 1.0 New Build Available
Posted by Jeff Genender <jg...@apache.org>.
Cool...I have a clustering GBean fix...so since we need to rebuild I
would like to slide mine in too.
Aaron Mulder wrote:
> I'd like to put one more fix in here -- sorry, but I just got back to
> my internet connection. Right now if you put a username or password
> of blank in the database pool portlet, the deployment fails. This is
> of course required for connections to the embedded Derby instance, and
> I have the fix ready.
>
> Thanks,
> Aaron
>
> On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
>> Can we also address part 2 (shutdown error) of GERONIMO-1371? It fails
>> consistently when issuing a startup followed by a shutdown..
>> Anyone have any insight here? If we don't fix it, we should add this to
>> the Release notes as a "known issue".
>>
>> BTW, looking through the release notes... I assume "Specific Issues,
>> Features and Improvements for Version 1.0" is a list of things that
>> already have been fixed in 1.0. We may want to make this a bit clearer.
>> "Specific Issues, Features and Improvements *fixed* for Version 1.0"
>>
>> Hmm.. Should there be a section in the release notes for common known
>> issues (JIRAs) or do you feel that a link to JIRA is sufficient? The
>> "Significant Missing Features" section info is much broader and not at a
>> JIRA granularity.
>>
>>
>> Thanks
>> -Dave-
>>
>> Dave Colasurdo wrote:
>>> Matt Hogstrom wrote:
>>>
>>>> Deferring to 1.1
>>>> GERONIMO-1371 - Geronimo startup/shutdown issues
>>>>
>>> Any chance of incorporating part 1 of JIRA 1371? It is simply adding an
>>> @echo off to startup.bat (and a "launching new window"
>>> message).
>>>
>>> While not a functional problem, it sure will make a big
>>> difference as to a user's first impression of geronimo..
>>>
>>> Have attached the patch to the JIRA..
>>>
>>> Here is the output with the fix:
>>>
>>> C:\matt_spin_121805\geronimo-1.0\bin>startup
>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>
>>> Launching Geronimo in a new window
>>>
>>>
>>> Here is the output Without the fix:
>>>
>>> c:\matt_spin_121805\geronimo-1.0\bin>startup
>>>
>>> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" == "Windows_NT"
>>> setlocal
>>>
>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>> CURRENT_DIR=c:\matt_spin_121805\geronim
>>> o-1.0\bin
>>>
>>> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
>>>
>>> c:\matt_spin_121805\geronimo-1.0\bin>set
>>> GERONIMO_HOME=c:\matt_spin_121805\geron
>>> imo-1.0\bin
>>>
>>> c:\matt_spin_121805\geronimo-1.0\bin>if exist
>>> "c:\matt_spin_121805\geronimo-1.0\
>>> bin\bin\geronimo.bat" goto okHome
>>>
>>> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>>>
>>> c:\matt_spin_121805\geronimo-1.0>set
>>> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
>>> 1.0
>>>
>>> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805\geronimo-1.0\bin
>>>
>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>> "c:\matt_spin_121805\geronimo-1.0\
>>> bin\geronimo.bat" goto okHome
>>>
>>> C:\matt_spin_121805\geronimo-1.0\bin>set
>>> EXECUTABLE=c:\matt_spin_121805\geronimo
>>> -1.0\bin\geronimo.bat
>>>
>>> C:\matt_spin_121805\geronimo-1.0\bin>if exist
>>> "c:\matt_spin_121805\geronimo-1.0\
>>> bin\geronimo.bat" goto okExec
>>>
>>> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>>>
>>> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto doneSetArgs
>>>
>>> C:\matt_spin_121805\geronimo-1.0\bin>call
>>> "c:\matt_spin_121805\geronimo-1.0\bin\
>>> geronimo.bat" start
>>> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
>>> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
>>> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
>>> Using JRE_HOME: c:\j2sdk1.4.2_08
>>>
>>>
>>>
>>>
>>>
Re: Release 1.0 New Build Available
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I'd like to put one more fix in here -- sorry, but I just got back to
my internet connection. Right now if you put a username or password
of blank in the database pool portlet, the deployment fails. This is
of course required for connections to the embedded Derby instance, and
I have the fix ready.
Thanks,
Aaron
On 12/18/05, Dave Colasurdo <da...@earthlink.net> wrote:
> Can we also address part 2 (shutdown error) of GERONIMO-1371? It fails
> consistently when issuing a startup followed by a shutdown..
> Anyone have any insight here? If we don't fix it, we should add this to
> the Release notes as a "known issue".
>
> BTW, looking through the release notes... I assume "Specific Issues,
> Features and Improvements for Version 1.0" is a list of things that
> already have been fixed in 1.0. We may want to make this a bit clearer.
> "Specific Issues, Features and Improvements *fixed* for Version 1.0"
>
> Hmm.. Should there be a section in the release notes for common known
> issues (JIRAs) or do you feel that a link to JIRA is sufficient? The
> "Significant Missing Features" section info is much broader and not at a
> JIRA granularity.
>
>
> Thanks
> -Dave-
>
> Dave Colasurdo wrote:
> > Matt Hogstrom wrote:
> >
> >>
> >> Deferring to 1.1
> >> GERONIMO-1371 - Geronimo startup/shutdown issues
> >>
> >
> > Any chance of incorporating part 1 of JIRA 1371? It is simply adding an
> > @echo off to startup.bat (and a "launching new window"
> > message).
> >
> > While not a functional problem, it sure will make a big
> > difference as to a user's first impression of geronimo..
> >
> > Have attached the patch to the JIRA..
> >
> > Here is the output with the fix:
> >
> > C:\matt_spin_121805\geronimo-1.0\bin>startup
> > Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> > Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> > Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> > Using JRE_HOME: c:\j2sdk1.4.2_08
> >
> > Launching Geronimo in a new window
> >
> >
> > Here is the output Without the fix:
> >
> > c:\matt_spin_121805\geronimo-1.0\bin>startup
> >
> > c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" == "Windows_NT"
> > setlocal
> >
> > c:\matt_spin_121805\geronimo-1.0\bin>set
> > CURRENT_DIR=c:\matt_spin_121805\geronim
> > o-1.0\bin
> >
> > c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
> >
> > c:\matt_spin_121805\geronimo-1.0\bin>set
> > GERONIMO_HOME=c:\matt_spin_121805\geron
> > imo-1.0\bin
> >
> > c:\matt_spin_121805\geronimo-1.0\bin>if exist
> > "c:\matt_spin_121805\geronimo-1.0\
> > bin\bin\geronimo.bat" goto okHome
> >
> > c:\matt_spin_121805\geronimo-1.0\bin>cd ..
> >
> > c:\matt_spin_121805\geronimo-1.0>set
> > GERONIMO_HOME=c:\matt_spin_121805\geronimo-
> > 1.0
> >
> > c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805\geronimo-1.0\bin
> >
> > C:\matt_spin_121805\geronimo-1.0\bin>if exist
> > "c:\matt_spin_121805\geronimo-1.0\
> > bin\geronimo.bat" goto okHome
> >
> > C:\matt_spin_121805\geronimo-1.0\bin>set
> > EXECUTABLE=c:\matt_spin_121805\geronimo
> > -1.0\bin\geronimo.bat
> >
> > C:\matt_spin_121805\geronimo-1.0\bin>if exist
> > "c:\matt_spin_121805\geronimo-1.0\
> > bin\geronimo.bat" goto okExec
> >
> > C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
> >
> > C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto doneSetArgs
> >
> > C:\matt_spin_121805\geronimo-1.0\bin>call
> > "c:\matt_spin_121805\geronimo-1.0\bin\
> > geronimo.bat" start
> > Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> > Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> > Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> > Using JRE_HOME: c:\j2sdk1.4.2_08
> >
> >
> >
> >
> >
>
Re: Release 1.0 New Build Available
Posted by Dave Colasurdo <da...@earthlink.net>.
Can we also address part 2 (shutdown error) of GERONIMO-1371? It fails
consistently when issuing a startup followed by a shutdown..
Anyone have any insight here? If we don't fix it, we should add this to
the Release notes as a "known issue".
BTW, looking through the release notes... I assume "Specific Issues,
Features and Improvements for Version 1.0" is a list of things that
already have been fixed in 1.0. We may want to make this a bit clearer.
"Specific Issues, Features and Improvements *fixed* for Version 1.0"
Hmm.. Should there be a section in the release notes for common known
issues (JIRAs) or do you feel that a link to JIRA is sufficient? The
"Significant Missing Features" section info is much broader and not at a
JIRA granularity.
Thanks
-Dave-
Dave Colasurdo wrote:
> Matt Hogstrom wrote:
>
>>
>> Deferring to 1.1
>> GERONIMO-1371 - Geronimo startup/shutdown issues
>>
>
> Any chance of incorporating part 1 of JIRA 1371? It is simply adding an
> @echo off to startup.bat (and a "launching new window"
> message).
>
> While not a functional problem, it sure will make a big
> difference as to a user's first impression of geronimo..
>
> Have attached the patch to the JIRA..
>
> Here is the output with the fix:
>
> C:\matt_spin_121805\geronimo-1.0\bin>startup
> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> Using JRE_HOME: c:\j2sdk1.4.2_08
>
> Launching Geronimo in a new window
>
>
> Here is the output Without the fix:
>
> c:\matt_spin_121805\geronimo-1.0\bin>startup
>
> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" == "Windows_NT"
> setlocal
>
> c:\matt_spin_121805\geronimo-1.0\bin>set
> CURRENT_DIR=c:\matt_spin_121805\geronim
> o-1.0\bin
>
> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
>
> c:\matt_spin_121805\geronimo-1.0\bin>set
> GERONIMO_HOME=c:\matt_spin_121805\geron
> imo-1.0\bin
>
> c:\matt_spin_121805\geronimo-1.0\bin>if exist
> "c:\matt_spin_121805\geronimo-1.0\
> bin\bin\geronimo.bat" goto okHome
>
> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>
> c:\matt_spin_121805\geronimo-1.0>set
> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
> 1.0
>
> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805\geronimo-1.0\bin
>
> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> "c:\matt_spin_121805\geronimo-1.0\
> bin\geronimo.bat" goto okHome
>
> C:\matt_spin_121805\geronimo-1.0\bin>set
> EXECUTABLE=c:\matt_spin_121805\geronimo
> -1.0\bin\geronimo.bat
>
> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> "c:\matt_spin_121805\geronimo-1.0\
> bin\geronimo.bat" goto okExec
>
> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>
> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto doneSetArgs
>
> C:\matt_spin_121805\geronimo-1.0\bin>call
> "c:\matt_spin_121805\geronimo-1.0\bin\
> geronimo.bat" start
> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> Using JRE_HOME: c:\j2sdk1.4.2_08
>
>
>
>
>
Re: Release 1.0 New Build Available
Posted by Matt Hogstrom <ma...@hogstrom.org>.
Thanks Dave. I think we can do that. Since its not a code change it should be
pretty easy. Keep us honest as the time progresses.
Dave Colasurdo wrote:
> Matt Hogstrom wrote:
>
>>
>> Deferring to 1.1
>> GERONIMO-1371 - Geronimo startup/shutdown issues
>>
>
> Any chance of incorporating part 1 of JIRA 1371? It is simply adding an
> @echo off to startup.bat (and a "launching new window"
> message).
>
> While not a functional problem, it sure will make a big
> difference as to a user's first impression of geronimo..
>
> Have attached the patch to the JIRA..
>
> Here is the output with the fix:
>
> C:\matt_spin_121805\geronimo-1.0\bin>startup
> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> Using JRE_HOME: c:\j2sdk1.4.2_08
>
> Launching Geronimo in a new window
>
>
> Here is the output Without the fix:
>
> c:\matt_spin_121805\geronimo-1.0\bin>startup
>
> c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" == "Windows_NT"
> setlocal
>
> c:\matt_spin_121805\geronimo-1.0\bin>set
> CURRENT_DIR=c:\matt_spin_121805\geronim
> o-1.0\bin
>
> c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
>
> c:\matt_spin_121805\geronimo-1.0\bin>set
> GERONIMO_HOME=c:\matt_spin_121805\geron
> imo-1.0\bin
>
> c:\matt_spin_121805\geronimo-1.0\bin>if exist
> "c:\matt_spin_121805\geronimo-1.0\
> bin\bin\geronimo.bat" goto okHome
>
> c:\matt_spin_121805\geronimo-1.0\bin>cd ..
>
> c:\matt_spin_121805\geronimo-1.0>set
> GERONIMO_HOME=c:\matt_spin_121805\geronimo-
> 1.0
>
> c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805\geronimo-1.0\bin
>
> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> "c:\matt_spin_121805\geronimo-1.0\
> bin\geronimo.bat" goto okHome
>
> C:\matt_spin_121805\geronimo-1.0\bin>set
> EXECUTABLE=c:\matt_spin_121805\geronimo
> -1.0\bin\geronimo.bat
>
> C:\matt_spin_121805\geronimo-1.0\bin>if exist
> "c:\matt_spin_121805\geronimo-1.0\
> bin\geronimo.bat" goto okExec
>
> C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
>
> C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto doneSetArgs
>
> C:\matt_spin_121805\geronimo-1.0\bin>call
> "c:\matt_spin_121805\geronimo-1.0\bin\
> geronimo.bat" start
> Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
> Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
> Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
> Using JRE_HOME: c:\j2sdk1.4.2_08
>
>
>
>
>
>
Re: Release 1.0 New Build Available
Posted by Dave Colasurdo <da...@earthlink.net>.
Matt Hogstrom wrote:
>
> Deferring to 1.1
> GERONIMO-1371 - Geronimo startup/shutdown issues
>
Any chance of incorporating part 1 of JIRA 1371? It is simply adding an
@echo off to startup.bat (and a "launching new window"
message).
While not a functional problem, it sure will make a big
difference as to a user's first impression of geronimo..
Have attached the patch to the JIRA..
Here is the output with the fix:
C:\matt_spin_121805\geronimo-1.0\bin>startup
Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
Using JRE_HOME: c:\j2sdk1.4.2_08
Launching Geronimo in a new window
Here is the output Without the fix:
c:\matt_spin_121805\geronimo-1.0\bin>startup
c:\matt_spin_121805\geronimo-1.0\bin>if "Windows_NT" == "Windows_NT"
setlocal
c:\matt_spin_121805\geronimo-1.0\bin>set
CURRENT_DIR=c:\matt_spin_121805\geronim
o-1.0\bin
c:\matt_spin_121805\geronimo-1.0\bin>if not "" == "" goto gotHome
c:\matt_spin_121805\geronimo-1.0\bin>set
GERONIMO_HOME=c:\matt_spin_121805\geron
imo-1.0\bin
c:\matt_spin_121805\geronimo-1.0\bin>if exist
"c:\matt_spin_121805\geronimo-1.0\
bin\bin\geronimo.bat" goto okHome
c:\matt_spin_121805\geronimo-1.0\bin>cd ..
c:\matt_spin_121805\geronimo-1.0>set
GERONIMO_HOME=c:\matt_spin_121805\geronimo-
1.0
c:\matt_spin_121805\geronimo-1.0>cd c:\matt_spin_121805\geronimo-1.0\bin
C:\matt_spin_121805\geronimo-1.0\bin>if exist
"c:\matt_spin_121805\geronimo-1.0\
bin\geronimo.bat" goto okHome
C:\matt_spin_121805\geronimo-1.0\bin>set
EXECUTABLE=c:\matt_spin_121805\geronimo
-1.0\bin\geronimo.bat
C:\matt_spin_121805\geronimo-1.0\bin>if exist
"c:\matt_spin_121805\geronimo-1.0\
bin\geronimo.bat" goto okExec
C:\matt_spin_121805\geronimo-1.0\bin>set CMD_LINE_ARGS=
C:\matt_spin_121805\geronimo-1.0\bin>if """" == """" goto doneSetArgs
C:\matt_spin_121805\geronimo-1.0\bin>call
"c:\matt_spin_121805\geronimo-1.0\bin\
geronimo.bat" start
Using GERONIMO_BASE: c:\matt_spin_121805\geronimo-1.0
Using GERONIMO_HOME: c:\matt_spin_121805\geronimo-1.0
Using GERONIMO_TMPDIR: c:\matt_spin_121805\geronimo-1.0\var\temp
Using JRE_HOME: c:\j2sdk1.4.2_08
Re: Release 1.0 New Build Available
Posted by anita kulshreshtha <a_...@yahoo.com>.
I have used geronimo-tomcat-j2ee-1.0-20051218.zip
and have tested all the issues mentioned here on win
XP. They all have been fixed.
thanks
Anita
--- Matt Hogstrom <ma...@hogstrom.org> wrote:
> I have rebuilt the 1.0 server with the following
> JIRA's incorporated and this
> was at Committed revision 357442 of subversion.
>
> The server started successfully on my system (Mac
> OS) for both Tomcat and Jetty.
> I wiped out my Maven repo before rebuilding so to
> the best of my knowledge it
> works on my system and should work on yours.
>
> The images are available at
> http://people.apache.org/~hogstrom/geronimo-1.0
>
> The files are:
>
> geronimo-tomcat-j2ee-1.0-20051218.tar.gz
> geronimo-tomcat-j2ee-1.0-20051218.zip
>
> geronimo-jetty-j2ee-1.0-20051218.tar.gz
> geronimo-jetty-j2ee-1.0-20051218.zip
>
> Note: These files extract into ./geronimo-1.0 which
> is different than the file
> name. Please ensure that any previous release of
> Geronimo installed in that
> directory tree has been removed.
>
> Please take time to download and run through the
> images and verify they start
> and stop without errors (there are some known
> ActiveMQ errors at shutdown around
> connection problems. I believe these can safely be
> ignored and will be fixed in
> a near term release.)
>
> Post comments back to the list and we'll incorporate
> the changes quickly and
> keep the train moving.
>
> I have not had time to download and retest these
> images to make sure they made
> it up correctly. Any problems reply back to this
> thread.
>
> Mr. Blevins and Mr. Jencks, I hate to impose on you
> but can you start a TCK run
> on this build and barring any major issues this
> might be it so it would be good
> to have verification of the build.
>
> Thanks
>
> - Matt
>
> Here is the list of defects incorporated into this
> build.
>
> Completed
> GERONIMO-1363 - DayTrader still using old
> geronimo-spec files - applied by Matt
> GERONIMO-1364 - update welcome pages to point at
> HTTP redirects in the
> geronimo.apache.org site
> GERONIMO-1372 - Exception during startup - TradeEJB
> - Fixed per Dain
> GERONIMO-1373 - DB info portlet not working
> correctly - Applied by Matt
> GERONIMO-1375 - Invalid login to console should not
> produce stack trace
> GERONIMO-1377 - Startup Warning on tomcat - unknown
> default host. - Fixed by Jeff
>
> Deferring to 1.1
> GERONIMO-1371 - Geronimo startup/shutdown issues
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com