Versions Compared

Old Version 7

changes.mady.by.user M

Saved on

compared with

New Version 8

changes.mady.by.user M

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

Excerpt

Planned release: 18.08 2013.

Table of Contents
minLevel4
 

Highlights

Updating from 0.27

Databases
Audit trail DB

The information elements have have been changed from varchar(255) to unlimited strings (

Jira Legacy
serverSBForge
keyBITMAG-646
). To update the database do the following:

  • Derby: Either just run the audit trail service, which will automatically update the DB, or run the sql/derby/auditTrailServiceDBUpdate2to3.sql script on the DB.
  • PostgreSQL: Run the sql/postgres/auditTrailServiceDBUpdate2to3.sql script on the DB.
Audit trail contributor DB

The information elements have have been changed from varchar(255) to unlimited strings (

Jira Legacy
serverSBForge
keyBITMAG-646
). Both the reference pillar and integrity service databases needs to be updated To update the database do the following:

  • Derby: Either just run the reference pillar and integrity service, which will automatically update the DB, or run the sql/derby/auditContributorDBUpdate2to3.sql script on the DBs.
  • PostgreSQL: Run the sql/postgres/auditContributorDBUpdate2to3.sql script on the reference pillar and integrity service DBs.
ReferenceSettings
AuditTrailPreservation

The different settings for AuditTrailPreservation has been moved into a dedicated element, <AuditTrailPreservation>. This element is now optional, eg. if undefined no audit trail preservation will be done.

Old settings:

Code Block
....
<AuditTrailServiceSettings>
  ....
      <AuditTrailPreservationInterval>604800000</AuditTrailPreservationInterval>
      <AuditTrailPreservationCollection>TwoPillarCollection</AuditTrailPreservationCollection>
      <AuditTrailPreservationTemporaryDirectory>${build.dir}/test/audittrailservice//tmpDir</AuditTrailPreservationTemporaryDirectory>
  ....
  </AuditTrailServiceSettings>
....

New settings (optional AuditTrailPreservation section):

Code Block
....
<AuditTrailServiceSettings>
  ....
    <AuditTrailPreservation>
      <AuditTrailPreservationInterval>604800000</AuditTrailPreservationInterval>
      <AuditTrailPreservationCollection>TwoPillarCollection</AuditTrailPreservationCollection>
      <AuditTrailPreservationTemporaryDirectory>${build.dir}/test/audittrailservice//tmpDir</AuditTrailPreservationTemporaryDirectory>
    </AuditTrailPreservation>
    ....
  </AuditTrailServiceSettings>
....
Integrity reports

As part of the solution to 

Jira Legacy
serverSBForge
keyBITMAG-862
 a setting defining the integrity report directory has been added to the IntegrityServiceSettings section. This means the integrity service settings needs to be updated with the new setting:

Code Block
...
<IntegrityServiceSettings>
   ...
   <ObsoleteChecksumSettings/>
 <IntegrityReportsDir>${IntegrityReportsDir}</IntegrityReportsDir>
</IntegrityServiceSettings>
Panel
titleDependencies

Message-XML-24
RepositorySettings 10

Panel
titleCompatible pillars
Panel
titleDownloads
Panel
Maven site

Jira Issues
renderModestatic
columnstype,key,priority,summary
titleList of issues resolved in this release
urlhttps://sbforge.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+BITMAG+AND+issuetype+in+%28Bug%2C+Improvement%2C+Epic%2C+Story%2C+Test%29+AND+fixVersion+%3D+"1.0"+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC&tempMax=1000

Jira Issues
renderModestatic
columnstype,key,priority,summary,fixversion
titleKnown bugs found in this release
urlhttps://sbforge.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+BITMAG+AND+issuetype+%3D+Bug+AND+affectedVersion+%3D+"1.0"+ORDER+BY+priority+DESC%2C+updated+DESC&tempMax=1000