Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
|Download • Git|
|Forums • Blog • Twitter • G+|
- 1 Eclipse Scout DocuWare (Oxygen Release)
- 1.1 Release Review Dates and Links
- 1.2 Overview
- 1.3 Features and Roadmap
- 1.4 Milestone Installations
- 1.5 Non-Code Aspects
- 1.6 APIs
- 1.7 Compatibility with Previous Releases
- 1.8 End-of-Life
- 1.9 Ramp down Policy
- 1.10 Bugzilla Tickets
- 1.11 Target Environment
- 1.12 Build Process
- 1.13 Current Project Metrics
- 1.14 Community and Support
- 1.15 IP Status
- 1.16 Previous Release Documentation
Eclipse Scout DocuWare (Oxygen Release)
Release Review Dates and Links
This release review is tracked in Bugzilla.
- May 24/2017 - IP Log submission deadline
- May 31/2017 - Review materials due
- June 7/2017 - First round of release reviews (aim for this date if you can)
- June 21/2017 - Second (final?) round of release reviews
- June 28/2017 - Eclipse Oxygen GA
Original source is here
- Schedule: Schedule
- Overview: Release overview
- Platform Plan: Placeholder
- Reports: Reports
- List: Participating Projects
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.
Features and Roadmap
The main focus of the Scout 7.0 release was on stability and completeness. The detailed feature list for Eclipse Scout Oxygen is available in the release notes for the 6.1 and 7.0 releases. Some notable new features are listed below
- Scout HTML fields and bean fields as well as Scout HTML enabled string columns and bean columns now support binary resources such as videos and images
- For simpler migrations of existing SWT based Scout applications to the HTML5 based UI of the new Scout releases a configurable bench layout is introduced for the Scout desktop component
- Tree icons have been re-introduced
Roadmap Scout Version 8.0+
Move to new service API
A PoC is planned to investigate a move from today’s service calls using Scout FormData/PageData objects to a new service API. The goal of the replacement is a more generic/powerful mechanism to deal with additional UI technologies/3rd party consumer in addition to the current Java client UI. Such a move requires careful analysis and discussions with the current user base. As of today, it is not yet clear if this initiative can be implemented in the context of the Photon release.
Alternatives to nested Java Classes for Scout UI Model?
Today, the Scout UI model for forms and pages is based on nested inner classes. While nested Java classes offer a very clear structuring of the Scout model code this mechanism is quite rigid regarding dynamically building UIs, for cases where the user needs to subclass a subset of components and in cases that would require multiple inheritance. For the Photon release we plan to investigate possible alternatives to this concept. As in the case of the new service API careful analysis will be required and it is not yet clear that any changes/new features will actually be implemented within the Photon release.
Improve Application Startup Performance
During development Scout applications need to be restarted frequently which is very time consuming. With the Scout Photon release restart times should be reduced significantly.
Please follow the steps below.
- Prior to the official Eclipse Release download the Scout EPP from the Developer Builds
- Download and Install the Scout SDK
- The Scout "Hello World!"
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: 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 7.0 ist not compatible with Scout 6.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.
Migrating from Scout 6.0 to 7.0 Migration corresponds to a two-step approach. see the following Eclipse Scout Migration Guides
With Scout release 7.0 no significant components reach their end-of-life. Therefore, no substantial migration efforts are anticipated for migrating a Scout application from release 6.0 to release 7.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.
For bug reports relevant to the Scout 7.0 release see Bugzilla
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|
For Scout 7.0 we recommend developing Scout with Eclipse Oxygen (4.7).
The following Eclipse platforms are supported:
|Eclipse Version||Scout Runtime||Scout SDK|
The HTML5 UI for Scout only supports the following browsers and versions:
- Microsoft Internet Explorer >= version 9 (10 or higher recommended)
- Microsoft Edge (desktop pc, surface tablet) >= 12
- Google Chrome >= version 36
- Firefox >= version 36
- Safari >= 7
Browser on mobile devices. Browsers are typically included in device OS. Therefore, our recommendations are linked to device OS versions as well:
- iOS >= 8
- Android >= 5
- Windows Mobile >= 10
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)|
|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.
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
According to the Eclipse project dashboard Scout belongs to the most active repositories hosted at Eclipse.
Latest project metrics for Eclipse Scout are provided on openHub.
Community and Support
- 3rd Eclipse Scout User Group Meeting (Eclipsecon Europe Unconference)
- EclipseCon Europe
- Devoxx Antwerpen
- Democamp December Munich December
- Gemeinsam BSI (Conference organized by BSI for its customers)
- Eclipse Democamp Zurich
- Eclipse Democamp Munich (planned)
- Java Forum Stuttgart (planned)
- Successful transition of many projects on new Java/HTML5 stack
- Increasing activites on the Scout forum and on Stackoverflow
- Large scale Eclipse Scout business applications built and in productive use
- All committers are currently employees from BSI
- jackson-core 2.8.7 CQ13363
- jackson-databind 2.8.7 CQ13364
- jackson-annotations 2.8.7 CQ13365
- Apache HttpClient 4.5.3 CQ13610
- google-http-client Version 1.22.0 CQ13611
- Logback classic 1.2.2 CQ 13513
- Logback core 1.2.2 CQ 13514
- javax.mail 1.5.6 CQ 13523
- commons-fileupload 1.3.2 CQ13113
- commons-logging 1.1.1 CQ 13114
- JAXB-API 2.2.12 Final CQ 13115
- Saaj-api 1.3.8 CQ13521
- org.quartz 2.2.3 CQ13116
- jul-to-slf4j 1.7.25 CQ13367
- slf4j-api 1.7.25 CQ13368
- slf4j-jdk14 1.7.25 CQ13369
- slf4j-log4j12 1.7.25 CQ13370
- xerces 2.11.0 CQ13117
- yuicompressor 2.4.9-BSI-1 CQ 13322
- jQuery 3.2.1 CQ13531
- jQuery Mobile 1.4.5 CQ 13452
- jasmine 2.5.2 CQ13532
To check the current state at any time, use the following link. To compare against potential issues use this IP Issues List. Caution: The link reporting potential issues contains many bogus links. See below for a partial list
Known bogus issues in IP issues list:
TODO: The Scout IP Log has been approved on [pending]. 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.