|Download • Git|
|Forums • Blog • Twitter • G+|
- 1 Eclipse Scout DocuWare (Neon Release)
- 1.1 Release Review Dates and Links
- 1.2 Overview
- 1.3 Features
- 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 Issues
- 1.16 Previous Release Documentation
Eclipse Scout DocuWare (Neon Release)
Release Review Dates and Links
This release review is tracked in bugzilla.
- May 26/2016 - IP Log submission deadline
- June 2/2016 - Review materials due
- June ??/2016 - Release Review
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.
Below, the central new features for Scout 6.0.0 are listed. For a more complete overview, see the New and Noteworthy.
Roadmap for 2016
With Neon, Scout comes with two big changes.
Please follow the steps below.
- Prior to the Eclipse Neon Release download the Scout EPP from the Developer Builds
- Download and Install the Scout SDK
- The Scout "Hello World!"
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.
- 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
- 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.
Bug reports relevant to the Scout 6.0 release
- Change Requests and Bugfixes, see Bugzilla tickets
- Overview for severity / status, see Bugzilla report
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 6.0 we recommend developing Scout with Eclipse Neon (4.6).
The following Eclipse platforms are supported:
|Eclipse Version||Scout Runtime||Scout SDK|
The HTML5 UI for Scout only supports the following browsers and versions:
TO BE VERIFIED
- Microsoft Internet Explorer >= version 9
- Google Chrome >= version 36
- Firefox >= version 36
- Safari >= TBD
- iOS >= TBD
- Android >= TBD
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
project metrics for Eclipse Scout provided on [openHub]
Community and Support
- 2nd Eclipse Scout User Group Meeting
- EclipseCon Europe
- Democamp November Frankfurt
- Democamp December Munich
- OOP Munich
- Democamp Munich (planned)
- Democamp Zurich (planned)
- Java Forum Stuttgart (planned)
- 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.
Scout CQs for new HTML5 Renderer
- FastClick (MIT Licence), Release 1.0.6 (Latest 1.0.6) Approved CQ9958 (1.0.1), New CQ11263 (1.0.6): -> OK -> checkin
- Font Awesome, Release 4.2.0 (Latest 4.3.0), Next Step: CQ9953 OK -> checkin
- jQuery (MIT Licence), Release 2.1.4 (Latest 2.2.3). CQ9954 (2.1.1), CQ11262 (2.1.4)OK -> checkin
- jQueryUI (MIT Licence), Release 1.11.2 (Latest 1.11.4). Next Step: CQ9960 OK -> checkin
- jQuery Mobile Version: (MIT Licence), Release 1.4.0, Latest 1.4.5 (PB on CQ8056), Next Step: CQ10281: OK -> checkin
- json.org (Apache Version 2 Licence), CQ9651 OK -> checkin
- Apache Commons FileUpload, Release 1.3.1, (PB CQ8219). CQ10065 OK -> checkin
- Apache Commons CLI, Release 1.2 (PB CQ4578). CQ10066 OK -> checkin
- Mozilla Rhino, Release 1.7R4 (PB CQ6737). CQ10067 OK -> checkin
- yuicompressor (BSD), Release 2.4.8, CQ10071 OK -> checkin
- LESS (Apache2 Licence), Release 1.7.4 (no PB on CQ6637 1.3.0 too old!). CQ10203 OK -> checkin
- lesscss-engine (Apache2 Licence), Release 1.5.1. CQ10076 OK -> checkin
- source-map.js (BSD Licence), Release 0.1.33 CQ10297 OK -> checkin
- Eclipse Scout HTML5 UI (EPL). CQ10064 OK -> checkin
Components needed for development
- phantomjs (BSD Licence), Release 1.9.2. CQ10077 -> withdrawn
- phantomjs-maven-plugin (MIT Licence), Release 0.2.1. CQ10078 -> EMO approved
- CoffeeScript (MIT License), Release 1.3.3. CQ10582 OK -> checkin
- jasmine (MIT Licence), Release 2.0.0 (latest 2.3.4). Next Step: CQ9955 OK -> checkin
- jasmine-maven-plugin (Apache2 Licence), Release 220.127.116.11. CQ10070. OK -> checkin
New Scout RT CQs
- Jandex (Apache Version 2 Licence), Release 1.2.2. Next Step: CQ9956 "required" prereq OK -> checkin
- Apache Commons Lang, Release 3.1.0, (PB on CQ6123) Next Step: CQ10282 OK -> checkin
- org.quartz, Release 2.2.2 Next Step: CQ10651 OK -> checkin
- 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
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.