You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2007/12/27 06:37:43 UTC
[jira] Created: (LANG-392) Improve javadoc samples
Improve javadoc samples
-----------------------
Key: LANG-392
URL: https://issues.apache.org/jira/browse/LANG-392
Project: Commons Lang
Issue Type: Task
Reporter: Henri Yandell
This was in the STATUS.html. The first step would seem to be to identify the javadoc that is missing example code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (LANG-392) Improve javadoc samples
Posted by Henri Yandell <fl...@gmail.com>.
On Thu, Dec 10, 2009 at 4:04 AM, sebb <se...@gmail.com> wrote:
> On 10/12/2009, Henri Yandell (JIRA) <ji...@apache.org> wrote:
>>
>> [ https://issues.apache.org/jira/browse/LANG-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Henri Yandell closed LANG-392.
>> ------------------------------
>>
>> Resolution: Fixed
>> Fix Version/s: (was: 3.0)
>>
>> I'm closing this as WONTFIX. It's very desirable, but no one has done anything on the subject and I don't see us considering this a release blocker.
>>
>> Most importantly - nothing points to which samples most need improving.
>
> Surely "LATER" would be better in this case?
It's a Bugzilla import status - I've never looked at LATER issues in JIRA :)
My general thinking is that we'll deal with issues on an individual
basis - i.e. their own JIRA issues, rather than an optimistic "make
things nicer" type ticket.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [jira] Closed: (LANG-392) Improve javadoc samples
Posted by sebb <se...@gmail.com>.
On 10/12/2009, Henri Yandell (JIRA) <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/LANG-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Henri Yandell closed LANG-392.
> ------------------------------
>
> Resolution: Fixed
> Fix Version/s: (was: 3.0)
>
> I'm closing this as WONTFIX. It's very desirable, but no one has done anything on the subject and I don't see us considering this a release blocker.
>
> Most importantly - nothing points to which samples most need improving.
Surely "LATER" would be better in this case?
> > Improve javadoc samples
> > -----------------------
> >
> > Key: LANG-392
> > URL: https://issues.apache.org/jira/browse/LANG-392
> > Project: Commons Lang
> > Issue Type: Task
> > Reporter: Henri Yandell
> >
> > This was in the STATUS.html. The first step would seem to be to identify the javadoc that is missing example code.
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
[jira] Closed: (LANG-392) Improve javadoc samples
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LANG-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Yandell closed LANG-392.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.0)
I'm closing this as WONTFIX. It's very desirable, but no one has done anything on the subject and I don't see us considering this a release blocker.
Most importantly - nothing points to which samples most need improving.
> Improve javadoc samples
> -----------------------
>
> Key: LANG-392
> URL: https://issues.apache.org/jira/browse/LANG-392
> Project: Commons Lang
> Issue Type: Task
> Reporter: Henri Yandell
>
> This was in the STATUS.html. The first step would seem to be to identify the javadoc that is missing example code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.