Joern Huxhorn wrote:
It's possible that I'm missing something but I think it should be
removed from the jar.
It has already been taken care of. See SEC-240.
___
Home: http://acegisecurity.org
Acegisecurity-developer mailing list
Angelo Luis wrote:
this is not fixed:
http://opensource.atlassian.com/projects/spring/browse/SEC-99
It isn't fixed for the reasons I provided in the comment, being:
I wish there was a simple way of resolving this issue, but whatever we
do would inevitably break backward compatibility and
this is not fixed:
http://opensource.atlassian.com/projects/spring/browse/SEC-99
It isn't fixed for the reasons I provided in the comment, being:
I wish there was a simple way of resolving this issue, but
whatever we do would inevitably break backward compatibility
and represent a risk as
Hi.
I have a small issue that could probably be fixed for 1.0.0.
I currently have some problems because acegi-security-1.0.0-RC1.jar
contains a log4j.properties file so I can't override it in my final app.
It's possible that I'm missing something but I think it should be
removed from the jar.
this is not fixed: http://opensource.atlassian.com/projects/spring/browse/SEC-99 :( :( :( :( :( :(
On 5/23/06, Ben Alex [EMAIL PROTECTED] wrote:
Hi everyoneI would like to release 1.0.0 final on Friday 26 May. All JIRA issuesassigned to me are now either completed or marked for a future
Hi everyone
I would like to release 1.0.0 final on Friday 26 May. All JIRA issues
assigned to me are now either completed or marked for a future release.
Please note that source code reformatting with Jalopy has been completed
(SEC-97) and the /jalopy.xml file revised. One of the changes
Ben all,
I don't see any items that I'd be able to tackle, so if others feel
the same way, I'd suggest moving them to 1.0.1 or
1.1.0.
Scott
Quoting Ben Alex [EMAIL PROTECTED]:
Hi everyone
I would like to release 1.0.0 final on Friday 26 May. All JIRA issues
assigned to me are now
