On Jan 21, 2009, at 9:09 AM, Les Hazlewood wrote:
I agree - I only kept it in Jira because I saw two comments there
first, and
I didn't think it would be an issue since all Jira comments are
mailed to
the mailing list. I'll keep them on the dev list from now on ;)
So, based on the most recent comments, can we resolve the issue now
and open
others later if necessary?
Sure. Sounds good. THanks!
Regards,
Alan
On Wed, Jan 21, 2009 at 11:29 AM, Alan Cabrera (JIRA)
<[email protected]>wrote:
[
https://issues.apache.org/jira/browse/JSEC-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665873
#action_12665873]
Alan Cabrera commented on JSEC-8:
---------------------------------
Guys, this should be on the mailing list.
Change instance variables from private to protected
---------------------------------------------------
Key: JSEC-8
URL: https://issues.apache.org/jira/browse/JSEC-8
Project: JSecurity
Issue Type: Improvement
Components: Specification API
Reporter: Alan Cabrera
Assignee: Les Hazlewood
Fix For: 1.0
Currently most instance variables are private, which limits
options when
the classes are extended. We are standardizing on protected from
now on, but
the existing classes should be updated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
