Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

 

Planned release: 2013-08-19.

 

Highlights

Updating from 0.27

Databases
Audit trail DB

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

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
). 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 ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. ). 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 ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. ). 

Old settings:

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

New settings (optional AuditTrailPreservation section):

....
<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  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  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:

...
<IntegrityServiceSettings>
   ...
   <ObsoleteChecksumSettings/>
 <IntegrityReportsDir>${IntegrityReportsDir}</IntegrityReportsDir>
</IntegrityServiceSettings>

type key priority summary

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

type key priority summary fixversion

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels