[
https://issues.apache.org/jira/browse/SHIRO-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Marwell updated SHIRO-572:
-----------------------------------
Fix Version/s: 2.0.0
> Validate everything in 1.2 / 1.3 has merged into 2.0
> ----------------------------------------------------
>
> Key: SHIRO-572
> URL: https://issues.apache.org/jira/browse/SHIRO-572
> Project: Shiro
> Issue Type: Task
> Reporter: Brian Demers
> Priority: Blocker
> Fix For: 2.0.0
>
>
> after a little bit of git-fu I found a handful of commits that may not be
> already in master. (meaning the commit messages from {{1.2}}/{{1.3}} did not
> match with {{master}}. These changes could have been already merged in (this
> would have been while the code was still in svn, so minor changes to commit
> messages was not uncommon.
> Here is the list:
> 57764965c0ec979270822ea4bd07336aed0d2acb - Updated copyright year
> e5ede6dd2bbac9bf3da9fc92daed4f7ab7506a15 - SHIRO-353: fixed logging statement
> 529a39563ba4f0ac77da64476c15ebe636501383 - Upgraded web.xml files to Servlet
> 2.5 and JSTL to 1.2 (tests were failing during release)
> 132ad01845baaefdb132edebcb5c35e059d5ec49 - ignoring test until it can be
> discovered why it fails only during release
> 49499993ba1e40f0242efb69d505a6a8e058c588 - SHIRO-380: added quick patch fix
> for runAs. This fix is point-version backwards and forwards compatible. A
> more suitable longer term solution should be addressed for Shiro 1.3 / 2.0 +
> c0b817c0445d833431d0d7d61d143c80ae0f561f - Make tests using generics compile
> on newer (1.5+) jdks
> Multiple commits from:
> SHIRO-399
> SHIRO-368
> Also, the release profiles and pom structures need a once over, those commits
> are NOT listed above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
