You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by dl...@apache.org on 2003/10/22 01:57:35 UTC
cvs commit: jakarta-velocity TODO.txt
dlr 2003/10/21 16:57:35
Modified: . TODO.txt
Log:
* TODO.txt
Updated priority of "UML Diagrams" and "Specification Files". Added
"Drop use of Log4J Category class".
Revision Changes Path
1.3 +33 -19 jakarta-velocity/TODO.txt
Index: TODO.txt
===================================================================
RCS file: /home/cvs/jakarta-velocity/TODO.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -u -r1.2 -r1.3
--- TODO.txt 2 Apr 2001 19:36:51 -0000 1.2
+++ TODO.txt 21 Oct 2003 23:57:35 -0000 1.3
@@ -1,27 +1,17 @@
+------------- Critical For Release -------------+
-o UML Diagrams
-
- PLAN:
- Use a tool to reverse engineer the code in XMI so we have
- something to play with in Argo.
-
- STATUS:
- Ilkka Priha has made us a set of XMI files for Velocity,
- I will check them into CVS and we can go from there.
- [JVZ] I've place the XMI file on the apache website
- if anyone wants to take a crack at using ArgoUML.
+No blockers.
-o Specification Files
- PLAN:
- 1. Update the bnf and ast files to reflect latest Velocity code.
- 2. Make sure that the questions in the questions file
- are all answered and dealt with.
+
++------------- Not Critical For Release -------------+
+
+o Drop use of Log4J Category class
+
+ PLAN: Replace with org.apache.log4j.Logger.
STATUS:
- [NONE]
+ [DLR] I will implement this for 1.5 (has open Bugzilla issue).
-+------------- Not Critical For Release -------------+
o Control Caching Resource Usage
@@ -32,7 +22,31 @@
extensively.
PLAN:
- Fix code.
+ Fix code using org.apache.commons.collections.LRUMap class.
STATUS:
[GMJ] Punt for next release.
+ [DLR] I will implement this for 1.5.
+
+
+o Specification Files
+ PLAN:
+ 1. Update the BNF and AST files to reflect latest Velocity code.
+ 2. Make sure that the questions in the questions file
+ are all answered and dealt with.
+
+ STATUS:
+ [NONE]
+
+
+o UML Diagrams
+
+ PLAN:
+ Use a tool to reverse engineer the code in XMI so we have
+ something to play with in Argo.
+
+ STATUS:
+ Ilkka Priha has made us a set of XMI files for Velocity,
+ I will check them into CVS and we can go from there.
+ [JVZ] I've place the XMI file on the apache website
+ if anyone wants to take a crack at using ArgoUML.
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-velocity TODO.txt
Posted by "Daniel L. Rall" <dl...@finemaltcoding.com>.
Geir Magnusson Jr. wrote:
>
> On Wednesday, October 22, 2003, at 06:38 AM, Geir Magnusson Jr. wrote:
>
>>> Not forcing existing code to update their Log4J makes sense, but
>>> the additional complexity for preserving compatibility didn't strike
>>> me as a good trade-off.
>>
>> There doesn't seem to be an overly clean way to do this. Logger is a
>> subclass of Category, so was trying to cook up a strategy to deal with
>> that. However, there's no clean way - if they remove Category as a
>> public class, we're done.
>>
>> So maybe we do this - to be nice to people, we deprecate
>> SimpleLog4JLogSystem class, the old version and make the one you just
>> fixed Log4JLogSystem, as the old Jon one is now gone. I don't think
>> anyone used the old one anyway.
>>
>> That way, existing impls work, people who want to be modern use the
>> new one, and we get rid of the SL4JLS next release. (calling it
>> 'simple' only made sense in the context of the other one anyway :)
>
> Done - I'm not overjoyed about changing Log4JLogSystem like that (moving
> your fixed SL4JLS to L4JLS), but this way, we are backwards compat and
> have new functionality at the same time.
>
> Let us know what you think.
As you, I think it's confusing. At the same time, Log4JLogSystem is a nice
name for what we're providing, and the backwards compat for -- what I assume
to be the more widely used -- SimpleLog4JLogSystem is nice, so the trade-off
is reasonable.
- Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-velocity TODO.txt
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Wednesday, October 22, 2003, at 06:38 AM, Geir Magnusson Jr. wrote:
>
>
>> Not forcing existing code to update their Log4J makes sense, but
>> the additional complexity for preserving compatibility didn't strike
>> me as a good trade-off.
>
> There doesn't seem to be an overly clean way to do this. Logger is a
> subclass of Category, so was trying to cook up a strategy to deal with
> that. However, there's no clean way - if they remove Category as a
> public class, we're done.
>
> So maybe we do this - to be nice to people, we deprecate
> SimpleLog4JLogSystem class, the old version and make the one you just
> fixed Log4JLogSystem, as the old Jon one is now gone. I don't think
> anyone used the old one anyway.
>
> That way, existing impls work, people who want to be modern use the
> new one, and we get rid of the SL4JLS next release. (calling it
> 'simple' only made sense in the context of the other one anyway :)
>
Done - I'm not overjoyed about changing Log4JLogSystem like that
(moving your fixed SL4JLS to L4JLS), but this way, we are backwards
compat and have new functionality at the same time.
Let us know what you think.
--
Geir Magnusson Jr 203-247-1713(m)
geirm@optonline.net
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-velocity TODO.txt
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Tuesday, October 21, 2003, at 09:54 PM, Daniel L. Rall wrote:
> Geir Magnusson Jr. wrote:
>> On Tuesday, October 21, 2003, at 09:42 PM, Daniel L. Rall wrote:
>>> Geir Magnusson Jr. wrote:
> ...
>>>> Re the Log4j, I've started playing with changing that...
>>>
>>> Should be done now.
>> yes, but in a way that breaks things. That's what I was playing with
>> - how not to break people...
> >
> > I'll add my bits to try and be compat.
>
> As Category is being completely removed from the Log4J package after a
> long deprecation period, I don't see much value in continuing to
> support in for post-1.4 releases.
Because we want people to just be able to drop 1.5 in. I agree that
it's old - but not only am I a big fan of not forcing dependencies if
it can be avoided (like commons-*), but hate when component foo forces
a change in component bar. In a production environment, when I may
only have the the resources to focus on replacing one or the other,
tying them together incites justifiably homicidal thoughts.
> Not forcing existing code to update their Log4J makes sense, but the
> additional complexity for preserving compatibility didn't strike me as
> a good trade-off.
There doesn't seem to be an overly clean way to do this. Logger is a
subclass of Category, so was trying to cook up a strategy to deal with
that. However, there's no clean way - if they remove Category as a
public class, we're done.
So maybe we do this - to be nice to people, we deprecate
SimpleLog4JLogSystem class, the old version and make the one you just
fixed Log4JLogSystem, as the old Jon one is now gone. I don't think
anyone used the old one anyway.
That way, existing impls work, people who want to be modern use the new
one, and we get rid of the SL4JLS next release. (calling it 'simple'
only made sense in the context of the other one anyway :)
>
> I'll wait and see what'cha got, unless you feel like spending time
> explaining before hand.
>
>> And we should just chuck Jon's old class. It's now been deprecated
>> through 1.3 and 1.4. Time to go, ja?
>
> Was wondering the same thing. I have no attachment to the
> Log4JLogger. I like APR's compatibility policy, where they don't dump
> deprecated code across minor point releases, but the Log4JLogger has
> already been deprecated so long that I'd rather see it go.
I'm worried that the above plan will be confusing, but I really don't
think anyone used it...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>
--
Geir Magnusson Jr 203-247-1713(m)
geirm@optonline.net
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-velocity TODO.txt
Posted by "Daniel L. Rall" <dl...@finemaltcoding.com>.
Geir Magnusson Jr. wrote:
>
> On Tuesday, October 21, 2003, at 09:42 PM, Daniel L. Rall wrote:
>
>> Geir Magnusson Jr. wrote:
...
>>> Re the Log4j, I've started playing with changing that...
>>
>> Should be done now.
>
> yes, but in a way that breaks things. That's what I was playing with -
> how not to break people...
>
> I'll add my bits to try and be compat.
As Category is being completely removed from the Log4J package after a long
deprecation period, I don't see much value in continuing to support in for
post-1.4 releases. Not forcing existing code to update their Log4J makes
sense, but the additional complexity for preserving compatibility didn't
strike me as a good trade-off.
I'll wait and see what'cha got, unless you feel like spending time explaining
before hand.
> And we should just chuck Jon's
> old class. It's now been deprecated through 1.3 and 1.4. Time to go, ja?
Was wondering the same thing. I have no attachment to the Log4JLogger. I
like APR's compatibility policy, where they don't dump deprecated code across
minor point releases, but the Log4JLogger has already been deprecated so long
that I'd rather see it go.
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-velocity TODO.txt
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Tuesday, October 21, 2003, at 09:42 PM, Daniel L. Rall wrote:
> Geir Magnusson Jr. wrote:
>> I think we should chuck the first two. Who cares? No one has cared
>> for a few years now.
>
> I wouldn't mind UML diagrams, but I don't feel the need for a spec.
>
>> Re the Log4j, I've started playing with changing that...
>
> Should be done now.
yes, but in a way that breaks things. That's what I was playing with -
how not to break people...
I'll add my bits to try and be compat. And we should just chuck Jon's
old class. It's now been deprecated through 1.3 and 1.4. Time to go,
ja?
>
>> On Tuesday, October 21, 2003, at 07:57 PM, dlr@apache.org wrote:
>>> dlr 2003/10/21 16:57:35
>>>
>>> Modified: . TODO.txt
>>> Log:
>>> * TODO.txt
>>> Updated priority of "UML Diagrams" and "Specification Files".
>>> Added
>>> "Drop use of Log4J Category class".
>>>
>>> Revision Changes Path
>>> 1.3 +33 -19 jakarta-velocity/TODO.txt
>>>
>>> Index: TODO.txt
>>> ===================================================================
>>> RCS file: /home/cvs/jakarta-velocity/TODO.txt,v
>>> retrieving revision 1.2
>>> retrieving revision 1.3
>>> diff -u -u -r1.2 -r1.3
>>> --- TODO.txt 2 Apr 2001 19:36:51 -0000 1.2
>>> +++ TODO.txt 21 Oct 2003 23:57:35 -0000 1.3
>>> @@ -1,27 +1,17 @@
>>> +------------- Critical For Release -------------+
>>>
>>> -o UML Diagrams
>>> -
>>> - PLAN:
>>> - Use a tool to reverse engineer the code in XMI so we have
>>> - something to play with in Argo.
>>> -
>>> - STATUS:
>>> - Ilkka Priha has made us a set of XMI files for Velocity,
>>> - I will check them into CVS and we can go from there.
>>> - [JVZ] I've place the XMI file on the apache website
>>> - if anyone wants to take a crack at using ArgoUML.
>>> +No blockers.
>>>
>>> -o Specification Files
>>> - PLAN:
>>> - 1. Update the bnf and ast files to reflect latest Velocity code.
>>> - 2. Make sure that the questions in the questions file
>>> - are all answered and dealt with.
>>> +
>>> ++------------- Not Critical For Release -------------+
>>> +
>>> +o Drop use of Log4J Category class
>>> +
>>> + PLAN: Replace with org.apache.log4j.Logger.
>>>
>>> STATUS:
>>> - [NONE]
>>> + [DLR] I will implement this for 1.5 (has open Bugzilla issue).
>>>
>>> -+------------- Not Critical For Release -------------+
>>>
>>> o Control Caching Resource Usage
>>>
>>> @@ -32,7 +22,31 @@
>>> extensively.
>>>
>>> PLAN:
>>> - Fix code.
>>> + Fix code using org.apache.commons.collections.LRUMap class.
>>>
>>> STATUS:
>>> [GMJ] Punt for next release.
>>> + [DLR] I will implement this for 1.5.
>>> +
>>> +
>>> +o Specification Files
>>> + PLAN:
>>> + 1. Update the BNF and AST files to reflect latest Velocity code.
>>> + 2. Make sure that the questions in the questions file
>>> + are all answered and dealt with.
>>> +
>>> + STATUS:
>>> + [NONE]
>>> +
>>> +
>>> +o UML Diagrams
>>> +
>>> + PLAN:
>>> + Use a tool to reverse engineer the code in XMI so we have
>>> + something to play with in Argo.
>>> +
>>> + STATUS:
>>> + Ilkka Priha has made us a set of XMI files for Velocity,
>>> + I will check them into CVS and we can go from there.
>>> + [JVZ] I've place the XMI file on the apache website
>>> + if anyone wants to take a crack at using ArgoUML.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>
--
Geir Magnusson Jr 203-247-1713(m)
geirm@optonline.net
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-velocity TODO.txt
Posted by "Daniel L. Rall" <dl...@finemaltcoding.com>.
Geir Magnusson Jr. wrote:
> I think we should chuck the first two. Who cares? No one has cared for
> a few years now.
I wouldn't mind UML diagrams, but I don't feel the need for a spec.
> Re the Log4j, I've started playing with changing that...
Should be done now.
> On Tuesday, October 21, 2003, at 07:57 PM, dlr@apache.org wrote:
>
>> dlr 2003/10/21 16:57:35
>>
>> Modified: . TODO.txt
>> Log:
>> * TODO.txt
>> Updated priority of "UML Diagrams" and "Specification Files". Added
>> "Drop use of Log4J Category class".
>>
>> Revision Changes Path
>> 1.3 +33 -19 jakarta-velocity/TODO.txt
>>
>> Index: TODO.txt
>> ===================================================================
>> RCS file: /home/cvs/jakarta-velocity/TODO.txt,v
>> retrieving revision 1.2
>> retrieving revision 1.3
>> diff -u -u -r1.2 -r1.3
>> --- TODO.txt 2 Apr 2001 19:36:51 -0000 1.2
>> +++ TODO.txt 21 Oct 2003 23:57:35 -0000 1.3
>> @@ -1,27 +1,17 @@
>> +------------- Critical For Release -------------+
>>
>> -o UML Diagrams
>> -
>> - PLAN:
>> - Use a tool to reverse engineer the code in XMI so we have
>> - something to play with in Argo.
>> -
>> - STATUS:
>> - Ilkka Priha has made us a set of XMI files for Velocity,
>> - I will check them into CVS and we can go from there.
>> - [JVZ] I've place the XMI file on the apache website
>> - if anyone wants to take a crack at using ArgoUML.
>> +No blockers.
>>
>> -o Specification Files
>> - PLAN:
>> - 1. Update the bnf and ast files to reflect latest Velocity code.
>> - 2. Make sure that the questions in the questions file
>> - are all answered and dealt with.
>> +
>> ++------------- Not Critical For Release -------------+
>> +
>> +o Drop use of Log4J Category class
>> +
>> + PLAN: Replace with org.apache.log4j.Logger.
>>
>> STATUS:
>> - [NONE]
>> + [DLR] I will implement this for 1.5 (has open Bugzilla issue).
>>
>> -+------------- Not Critical For Release -------------+
>>
>> o Control Caching Resource Usage
>>
>> @@ -32,7 +22,31 @@
>> extensively.
>>
>> PLAN:
>> - Fix code.
>> + Fix code using org.apache.commons.collections.LRUMap class.
>>
>> STATUS:
>> [GMJ] Punt for next release.
>> + [DLR] I will implement this for 1.5.
>> +
>> +
>> +o Specification Files
>> + PLAN:
>> + 1. Update the BNF and AST files to reflect latest Velocity code.
>> + 2. Make sure that the questions in the questions file
>> + are all answered and dealt with.
>> +
>> + STATUS:
>> + [NONE]
>> +
>> +
>> +o UML Diagrams
>> +
>> + PLAN:
>> + Use a tool to reverse engineer the code in XMI so we have
>> + something to play with in Argo.
>> +
>> + STATUS:
>> + Ilkka Priha has made us a set of XMI files for Velocity,
>> + I will check them into CVS and we can go from there.
>> + [JVZ] I've place the XMI file on the apache website
>> + if anyone wants to take a crack at using ArgoUML.
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-velocity TODO.txt
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
I think we should chuck the first two. Who cares? No one has cared
for a few years now.
Re the Log4j, I've started playing with changing that...
On Tuesday, October 21, 2003, at 07:57 PM, dlr@apache.org wrote:
> dlr 2003/10/21 16:57:35
>
> Modified: . TODO.txt
> Log:
> * TODO.txt
> Updated priority of "UML Diagrams" and "Specification Files".
> Added
> "Drop use of Log4J Category class".
>
> Revision Changes Path
> 1.3 +33 -19 jakarta-velocity/TODO.txt
>
> Index: TODO.txt
> ===================================================================
> RCS file: /home/cvs/jakarta-velocity/TODO.txt,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -u -u -r1.2 -r1.3
> --- TODO.txt 2 Apr 2001 19:36:51 -0000 1.2
> +++ TODO.txt 21 Oct 2003 23:57:35 -0000 1.3
> @@ -1,27 +1,17 @@
> +------------- Critical For Release -------------+
>
> -o UML Diagrams
> -
> - PLAN:
> - Use a tool to reverse engineer the code in XMI so we have
> - something to play with in Argo.
> -
> - STATUS:
> - Ilkka Priha has made us a set of XMI files for Velocity,
> - I will check them into CVS and we can go from there.
> - [JVZ] I've place the XMI file on the apache website
> - if anyone wants to take a crack at using ArgoUML.
> +No blockers.
>
> -o Specification Files
> - PLAN:
> - 1. Update the bnf and ast files to reflect latest Velocity code.
> - 2. Make sure that the questions in the questions file
> - are all answered and dealt with.
> +
> ++------------- Not Critical For Release -------------+
> +
> +o Drop use of Log4J Category class
> +
> + PLAN: Replace with org.apache.log4j.Logger.
>
> STATUS:
> - [NONE]
> + [DLR] I will implement this for 1.5 (has open Bugzilla issue).
>
> -+------------- Not Critical For Release -------------+
>
> o Control Caching Resource Usage
>
> @@ -32,7 +22,31 @@
> extensively.
>
> PLAN:
> - Fix code.
> + Fix code using org.apache.commons.collections.LRUMap class.
>
> STATUS:
> [GMJ] Punt for next release.
> + [DLR] I will implement this for 1.5.
> +
> +
> +o Specification Files
> + PLAN:
> + 1. Update the BNF and AST files to reflect latest Velocity code.
> + 2. Make sure that the questions in the questions file
> + are all answered and dealt with.
> +
> + STATUS:
> + [NONE]
> +
> +
> +o UML Diagrams
> +
> + PLAN:
> + Use a tool to reverse engineer the code in XMI so we have
> + something to play with in Argo.
> +
> + STATUS:
> + Ilkka Priha has made us a set of XMI files for Velocity,
> + I will check them into CVS and we can go from there.
> + [JVZ] I've place the XMI file on the apache website
> + if anyone wants to take a crack at using ArgoUML.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>
--
Geir Magnusson Jr 203-247-1713(m)
geirm@optonline.net
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org