bitrepository-reference

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[maven-release-plugin] prepare for next development iteration

    • -1
    • +1
    /bitrepository-audit-trail-service/pom.xml
    • -1
    • +1
    /bitrepository-integrity-service/pom.xml
    • -1
    • +1
    /bitrepository-monitoring-service/pom.xml
    • -1
    • +1
    /bitrepository-reference-pillar/pom.xml
    • -1
    • +1
    /bitrepository-reference-settings/pom.xml
[maven-release-plugin] prepare release bitrepository-parent-1.9.0.1

    • -1
    • +1
    /bitrepository-audit-trail-service/pom.xml
    • -1
    • +1
    /bitrepository-integrity-service/pom.xml
    • -1
    • +1
    /bitrepository-monitoring-service/pom.xml
    • -1
    • +1
    /bitrepository-reference-pillar/pom.xml
    • -1
    • +1
    /bitrepository-reference-settings/pom.xml
Update project version to 1.9.0.1-SNAPSHOT

    • -1
    • +1
    /bitrepository-audit-trail-service/pom.xml
    • -1
    • +1
    /bitrepository-integrity-service/pom.xml
    • -1
    • +1
    /bitrepository-monitoring-service/pom.xml
    • -1
    • +1
    /bitrepository-reference-pillar/pom.xml
    • -1
    • +1
    /bitrepository-reference-settings/pom.xml
remove forgotten out-commented code in PermissionStore

remove forgotten out-commented code in PermissionStore

Pokkers! Den havde jeg glemt. Gone now

Pokkers! Den havde jeg glemt. Gone now

Måske fjern den udkommenterede del?

Måske fjern den udkommenterede del?

Fair nok. Var bare ikke klar over, at vi var begyndt at bruge den notation.

Fair nok.
Var bare ikke klar over, at vi var begyndt at bruge den notation.

Vi gør god brug af 'diamond' notationen rundt omkring. Typen står jo allerede der hvor variablen er erklæret (se linje 82). Finder du det svært at læse?

Vi gør god brug af 'diamond' notationen rundt omkring. Typen står jo allerede der hvor variablen er erklæret (se linje 82). Finder du det svært at læse?

Ikke nogen type på hash-settet? allowedOperationPermissions = new HashSet<OperationPermission>();

Ikke nogen type på hash-settet?

allowedOperationPermissions = new HashSet<OperationPermission>();
BITMAG-1136 Change permission checking to take collectionID into account when authorizing an...
BITMAG-1136 Change permission checking to take collectionID into account when authorizing an...
BITMAG-1136 Change permission checking to take collectionID into account when authorizing an operation

BITMAG-1136 Change permission checking to take collectionID into account when authorizing an operation

SettingsUtils is used non-statically.
SettingsUtils is used non-statically.
This does not really work

  1. … 50 more files in changeset.
AccessComponentFactory non-static

SettingsUtils is used non-statically.

  1. … 40 more files in changeset.
[maven-release-plugin] prepare for next development iteration

    • -1
    • +1
    /bitrepository-audit-trail-service/pom.xml
    • -1
    • +1
    /bitrepository-integrity-service/pom.xml
    • -1
    • +1
    /bitrepository-monitoring-service/pom.xml
    • -1
    • +1
    /bitrepository-reference-pillar/pom.xml
    • -1
    • +1
    /bitrepository-reference-settings/pom.xml
[maven-release-plugin] prepare release bitrepository-parent-1.9

    • -1
    • +1
    /bitrepository-audit-trail-service/pom.xml
    • -1
    • +1
    /bitrepository-integrity-service/pom.xml
    • -1
    • +1
    /bitrepository-monitoring-service/pom.xml
    • -1
    • +1
    /bitrepository-reference-pillar/pom.xml
    • -1
    • +1
    /bitrepository-reference-settings/pom.xml
minimum corrections to fix javadoc validity

[maven-release-plugin] rollback the release of bitrepository-parent-1.9

    • -1
    • +1
    /bitrepository-audit-trail-service/pom.xml
    • -1
    • +1
    /bitrepository-integrity-service/pom.xml
    • -1
    • +1
    /bitrepository-monitoring-service/pom.xml
    • -1
    • +1
    /bitrepository-reference-pillar/pom.xml
    • -1
    • +1
    /bitrepository-reference-settings/pom.xml
[maven-release-plugin] prepare for next development iteration

    • -1
    • +1
    /bitrepository-audit-trail-service/pom.xml
    • -1
    • +1
    /bitrepository-integrity-service/pom.xml
    • -1
    • +1
    /bitrepository-monitoring-service/pom.xml
    • -1
    • +1
    /bitrepository-reference-pillar/pom.xml
    • -1
    • +1
    /bitrepository-reference-settings/pom.xml
[maven-release-plugin] prepare release bitrepository-parent-1.9

    • -1
    • +1
    /bitrepository-audit-trail-service/pom.xml
    • -1
    • +1
    /bitrepository-integrity-service/pom.xml
    • -1
    • +1
    /bitrepository-monitoring-service/pom.xml
    • -1
    • +1
    /bitrepository-reference-pillar/pom.xml
    • -1
    • +1
    /bitrepository-reference-settings/pom.xml
Followup on CR-BITMAG-381

It seems nice, but all the file-ids it finds starts with the relative path to the folderDir. Thus a FileID = folder1/folder2/file1 will be retrieved as CollectionID/folderDir/folder1/folder2/file1 ...

It seems nice, but all the file-ids it finds starts with the relative path to the folderDir.
Thus a FileID = folder1/folder2/file1
will be retrieved as CollectionID/folderDir/folder1/folder2/file1

This must be an optimization for another day