You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Shinobu Kawai Yoshida <sh...@gmail.com> on 2005/01/19 13:21:59 UTC

Bugs that depend on other bugs

Hi Will,

> http://issues.apache.org/bugzilla/show_bug.cgi?id=8651
> 
> 
> ------- Additional Comments From wglass@forio.com  2005-01-19 01:50 -------
> I'm against using setAccessible within Velocity.  It's hard enough to
> configure the security policies for a webapp container as it is.  Why add
> another requirement to the mess?

Me too.  -1 for using setAccessible within Velocity.

But what should be done for bugs that depend on other bugs?  Should
there be a uncommitted patch so whoever can't wait for the fix can
apply?  Or should we just let them wait for the root bug to get fixed?
## As for me, I say redirect them to nag the root bug people.  eg.
with votes, etc.

FYI, Bugzilla #33020 also depends on a bug of commons-collections.
   http://issues.apache.org/bugzilla/show_bug.cgi?id=33020

Best regards,
-- Shinobu

--
Shinobu "Kawai" Yoshida <sh...@gmail.com>

---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org


Re: Bugs that depend on other bugs

Posted by Shinobu Kawai Yoshida <sh...@gmail.com>.
Hi guys, thanks for your comments.

> Will Glass-Husain <wg...@forio.com> wrote:
> > It seems reasonable to me to keep this as a Velocity bug.  This can be a
> > tickler for updating the jar file once the dependent library fixes the
> bug.
> > It also prevents dup issues from getting created.

OK.  So we can leave it alone for now.

> And to the end user, it's still a Velocity bug.   End-users should be able
> to view Velocity as a "black box."

Sure hope it gets fixed soon for Velocity's sake.  :)

Best regards,
-- Shinobu

--
Shinobu "Kawai" Yoshida <sh...@gmail.com>

---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org


Re: Bugs that depend on other bugs

Posted by Mike Kienenberger <mk...@alaska.net>.
Will Glass-Husain <wg...@forio.com> wrote:
> It seems reasonable to me to keep this as a Velocity bug.  This can be a 
> tickler for updating the jar file once the dependent library fixes the 
bug. 
> It also prevents dup issues from getting created.

And to the end user, it's still a Velocity bug.   End-users should be able 
to view Velocity as a "black box."

-Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org


Re: Bugs that depend on other bugs

Posted by Will Glass-Husain <wg...@forio.com>.
It seems reasonable to me to keep this as a Velocity bug.  This can be a 
tickler for updating the jar file once the dependent library fixes the bug. 
It also prevents dup issues from getting created.

WILL

----- Original Message ----- 
From: "Shinobu Kawai Yoshida" <sh...@gmail.com>
To: "Velocity Developers List" <ve...@jakarta.apache.org>
Sent: Wednesday, January 19, 2005 4:21 AM
Subject: Bugs that depend on other bugs


> Hi Will,
>
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=8651
>>
>>
>> ------- Additional Comments From wglass@forio.com  2005-01-19 
>> 01:50 -------
>> I'm against using setAccessible within Velocity.  It's hard enough to
>> configure the security policies for a webapp container as it is.  Why add
>> another requirement to the mess?
>
> Me too.  -1 for using setAccessible within Velocity.
>
> But what should be done for bugs that depend on other bugs?  Should
> there be a uncommitted patch so whoever can't wait for the fix can
> apply?  Or should we just let them wait for the root bug to get fixed?
> ## As for me, I say redirect them to nag the root bug people.  eg.
> with votes, etc.
>
> FYI, Bugzilla #33020 also depends on a bug of commons-collections.
>   http://issues.apache.org/bugzilla/show_bug.cgi?id=33020
>
> Best regards,
> -- Shinobu
>
> --
> Shinobu "Kawai" Yoshida <sh...@gmail.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org