Jump to: navigation, search


Wiki Home

Eclipse Scout DocuWare (Mars Release)

This page provides the required docuware for the Scout 5.0 Release Review as part of the upcoming Mars Simultaneous Release according to the Eclipse process documentation.

Contact: matthias(dot)zimmermann(at)bsi-software(dot)com

Communication Channels:

Release Review Dates and Links

Review Bug

To track this Scout release Bug 467053 is used.

Review Dates

  • May 22/2015 - IP Log submission deadline
  • May 29/2015 - Review materials due
  • June 12/2015 - Release Review

Original source is here

Additional Links


Eclipse Scout is a mature and open framework for modern, service oriented business applications.

  • Scout applications may run on different frontend technologies desktop (Swing, SWT), web and mobile (RAP) without any changes in the source code
  • Scout substantially boosts developer productivity and is simple to learn.
  • User friendly applications are straight forward to implement with Scout’s comprehensive set of user interface components.
  • Completely based on Java/Eclipse, Scout Applications are easy to integrate in most IT environments.


Below, the central new features for Scout 5.0.0 are listed. For a more complete overview, see the New and Noteworthy.

Support for modular Scout Applications

With Mars, Scout amends the support to build highly modular and extensible business applications.

Scout Runtime and SDK

Added support for updates on required software for Scout (eg. RAP 3.0) New and Noteworthy

Scout Documentation

Implemented common documentation platform for various output formats documents. bug 465960

Non-Code Aspects

Scout Documentation/Tutorials etc. are mainly provided via the Scout Wiki

The Scout team has updated the Scout Book book and added material regarding the use of UI widgets.

  • The progress of the Scout book may be monitored in the following output directory
  • Setup and process description on the Scout wiki

Status per communication channel

  • Forum: OK
  • Wiki: OK
  • Webpage: OK
  • Mailing list: OK for important info to all committers


We certify that the public Scout APIs in this release are production quality. As a significant amount of commercial customer applications are based on these APIs we evaluate/communicate changes accordingly.

Compatibility with Previous Releases

Scout RT 5.0 will NOT be compatible with Scout 4.0.

Scout SDK 5.0 will NOT be compatible with Scout SDK 4.0. However, the Scout SDK API is not yet used frequently.

We try to make migration to new releases as easy as possible, however to keep our code clean and simple we need to change the API in new releases. There are no more API changes after milestone M6. API Compatibility rules are described in the contribution guidelines in more detail. How to migrate from 4.0 to 5.0 is described in these individual bugs.


Some functionality will be dropped completely with Scout 5.0. We suppose this won't be an issue for most Scout projects.

  • Java Versions Java 6 is not supported anymore
  • Eclipse Versions: The following eclipse versions that where previously supported or partially supported, are not supported anymore
    • Scout RT: 4.4
    • Scout SDK: 3.7
  • Rap Versions: RAP 2.3 is not supported anymore, the current RAP version is 3.0

Ramp down Policy

We use daily builds. No API changes after M6, no new features after M7. In the RC phase only bugs marked P2 or higher or severity major or higher will be fixed.

Bugzilla Tickets

Target Environment


All of Eclipse Scout is "pure" Java code and has no direct dependence on the underlying operating system. The chief dependence is therefore on the Java Runtime (JRE) itself. The Scout 5.0 release of is still compatible with Java SE 7.

As the announced end of public upates for Java 7 is scheduled for April 2015, Scout projects working with Oracle products might want to consider moving to Java 8 as soon as possible. The eclipse scout package only runs with Java >=1.7.

Java Version Support for Scout Runtime/SDK
7 supported
8 recommended

Eclipse Platform

For the Mars release of Scout we recommend developing Scout with Eclipse Mars (4.5) and using Eclipse 3.8 as a target platform. Scout is still using the compatibility layer for the eclipse 3.x stream. (See Scout/Targets for more detail).

The following Eclipse platforms are supported:

Eclipse Version Scout Runtime Scout SDK
Indigo (3.7.2) supported -
Juno (3.8.2) recommended supported
Juno (4.2.2) - supported
Kepler (4.3.2) - supported
Luna (4.4) - supported
Mars (4.5) supported recommended

RAP Version

Eclipse Scout and RAP are participating in the Simultaneous Release and therefore needs to support RAP 3.0.

RAP Version Scout Runtime
3.0 supported

Browser Versions

The web UI for Scout is based on RAP and therefore only supports the browser version supported by RAP:

  • Microsoft Internet Explorer 9+
  • Google Chrome 7+
  • Firefox 9+
  • Safari 5+
  • Android 3 (Limited)

Tested Platforms

We focus our testing on a handful of popular combinations (OS, HW Arch, Java VM, Eclipse platform); these are our reference platforms. Scout undoubtedly runs fine in many operating environments beyond the reference platforms we test. However, since we do not systematically test them we cannot vouch for them. Problems encountered when running Scout on a non-reference platform that cannot be recreated on any reference platform will be given lower priority than problems with running Scout on a reference platform.

Scout 5.0 will be tested and validated on the following reference platforms:

Operating System OS Version Hardware Java VM (vendor, version, arch) Eclipse Platform (version, arch)
Windows 7 x86 32-bit Oracle JDK 7, 32-bit 3.7.2, 32-bit
x86 64-bit 3.8.2, 32-bit
Oracle JDK 7, 32-bit 4.5, 32-bit, EPP
Oracle JDK 7, 64-bit 4.5, 64-bit, EPP
Oracle JDK 8, 64-bit 4.5, 64-bit, EPP
8 x86 64-bit Oracle JDK 7, 64-bit 4.5, 64-bit, EPP
Oracle JDK 8, 32-bit 4.5, 32-bit, EPP
Ubuntu Linux 13.10 x86 64-bit OpenJDK 7, 64-bit 4.5, 64-bit, EPP
x86 32-bit OpenJDK 7, 32-bit 4.5, 32-bit, EPP
Apple Mac OS 10.8 x86 64-bit Oracle JDK 7, 64-bit 4.5, 64-bit, EPP

Build Process

Scout is built on Hudson @ Eclipse.

Scout is using maven and tycho for building.

  • Gerrit Jobs run build against lowest target platform with runtime unit tests
  • Nightly Jobs run against all platforms with all unit tests
  • Release Jobs can be parameterized for a specific tag and deploy to a specific updatesite
  • Some tests currently still run only at BSI's infrastructure: Scout GUI tests using java.awt.Robot, because they need a fully-fledged desktop environment.

Scout Maven Artifacts uploaded to repo.eclipse.org

Current Project Metrics

project metrics for Eclipse Scout provided on [openHub]

Community and Support

Activities 2014

  • EclipseCon Europe: Booth + Talk
  • First Eclipse Scout User Group Meeting
  • Eclipse Finance Day Zurich: Co-organisation by BSI
  • Eclipse X-Mas Democamp Munich: Talk
  • Customer presentations

Activities 2015

  • OOP München: Booth
  • EclipseCon San Francisco: Booth
  • Javaland: Booth, Talk (Scout and IoT)
  • Demo Camp Frankfurt: Talk
  • Demo Camp München: Co-organisation by BSI and Talk
  • Demo Camp Zurich: Co-organisation by BSI and Talk
  • Demo Camp Stuttgart: Talk
  • Customer presentations

Current Status

  • Increasing activites on the Scout forum from outside BSI.
  • First large scale business applications built outside BSI are live.
  • All committers are currently employees from BSI.

IP Issues

Scout's IP Log for Scout has been generated according to the Wiki description. To check the current state at any time, use the following link.

The Scout IP Log has been approved on June 8th. The component leadership verifies that:

  • The about files and use licenses are in place as per the Guidelines to Legal Documentation.
  • All contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
  • All significant contributions have been reviewed by the Foundation's legal staff.
  • All non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff.
  • All Contribution Questionnaires have been completed.

Previous Release Documentation