Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Sakai Developement Version 23-SNAPSHOT

  1. … 449 more files in changeset.
Sakai Developement Version 20-SNAPSHOT

  1. … 456 more files in changeset.
Releasing Sakai 20.4

  1. … 456 more files in changeset.
Sakai Developement Version 21-SNAPSHOT

  1. … 456 more files in changeset.
Releasing Sakai 21.1

  1. … 456 more files in changeset.
Sakai Developement Version 20-SNAPSHOT

  1. … 456 more files in changeset.
Releasing Sakai 20.3

  1. … 456 more files in changeset.
Sakai Developement Version 21-SNAPSHOT

  1. … 456 more files in changeset.
Releasing Sakai 21.0

  1. … 456 more files in changeset.
Sakai Developement Version 20-SNAPSHOT

  1. … 456 more files in changeset.
Releasing Sakai 20.2

  1. … 456 more files in changeset.
SAK-44463 Update Apache httpcore 5.0 & HttpClient 5.0 (#8683)

  1. … 5 more files in changeset.
Move version to 22-SNAPSHOT

  1. … 456 more files in changeset.
Setting version back to 20-SNAPSHOT for Developement

  1. … 456 more files in changeset.
Releasing Sakai 20.1

  1. … 456 more files in changeset.
Sakai Developement 20-SNAPSHOT

  1. … 456 more files in changeset.
Releasing Sakai 20.0

  1. … 456 more files in changeset.
SAK-43092 - Fix up POMs for Eclipse compatibility (#7825)

There were a few modules that would compile with Maven directly, but

throw errors when imported as Eclipse projects. The main two issues were

in the Java EE API and a Jackson coordinate change.

There are two minor code changes that I expect would have broken Maven

builds, but apparently did not. One was a test class/package mismatch

in LTI and the other was some missing method implementations for an XML

class in rwiki.

  1. … 20 more files in changeset.
SAK-43092 - Fix up POMs for Eclipse compatibility (#7825)

There were a few modules that would compile with Maven directly, but

throw errors when imported as Eclipse projects. The main two issues were

in the Java EE API and a Jackson coordinate change.

There are two minor code changes that I expect would have broken Maven

builds, but apparently did not. One was a test class/package mismatch

in LTI and the other was some missing method implementations for an XML

class in rwiki.

(cherry picked from commit a5fd8dfc95d0aa6d75deeda35e063e54c016e852)

  1. … 20 more files in changeset.
SAK-43092 - Fix up POMs for Eclipse compatibility

There were a few modules that would compile with Maven directly, but

throw errors when imported as Eclipse projects. The main two issues were

in the Java EE API and a Jackson coordinate change.

There are two minor code changes that I expect would have broken Maven

builds, but apparently did not. One was a test class/package mismatch

in LTI and the other was some missing method implementations for an XML

class in rwiki.

  1. … 20 more files in changeset.
SAK-43092 - Fix up POMs for Eclipse compatibility

There were a few modules that would compile with Maven directly, but

throw errors when imported as Eclipse projects. The main two issues were

in the Java EE API and a Jackson coordinate change.

There are two minor code changes that I expect would have broken Maven

builds, but apparently did not. One was a test class/package mismatch

in LTI and the other was some missing method implementations for an XML

class in rwiki.

  1. … 19 more files in changeset.
Update master to new developement version for Sakai 21

  1. … 459 more files in changeset.
SAK-42478 Google Drive & OneDrive: pom master (#7340)

* SAK-42478 Google Drive & OneDrive: pom master

* SAK-42478 delete commons-collections

  1. … 1 more file in changeset.
SAK-42190 OneDrive integration with Sakai filepicker (#7149)

* SAK-42190 OneDrive integration with Sakai filepicker

* Remove the handler from Portal and improve navigation

* More fixes from the review

* More changes from the review

  1. … 32 more files in changeset.