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 »

MyTimetable 3.0 is currently in the state 'in development', however we do have a branch available that can be considered 'stable'. Some customers are already using this stable branch, but we recommend most customers to stay at version 2.7 till the last features of 3.0 have been implemented. These release notes are work in progress, and planned features may change at any time. MyTimetable 3.0 is tracked using the git branches: master (for the unstable features) and rb-3.0 (for the stable branch).

MyTimetable 3.0 is a major feature release and introduces direct, push-based, synchronisation support for Microsoft Exchange, Office 365 and Google Calendar. These features are not 'plug and play' but require additional set up and maintenance and are thus not part of a regular upgrade. Please contact us for details.

Next to the push-based synchronisation, MyTimetable 3.0 offers a polished user interface, changes in the iCalendar feed handling, and many back-end changes to make the system perform better than ever.

All work involved in upgrading to the latest MyTimetable version (configuration, building, testing) is free of charge for our customers with a Software Assurance or All-In support agreement.

Functional changes

  • As usual, many small bug fixes and changes are included in this release. 416 issues were fixed in 701 commits.

Non-functional, technical and back-end changes

The following changes have been made to the MyTimetable backend and underlying software, and have no direct impact on MyTimetable functionality:

  • The project has been divided into separate modules: mytimetable-common, mytimetable-core, mytimetable-dataprovider-syllabus, mytimetable-web-shared, mytimetable-web-server, mytimetable-web-gwt and mytimetable-web-mobile.

  • The compatibility level of all source has been updated to Java 7 and the source was stripped from unnecessary type information by introducing the diamond operator.
  • Switch to Thymeleaf based templates, to better separate view and controller logic.
  • GWT upgrade to version 2.7.0. This also means we switched to 'super-dev' mode and are now using Java 7 source level for the GWT sources.
  • Removed AspectJ from the build pipeline and switched to Spring-based aspects. We were not really using the extra AspectJ features, and using AspectJ did interfere with the IDE/IntelliJ build chain, so we chose to remove it.
  • Introduced a Gulp / SASS / Bower based build chain for many of our assets (CSS, Bootstrap, JS). During this process many of these dependencies were also upgraded to the latest version.
  • The following dependencies were upgraded:

    • Spring (4.1.5)

    • Spring Security (3.2.0)

    • Gradle (2.3)

    • AspectJ (1.7.4)
    • Joda-Time (2.7)
    • Servlet API (3.1.0)
    • Apache CXF (3.0.4)
    • Flyway (3.1)
    • MySQL connector (5.1.34)
    • HikariCP (2.3.2)
    • slf4j (1.7.10)
    • Guava (18)
    • Jackson (2.5.1)
    • Commons-codec (1.10)

Removed and deprecated features

The following features from earlier MyTimetable versions have been deprecated, removed, or partially removed and are not supported anymore:

  • Legacy UserCalendarItemsService removed. A new version of the Blackboard building block is available that uses the MyTimetable API instead of the legacy SOAP service. Custom integrations should also switch to the MyTimetable API, contact us for help with this.
  • No labels