[WG: I18N & L10N] [Building Sakai] Shouldn't bug reports be easier to read for humans?
Steve Swinsburg
steve.swinsburg at gmail.com
Wed Jul 17 05:09:40 PDT 2013
Add a property, portal.error.pretty=true and then format to your hearts content.
Cheers,
Steve
Sent from my iPad
On 17/07/2013, at 21:50, Aaron Zeckoski <azeckoski at unicon.net> wrote:
> Portal code is part of the critical set with kernel and access and is
> subject to review since breaking it affects nearly everything in
> Sakai. That said, no one should really make changes to the trunk of
> the code without at least one other person looking at those changes.
> It's simply a good practice.
>
> I agree with Matt that this could affect people who scan the logs and
> really should be handled in an additive way instead of simply
> replacing it.
>
> -AZ
>
>
>
> On Wed, Jul 17, 2013 at 4:19 AM, Jean-Francois Leveque
> <jean-francois.leveque at upmc.fr> wrote:
>> I'm personally not aware or reasons to preserve the old values, that's
>> why I was asking. Unless I get answers from people who need the old
>> values to be kept, I won't.
>>
>> I'm adding the production list now to reach a larger audience who might
>> need the old values.
>>
>> Unless this part of the code is subject to review like kernel because
>> changes are known to be risky, I think I can handle it myself.
>>
>> On 17/07/2013 04:12, Matthew Jones wrote:
>>> Agreed. If it's important to you, submit a patch or contract with a
>>> developer/commercial affiliate to have it resolved. Would be a few lines
>>> of code and a few new message strings.
>>>
>>> The code is somewhere in
>>> portal/portal-util/util/src/java/org/sakaiproject/portal/util/ErrorReporter.java
>>>
>>> I think you'd want to preserve the old values in-case anyone is using
>>> them and append new values like Created (formatted)
>>>
>>> Unless it's a high priority bug (breaks tool functionality) or a desired
>>> local feature, generally it could take a while until it gets resolved.
>>>
>>>
>>> On Tue, Jul 16, 2013 at 9:17 PM, Poindexter, David Ray
>>> <davpoind at iupui.edu <mailto:davpoind at iupui.edu>> wrote:
>>>
>>> Dev resources, I'm guessing.
>>>
>>> --
>>> David Poindexter
>>> Sent from my mobile
>>>
>>> On Jul 16, 2013, at 10:49 AM, "Jean-Francois Leveque"
>>> <jean-francois.leveque at upmc.fr
>>> <mailto:jean-francois.leveque at upmc.fr>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I've created https://jira.sakaiproject.org/browse/SAK-22022 as a
>>> feature
>>>> request some time ago.
>>>>
>>>> Do we have reasons not to do this?
>>>>
>>>> Cheers,
>>>> J-F
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> _______________________________________________
> i18n mailing list
> i18n at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/i18n
>
> TO UNSUBSCRIBE: send email to i18n-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
More information about the i18n
mailing list