Page Comparison

...

• If you encounter "Unable to read the metadata file for artifact" errors in your ant builds, delete the containing directory for the offending file listed in the error, then try black-listing several repos in your ~/.m2/settings.xml. If you don't have that file already, use the following: 

  No Format

  <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <profiles> <profile> <id>exclude-bad-repos</id> <activation> <activeByDefault>true</activeByDefault> </activation> <repositories> <repository> <id>codehaus</id> <url>http://repository.codehaus.org</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> <repository> <id>sonatype-nexus-snapshots</id> <url>https://oss.sonatype.org/content/repositories/snapshots/</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> <repository> <id>sonatype-nexus-staging</id> <url>http://oss.sonatype.org/service/local/staging/deploy/maven2/</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> </profile> </profiles> </settings>

  This issue is being tracked by 

  Jira Legacy
  server JASIG Issue Tracker serverId 76221f40-4501-3df1-8578-6c87908cbdf7 key SSP-2380

• Default roles assignments for access to Reports and Manage Users was changed.  By default only the administrator and developer roles will have access to Reports and Manage Users.  The following data imports (5 total) need to be executed from the SSP-Platform directory

  Code Block

  SSP_CONFIGDIR=/path/to/config/dir ant -Dmaven.test.skip=true -Dfile=uportal-war/src/main/data/ssp_entities/permission_set/SSP_SUPPORT_STAFF__REPORT_READ__SSP.permission-set.xml data-import SSP_CONFIGDIR=/path/to/config/dir ant -Dmaven.test.skip=true -Dfile=uportal-war/src/main/data/ssp_entities/patches-SSP-2-0-0/SSP-1526/permission_set/SSP_COACH__REPORT_READ__SSP.permission-set.xml data-import SSP_CONFIGDIR=/path/to/config/dir ant -Dmaven.test.skip=true -Dfile=uportal-war/src/main/data/ssp_entities/portlet-definition/SSP_Reports.portlet-definition.xml data-import SSP_CONFIGDIR=/path/to/config/dir ant -Dmaven.test.skip=true -Dfile=uportal-war/src/main/data/ssp_entities/fragment-definition/ssp-reports-lo.fragment-definition.xml data-import SSP_CONFIGDIR=/path/to/config/dir ant -Dmaven.test.skip=true -Dfile=uportal-war/src/main/data/ssp_entities/fragment-definition/manage-users-lo.fragment-definition.xml data-import

• As part of the Action Plan tool, a new permission for the Strengths section was added.  The new permission needs to be imported by executing the import below (1 total)

  Code Block
  SSP_CONFIGDIR=/path/to/your/ssp/config/dir ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-4-0/SSP-2154 data-import

  Warning

  Quite a few changes were made to the email and MAP message templates.  The latest message templates are documented individually in the Users Guide.  If you have updated any of the message templates since version 2.0.0, it is strongly recommended to review the new message templates as changes to the person definition to improve performance have changed message variables, specifically createdBy and modifiedBy.

• The following code block can be added to the MAP Plan Printout and MAP Plan Full Printout message templates to include notes entered when emailing a Plan.  The notes can be placed in any position desired.  The default message templates place the notes above the institution image (MAP Plan Full Printout) and term/course table (MAP Plan Printout).

  Code Block
  #if("$!emailNotes" != "") <div> <p>$!studentFullName,</p> <p> $!emailNotes </p> </div> #end

...