You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by "Mikhail Loenko (JIRA)" <ji...@apache.org> on 2006/03/02 14:08:39 UTC

[jira] Created: (HARMONY-153) mark deprecated API

mark deprecated API
-------------------

         Key: HARMONY-153
         URL: http://issues.apache.org/jira/browse/HARMONY-153
     Project: Harmony
        Type: Improvement
  Components: Classlib  
    Reporter: Mikhail Loenko
    Priority: Minor


As agreed on the mailing list deprecated classes, methods, etc should be marked

I'm going to provide a patch shortly

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Resolved: (HARMONY-153) mark deprecated API

Posted by Mikhail Loenko <ml...@gmail.com>.
Verified

2006/3/3, Tim Ellison <t....@gmail.com>:
> Mikhail Loenko wrote:
> > One fix was applied to a wrong file, it was applied to
> >    java.security.Policy
> > instead of
> >    javaX.security.Policy
>
> javax.security.auth.Policy, right?  I've moved it -- thanks.
>
> (My patch program wouldn'd read your diff for some reason, so I did it
> by hand, wrongly).  Thanks for catching that.
>
> Please take a look at the correction at repo revision 382802.
>
> Regards,
> Tim
>
> > Remaining fixes and comments are OK
> >
> > Thanks,
> > Mikhail
> >
> > 2006/3/2, Tim Ellison (JIRA) <ji...@apache.org>:
> >>     [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
> >>
> >> Tim Ellison resolved HARMONY-153:
> >> ---------------------------------
> >>
> >>    Resolution: Fixed
> >>
> >> Mikhail,
> >>
> >> I've fixed the problem at repo revision 382400, but to fit in with common convention I have added some explanations to the deprecation tag.  Please review and check that they are reasonable.
> >>
> >> Thanks,
> >> Tim
> >>
> >>> mark deprecated API
> >>> -------------------
> >>>
> >>>          Key: HARMONY-153
> >>>          URL: http://issues.apache.org/jira/browse/HARMONY-153
> >>>      Project: Harmony
> >>>         Type: Improvement
> >>>   Components: Classlib
> >>>     Reporter: Mikhail Loenko
> >>>     Assignee: Tim Ellison
> >>>     Priority: Minor
> >>>  Attachments: deprecated.txt
> >>>
> >>> As agreed on the mailing list deprecated classes, methods, etc should be marked
> >>> I'm going to provide a patch shortly
> >> --
> >> This message is automatically generated by JIRA.
> >> -
> >> If you think it was sent incorrectly contact one of the administrators:
> >>   http://issues.apache.org/jira/secure/Administrators.jspa
> >> -
> >> For more information on JIRA, see:
> >>   http://www.atlassian.com/software/jira
> >>
> >>
> >
>
> --
>
> Tim Ellison (t.p.ellison@gmail.com)
> IBM Java technology centre, UK.
>

Re: [jira] Resolved: (HARMONY-153) mark deprecated API

Posted by Tim Ellison <t....@gmail.com>.
Mikhail Loenko wrote:
> One fix was applied to a wrong file, it was applied to
>    java.security.Policy
> instead of
>    javaX.security.Policy

javax.security.auth.Policy, right?  I've moved it -- thanks.

(My patch program wouldn'd read your diff for some reason, so I did it
by hand, wrongly).  Thanks for catching that.

Please take a look at the correction at repo revision 382802.

Regards,
Tim

> Remaining fixes and comments are OK
> 
> Thanks,
> Mikhail
> 
> 2006/3/2, Tim Ellison (JIRA) <ji...@apache.org>:
>>     [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
>>
>> Tim Ellison resolved HARMONY-153:
>> ---------------------------------
>>
>>    Resolution: Fixed
>>
>> Mikhail,
>>
>> I've fixed the problem at repo revision 382400, but to fit in with common convention I have added some explanations to the deprecation tag.  Please review and check that they are reasonable.
>>
>> Thanks,
>> Tim
>>
>>> mark deprecated API
>>> -------------------
>>>
>>>          Key: HARMONY-153
>>>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>>>      Project: Harmony
>>>         Type: Improvement
>>>   Components: Classlib
>>>     Reporter: Mikhail Loenko
>>>     Assignee: Tim Ellison
>>>     Priority: Minor
>>>  Attachments: deprecated.txt
>>>
>>> As agreed on the mailing list deprecated classes, methods, etc should be marked
>>> I'm going to provide a patch shortly
>> --
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the administrators:
>>   http://issues.apache.org/jira/secure/Administrators.jspa
>> -
>> For more information on JIRA, see:
>>   http://www.atlassian.com/software/jira
>>
>>
> 

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.

Re: [jira] Resolved: (HARMONY-153) mark deprecated API

Posted by Mikhail Loenko <ml...@gmail.com>.
One fix was applied to a wrong file, it was applied to
   java.security.Policy
instead of
   javaX.security.Policy

Remaining fixes and comments are OK

Thanks,
Mikhail

2006/3/2, Tim Ellison (JIRA) <ji...@apache.org>:
>     [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
>
> Tim Ellison resolved HARMONY-153:
> ---------------------------------
>
>    Resolution: Fixed
>
> Mikhail,
>
> I've fixed the problem at repo revision 382400, but to fit in with common convention I have added some explanations to the deprecation tag.  Please review and check that they are reasonable.
>
> Thanks,
> Tim
>
> > mark deprecated API
> > -------------------
> >
> >          Key: HARMONY-153
> >          URL: http://issues.apache.org/jira/browse/HARMONY-153
> >      Project: Harmony
> >         Type: Improvement
> >   Components: Classlib
> >     Reporter: Mikhail Loenko
> >     Assignee: Tim Ellison
> >     Priority: Minor
> >  Attachments: deprecated.txt
> >
> > As agreed on the mailing list deprecated classes, methods, etc should be marked
> > I'm going to provide a patch shortly
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>   http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>   http://www.atlassian.com/software/jira
>
>

Re: [jira] Closed: (HARMONY-153) mark deprecated API

Posted by Mikhail Loenko <ml...@gmail.com>.
Seems like if the whole class is deprecated we have to mark all the
constructors and methods also.

See comparison results:
http://www.kaffe.org/~stuart/japi/htmlout/h-jdk15-harmony.html#err_bad_java_security

Thanks,
Mikhail

2006/3/7, Tim Ellison (JIRA) <ji...@apache.org>:
>     [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
>
> Tim Ellison closed HARMONY-153:
> -------------------------------
>
>
> Verified by Mikhail
>
> > mark deprecated API
> > -------------------
> >
> >          Key: HARMONY-153
> >          URL: http://issues.apache.org/jira/browse/HARMONY-153
> >      Project: Harmony
> >         Type: Improvement
> >   Components: Classlib
> >     Reporter: Mikhail Loenko
> >     Assignee: Tim Ellison
> >     Priority: Minor
> >  Attachments: deprecated.txt
> >
> > As agreed on the mailing list deprecated classes, methods, etc should be marked
> > I'm going to provide a patch shortly
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>   http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>   http://www.atlassian.com/software/jira
>
>

Re: jiritus

Posted by Geir Magnusson Jr <ge...@pobox.com>.

Tim Ellison wrote:
> Geir Magnusson Jr wrote:
>> Um.  Sorry - I take back the first part.  I misread it.  I thought you
>> were putting it in yourself...  Never mind.  There's nothing to see
>> here.  Look!  An eagle!  Over there!
> 
> Where? where?  looks like a sparrow to me.
> 
>> My [friendly] rant about JIRA still stands tho... :)
> 
> I actually don't mind discussions via JIRA, they all come out threaded
> on the dev- list for me anyways so it doesn't look much different to the
> normal banter.  And I prefer to take in fixes etc. via JIRA so we have
> traceability where they were not authored by card-carrying ACQ people
> (should we ever need to back them out).

Two different issues.  Fixes should come in via JIRA from 
non-committers.  THen we have a clear record.

But JIRA output is pretty ugly.

Can we please try to have the tech discussions here when possible?

geir

> 
> Regards,
> Tim
> 
>> geir
>>
>>
>> Geir Magnusson Jr wrote:
>>> Please note that there's no need to pre-JIRA something you're about to
>>> do, unless your short term memory is so shot that you might forget and
>>> wander away from your desk, humming Oh Canada! in a minor key while
>>> looking for the body of Jimmy Hoffa....
>>>
>>> Just do it.  Maybe a quick note to the mail list, but just note it.
>>>
>>> <soapbox>
>>>
>>> I think we're overusing JIRA.  It seems the discussions get buried in
>>> there.   Clearly it's a great way to note things we don't want to
>>> forget about, or submit patches and features, but can we try to get
>>> some of the tech discussions out and onto the list?
>>>
>>> I filter JIRA email automatically, as I consider harmony-dev@ as the
>>> place to discuss things...
>>>
>>> Just my $0.02
>>>
>>> </soapbox>
>>>
>>> geir
>>>
>>>
>>> Tim Ellison (JIRA) wrote:
>>>>      [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
>>>>
>>>> Tim Ellison reassigned HARMONY-153:
>>>> -----------------------------------
>>>>
>>>>     Assign To: Tim Ellison
>>>>
>>>>> mark deprecated API
>>>>> -------------------
>>>>>
>>>>>          Key: HARMONY-153
>>>>>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>>>>>      Project: Harmony
>>>>>         Type: Improvement
>>>>>   Components: Classlib
>>>>>     Reporter: Mikhail Loenko
>>>>>     Assignee: Tim Ellison
>>>>>     Priority: Minor
>>>>>  Attachments: deprecated.txt
>>>>>
>>>>> As agreed on the mailing list deprecated classes, methods, etc
>>>>> should be marked
>>>>> I'm going to provide a patch shortly
>>>
> 

jiritus (was: Re: [jira] Assigned: (HARMONY-153) mark deprecated API)

Posted by Tim Ellison <t....@gmail.com>.
Geir Magnusson Jr wrote:
> Um.  Sorry - I take back the first part.  I misread it.  I thought you
> were putting it in yourself...  Never mind.  There's nothing to see
> here.  Look!  An eagle!  Over there!

Where? where?  looks like a sparrow to me.

> My [friendly] rant about JIRA still stands tho... :)

I actually don't mind discussions via JIRA, they all come out threaded
on the dev- list for me anyways so it doesn't look much different to the
normal banter.  And I prefer to take in fixes etc. via JIRA so we have
traceability where they were not authored by card-carrying ACQ people
(should we ever need to back them out).

Regards,
Tim

> geir
> 
> 
> Geir Magnusson Jr wrote:
>> Please note that there's no need to pre-JIRA something you're about to
>> do, unless your short term memory is so shot that you might forget and
>> wander away from your desk, humming Oh Canada! in a minor key while
>> looking for the body of Jimmy Hoffa....
>>
>> Just do it.  Maybe a quick note to the mail list, but just note it.
>>
>> <soapbox>
>>
>> I think we're overusing JIRA.  It seems the discussions get buried in
>> there.   Clearly it's a great way to note things we don't want to
>> forget about, or submit patches and features, but can we try to get
>> some of the tech discussions out and onto the list?
>>
>> I filter JIRA email automatically, as I consider harmony-dev@ as the
>> place to discuss things...
>>
>> Just my $0.02
>>
>> </soapbox>
>>
>> geir
>>
>>
>> Tim Ellison (JIRA) wrote:
>>>      [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
>>>
>>> Tim Ellison reassigned HARMONY-153:
>>> -----------------------------------
>>>
>>>     Assign To: Tim Ellison
>>>
>>>> mark deprecated API
>>>> -------------------
>>>>
>>>>          Key: HARMONY-153
>>>>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>>>>      Project: Harmony
>>>>         Type: Improvement
>>>>   Components: Classlib
>>>>     Reporter: Mikhail Loenko
>>>>     Assignee: Tim Ellison
>>>>     Priority: Minor
>>>>  Attachments: deprecated.txt
>>>>
>>>> As agreed on the mailing list deprecated classes, methods, etc
>>>> should be marked
>>>> I'm going to provide a patch shortly
>>>
>>
>>
> 

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.

Re: [jira] Assigned: (HARMONY-153) mark deprecated API

Posted by Geir Magnusson Jr <ge...@pobox.com>.
Um.  Sorry - I take back the first part.  I misread it.  I thought you 
were putting it in yourself...  Never mind.  There's nothing to see 
here.  Look!  An eagle!  Over there!

My [friendly] rant about JIRA still stands tho... :)

geir


Geir Magnusson Jr wrote:
> Please note that there's no need to pre-JIRA something you're about to 
> do, unless your short term memory is so shot that you might forget and 
> wander away from your desk, humming Oh Canada! in a minor key while 
> looking for the body of Jimmy Hoffa....
> 
> Just do it.  Maybe a quick note to the mail list, but just note it.
> 
> <soapbox>
> 
> I think we're overusing JIRA.  It seems the discussions get buried in 
> there.   Clearly it's a great way to note things we don't want to forget 
> about, or submit patches and features, but can we try to get some of the 
> tech discussions out and onto the list?
> 
> I filter JIRA email automatically, as I consider harmony-dev@ as the 
> place to discuss things...
> 
> Just my $0.02
> 
> </soapbox>
> 
> geir
> 
> 
> Tim Ellison (JIRA) wrote:
>>      [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
>>
>> Tim Ellison reassigned HARMONY-153:
>> -----------------------------------
>>
>>     Assign To: Tim Ellison
>>
>>> mark deprecated API
>>> -------------------
>>>
>>>          Key: HARMONY-153
>>>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>>>      Project: Harmony
>>>         Type: Improvement
>>>   Components: Classlib
>>>     Reporter: Mikhail Loenko
>>>     Assignee: Tim Ellison
>>>     Priority: Minor
>>>  Attachments: deprecated.txt
>>>
>>> As agreed on the mailing list deprecated classes, methods, etc should 
>>> be marked
>>> I'm going to provide a patch shortly
>>
> 
> 

Re: [jira] Assigned: (HARMONY-153) mark deprecated API

Posted by Geir Magnusson Jr <ge...@pobox.com>.
Please note that there's no need to pre-JIRA something you're about to 
do, unless your short term memory is so shot that you might forget and 
wander away from your desk, humming Oh Canada! in a minor key while 
looking for the body of Jimmy Hoffa....

Just do it.  Maybe a quick note to the mail list, but just note it.

<soapbox>

I think we're overusing JIRA.  It seems the discussions get buried in 
there.   Clearly it's a great way to note things we don't want to forget 
about, or submit patches and features, but can we try to get some of the 
tech discussions out and onto the list?

I filter JIRA email automatically, as I consider harmony-dev@ as the 
place to discuss things...

Just my $0.02

</soapbox>

geir


Tim Ellison (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
> 
> Tim Ellison reassigned HARMONY-153:
> -----------------------------------
> 
>     Assign To: Tim Ellison
> 
>> mark deprecated API
>> -------------------
>>
>>          Key: HARMONY-153
>>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>>      Project: Harmony
>>         Type: Improvement
>>   Components: Classlib
>>     Reporter: Mikhail Loenko
>>     Assignee: Tim Ellison
>>     Priority: Minor
>>  Attachments: deprecated.txt
>>
>> As agreed on the mailing list deprecated classes, methods, etc should be marked
>> I'm going to provide a patch shortly
> 

[jira] Assigned: (HARMONY-153) mark deprecated API

Posted by "Tim Ellison (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]

Tim Ellison reassigned HARMONY-153:
-----------------------------------

    Assign To: Tim Ellison

> mark deprecated API
> -------------------
>
>          Key: HARMONY-153
>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>      Project: Harmony
>         Type: Improvement
>   Components: Classlib
>     Reporter: Mikhail Loenko
>     Assignee: Tim Ellison
>     Priority: Minor
>  Attachments: deprecated.txt
>
> As agreed on the mailing list deprecated classes, methods, etc should be marked
> I'm going to provide a patch shortly

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (HARMONY-153) mark deprecated API

Posted by "Tim Ellison (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
     
Tim Ellison resolved HARMONY-153:
---------------------------------

    Resolution: Fixed

Mikhail,

I've fixed the problem at repo revision 382400, but to fit in with common convention I have added some explanations to the deprecation tag.  Please review and check that they are reasonable.

Thanks,
Tim

> mark deprecated API
> -------------------
>
>          Key: HARMONY-153
>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>      Project: Harmony
>         Type: Improvement
>   Components: Classlib
>     Reporter: Mikhail Loenko
>     Assignee: Tim Ellison
>     Priority: Minor
>  Attachments: deprecated.txt
>
> As agreed on the mailing list deprecated classes, methods, etc should be marked
> I'm going to provide a patch shortly

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (HARMONY-153) mark deprecated API

Posted by "Tim Ellison (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]
     
Tim Ellison closed HARMONY-153:
-------------------------------


Verified by Mikhail

> mark deprecated API
> -------------------
>
>          Key: HARMONY-153
>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>      Project: Harmony
>         Type: Improvement
>   Components: Classlib
>     Reporter: Mikhail Loenko
>     Assignee: Tim Ellison
>     Priority: Minor
>  Attachments: deprecated.txt
>
> As agreed on the mailing list deprecated classes, methods, etc should be marked
> I'm going to provide a patch shortly

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (HARMONY-153) mark deprecated API

Posted by "Mikhail Loenko (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HARMONY-153?page=all ]

Mikhail Loenko updated HARMONY-153:
-----------------------------------

    Attachment: deprecated.txt

patch

> mark deprecated API
> -------------------
>
>          Key: HARMONY-153
>          URL: http://issues.apache.org/jira/browse/HARMONY-153
>      Project: Harmony
>         Type: Improvement
>   Components: Classlib
>     Reporter: Mikhail Loenko
>     Priority: Minor
>  Attachments: deprecated.txt
>
> As agreed on the mailing list deprecated classes, methods, etc should be marked
> I'm going to provide a patch shortly

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira