[maven-release-plugin] prepare for next development iteration
NOJIRA Bump SSP dev version
SSP-2150 Fix test broken by Spring error msg changes
SSP-2414 Sinclair-ish header and logo redesign

Mostly the same as the latest Sinclair design in that it uses the same
logo and shrinks the header vertical space accordingly. But the footer
is still 300px tall.
SSP-2414 More Sinclair-ish portal footer styling, but sans black bg

Decided the shorter footer made sense b/c it meant less chance of
accidentally scrolling large portions of the SSP UI off the screen
just to end up looking at a large, most blank swath of "footer".
Still didn't like the short band of black floating in the middle of
larger browser resolutions during login, though, so I removed the
black background style.
SSP-2414 Shrink footer font
SSP-2415 New person merger: NonDuplicatingMultivaluedAttributeMerger

See more details in the comments in added to
personDirectoryContext.xml

rebase
NOJIRA Remove dummy users
SSP-2421 PAGS IPersonTester that toString()s attributes

...so we can support non-string attributes. Booleans in particular.
SSP-2289 Add support for sectionCode and studentUserName SSO params
SSP-2289 Add support for termCode SSO params
SSP-2289, SSP-2422, SSP-2425 Support schoolId in SSO requests

Expands on previous SSP-2289 work to add support for schoolId
as a param to identify the SSO-ing end user. Along the way it
also corrects error response status codes (SSP-2425) and
requires that the SSO-ing end user be resolvable as such
(SSP-2422).

Note that the schoolId support involved some fairly significant,
if small in terms of LoC, changes to core uP/SSP-Platform
user attribute handling. In particular, the default local
attribute mapping in personDirectoryContext.xml changed to
explicitly map 'schoolId' as a queryable logical attribute,
pointed at the 'username' physical attribute by default. I.e.
the queryAttributeMapping config now more closely matches the
resultAttributeMapping config. We had to do this for schoolId
because it doesn't actually have its own physical attribute.
So previously uP would happily query on it for us, but would
never find any results. Once we changed the queryAttributeMapping,
though (<entry key="schoolId" value="username" />), the lookups
still didn't work for two reasons:

  1) LocalAccountPersonAttributeDao wasn't mapping logical
     attribute names to physical attribute names like we expect
     in "standard" PersonDirectory DAOs, so 'studentId' was being
     passed through to the db literally as the attribute name, and:

  2) Once the code was added to actually respect the logical->physical
     mapping query attribute mapping, it still didn't work because
     'username' is modeled differently and has so be called out
     specially to the underlying DAO (JpaLocalAccountDaoImpl).
SSP-2442 Increase SSP portlet timeout back to orig

Had been inadvertently dropped (dramatically) from 20000ms to 120ms
in a3c746e2e445913058bcca76e5a538ef23daa086.
SSP-2452 Specify username data attr name in uPortalJdbcUserSource
SSP-2466, SSP-2289 Pass through unmapped attr queries to local uP DAO

This fixes a regression created by
df33770a7c3429b59ff2aeb2892c52d6d0b47e16 (SSP-2289), which in an
attempt to respect logical->physical attr mappings when querying the
local uP PD DAO, unmapped attr queries were effectively swallowed.
This restores the previous behavior which handled such queries by
using the logical attr name in the client's query as the physical
attr name in the actual db query.
SSP-2306 - Remove portal 'Forgot username...' link
SSP-2508, UP-4066, UP-4105 Manage portlets permissions enforcement.

Addresses CVE-2014-3146 .
Manage Portlets: Group and category selection use permissions to get forest root

This change provides several necessary fixes for delegated portlet administration.
First, it updaes the 'Select Categories' and 'Select Groups' steps by filtering
the available choices based on the user's permissions.  (In the past, Portlet
Administration users were almost always superusers.)  Secondly -- and also in
furtherance of delegated portlet admin -- this change includes several additional
permissions checks during and at the end of the Portlet Manager publishing wizard.
These check are aimed at preventing a Portlet Manager user who is a non-superuser
from stepping outside the bounds of granted authority.

Conflicts:
	pom.xml
	uportal-war/pom.xml
	uportal-war/src/main/java/org/jasig/portal/layout/dlm/remoting/JsonEntityBean.java
SSP-2508, UP-4106 Enforce CONFIG permission.

Addresses CVE-2014-3147.

Conflicts:
	uportal-war/src/main/java/org/jasig/portal/portlet/rendering/PortletRendererImpl.java
UP-4038 : fix http redirect for sonatype snapshot repo
SSP-2380 Blacklist https://oss.sonatype.org/service/local/staging/deploy/maven2

See comments in pom.xml patch.