Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search


The Scout documentation has been moved to

Eclipse Scout DocuWare (Neon Release)

This page provides the required docuware for the Scout 6.0 Release Review as part of the upcoming Neon 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

This release review is tracked in bugzilla.

Review Dates

  • May 26/2016 - IP Log submission deadline
  • June 2/2016 - Review materials due
  • June ??/2016 - Release Review

Original source is here

Additional Links


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

  • Scout HTML5 client applications may run on the desktop, on tablets and on mobile phones 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, Scout Applications are easy to integrate in most IT environments.


Below, the central new features for Scout 6.0.0 are listed. For a more complete overview, see the The Scout documentation has been moved to

Roadmap for 2016

With Neon, Scout comes with two big changes.

Milestone Installations

Please follow the steps below.

  1. Prior to the Eclipse Neon Release download the Scout EPP from the Developer Builds
  2. Download and Install the Scout SDK
  3. The Scout "Hello World!"

Non-Code Aspects

Scout Documentation/Tutorials etc. is written with Asciidoctor and hosted on Github. The progress of the Scout book may be monitored in the following output directory

Status per communication channel

  • Forum: OK
  • Wiki: OK
  • Webpage: In need of an update
  • 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 6.0 will NOT be compatible with Scout 5.0.

Scout SDK 6.0 will NOT be compatible with Scout SDK 5.0.

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.

Placeholder: Migration Guidelines for how to migrate from 5.0 to 6.0.


With release 6.0 significant changes are shipped that are affecting all Scout applications that want to migrate to the latest release. This is why we started to announce the changes related to removing the dependency to the Eclipse platform and the switch to a new HTML5 renderer in early 2015.

Scout Client

  • Eclipse SWT renderer is no longer supported
  • Eclipse RAP renderer is no longer supported
  • Java Swing renderer is no longer supported
  • OSGi/Eclipse runtime platform is no longer supported

Scout Server

  • OSGi/Eclipse runtime platform is no longer supported

Experience with Migration to Neon Release

  • Relatively modest efforts are required to migrate old Scout applications that are based on the old Scout Eclipse/OSGi platform to new Java/HTML5 platform.
  • This holds true for the migration of several productive Scout applications by BSI and other organisations.

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

Bug reports relevant to the Scout 6.0 release

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 6.0 runtime is still compatible with Java SE 7. As the announced end of public updates 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 >=8.

Java Version Support for Scout Runtime/SDK
8 recommended
9 experimental

Eclipse Platform

For Scout 6.0 we recommend developing Scout with Eclipse Neon (4.6).

The following Eclipse platforms are supported:

Eclipse Version Scout Runtime Scout SDK
Luna (4.4) - supported
Mars (4.5) - supported
Neon (4.6) - recommended

Browser Versions

The HTML5 UI for Scout only supports the following browsers and versions:


  • Microsoft Internet Explorer >= version 9
  • Google Chrome >= version 36
  • Firefox >= version 36
  • Safari >= TBD
  • iOS >= TBD
  • Android >= TBD

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 6.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 64-bit
Oracle JDK 7, 64-bit 4.6, 64-bit, EPP
Oracle JDK 8, 64-bit 4.6, 64-bit, EPP
10 Oracle JDK 8, 64-bit 4.6, 64-bit, EPP
Ubuntu Linux 15.10 OpenJDK 7, 64-bit 4.6, 64-bit, EPP
Apple Mac OS 10.8 Oracle JDK 7, 64-bit 4.6, 64-bit, EPP

With Scout 6.0 we no longer explicitly test our bits on 32bit architectures.

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

Current Project Metrics

project metrics for Eclipse Scout provided on [openHub]

Community and Support

Activities 2015

  • 2nd Eclipse Scout User Group Meeting
  • EclipseCon Europe
  • Democamp November Frankfurt
  • Democamp December Munich

Activities 2016

  • OOP Munich
  • Javaland
  • Democamp Munich (planned)
  • Democamp Zurich (planned)
  • Java Forum Stuttgart (planned)

Current Status

  • Increasing activites on the Scout forum.
  • Starting to get questions on Stackoverflow.
  • Large scale business applications built and in productive use.
  • All committers are currently employees from BSI.

IP Issues

Scout CQs for new HTML5 Renderer

Runtime Components

Components needed for development

New Scout RT CQs

  • javax.mail, Release 1.5.5 CQ11275 Next Step: OK -> checkin
  • [Jcodemodel], Release 1.0.3 CQ11297 Next Step: OK -> checkin
  • [Apache Commons-io], Release 2.2 CQ11276 (PB9476) Next Step: OK -> checkin
  • [javax.annotation-api], Release 1.2 CQ11292 (PB7386) Next Step: OK -> checkin
  • [Jsr181-api], Release 1.0-MR1 CQ11296 Next Step: OK -> checkin
  • [Jaxb-api], Release 2.2.9 CQ11294 Next Step: OK -> checkin
  • [javax.xml.soap-api], Release 1.3.5 CQ11295 Next Step: OK -> checkin
  • [jaxws-api], Release 2.2.10 CQ11293 Next Step: OK -> checkin
  • [Junit], Release 4.12 CQ11286 (PB9232) Next Step: OK -> checkin
  • [Log4j], Release 1.2.17 CQ11285 (PB7837) Next Step: OK -> checkin
  • [Apache commons-math], Release 3.5 CQ11288 (PB9724) Next Step: OK -> checkin
  • [Mockito-core], Release 1.10.19 CQ11290 Next Step: OK -> checkin
  • [Objenesis], Release 2.2 CQ11298 Next Step: OK -> checkin
  • [Asm/asm-commons/asm-tree], Release 5.0.1 CQ11277 (PB8128) Next Step: OK -> checkin
  • [Slf4j-api], Release 1.7.12 CQ11278 (PB10122) Next Step: OK -> checkin
  • [Xalan], Release 2.7.0 CQ11279 (PB1761) Next Step: OK -> checkin

New Scout SDK CQs

  • [Guava], Release 15.0 CQ11280 (PB7768) Next Step: OK -> checkin
  • [Wagon-http], Release 2.10 CQ11283 Next Step: OK -> checkin
  • [Wagon-http-shared], Release 2.10 CQ11284 Next Step: OK -> checkin
  • [Wagon-provider-api], Release 2.10 CQ11282 Next Step: OK -> checkin
  • [Maven-model], Release 3.3.3 CQ11281 (PB9261) Next Step: OK -> checkin
  • [Plexus-utils], Release 3.0.20 CQ11289 (PB9283) Next Step: OK -> checkin

Other Scout CQs for this Release

IP Log

The state of the IP log is tracked with this bug. 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 May ?. 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

Back to the top