Skip to main content
Jump to: navigation, search

Difference between revisions of "Scout/Release/Oxygen"

< Scout‎ | Release
(IP Log)
(Features)
 
(31 intermediate revisions by 2 users not shown)
Line 20: Line 20:
 
=== Review Bug ===
 
=== Review Bug ===
  
This release review is tracked in TODO: update link for Scout 7.0 (link for Scout 6.0: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=493939 bugzilla]).
+
This release review is tracked in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=517715 Bugzilla].
  
 
=== Review Dates ===
 
=== Review Dates ===
Line 46: Line 46:
 
* Completely based on Java, Scout Applications are easy to integrate in most IT environments.
 
* Completely based on Java, Scout Applications are easy to integrate in most IT environments.
  
== Features ==
+
== Features and Roadmap ==
  
TODO
+
=== Features ===
  
=== Roadmap for 2017/18 ===
+
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 [https://eclipsescout.github.io/6.1/release-notes.html 6.1] and [https://eclipsescout.github.io/7.0/release-notes.html 7.0] releases.
 +
Some notable new features are listed below
  
TODO
+
* Several refactorings in the Scout HTML layer to better separate the Scout JavaScript parts from the rest of the Scout framework (working title "Scout JS")
 +
* 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+ ===
 +
 
 +
'''Scout JS'''
 +
 
 +
During the Oxygen release some initial steps under the name “Scout JS” were implemented to decouple the new Scout HTML5 widgets from the rest of the framework. The goal of these efforts is to provide a Scout JS widget library that can be used by classical Scout applications as well as other pure JavaScript consumers. The current State of Scout JS is focused on the requirements of individual customer projects and not intended for productive use outside of the scope of these specific projects.
 +
 
 +
In the context of the Photon release we expect to complete this refactoring to a point where Scout JS provides a production ready widget library for a more general class of JavaScript applications / web UIs.
 +
 
 +
'''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.
  
 
== Milestone Installations ==
 
== Milestone Installations ==
Line 58: Line 83:
 
Please follow the steps below.
 
Please follow the steps below.
  
# Prior to the Eclipse Neon Release download the Scout EPP from the [https://www.eclipse.org/downloads/index-developer.php Developer Builds]
+
# Prior to the official Eclipse Release download the Scout EPP from the [https://www.eclipse.org/downloads/index-developer.php Developer Builds]
# [https://eclipsescout.github.io/6.0/latest/article_install/scout_install/scout_install.html Download and Install the Scout SDK]
+
# [https://eclipsescout.github.io/7.0/latest/article_install/scout_install/scout_install.html Download and Install the Scout SDK]
# [https://eclipsescout.github.io/6.0/latest/article_helloworld/scout_helloworld/scout_helloworld.html The Scout "Hello World!"]
+
# [https://eclipsescout.github.io/7.0/latest/article_helloworld/scout_helloworld/scout_helloworld.html The Scout "Hello World!"]
  
 
== Non-Code Aspects ==
 
== Non-Code Aspects ==
  
 
Scout Documentation/Tutorials etc. is written with Asciidoctor and hosted on [https://github.com/BSI-Business-Systems-Integration-AG/org.eclipse.scout.docs Github].
 
Scout Documentation/Tutorials etc. is written with Asciidoctor and hosted on [https://github.com/BSI-Business-Systems-Integration-AG/org.eclipse.scout.docs Github].
The progress of the Scout book may be monitored in the following [https://eclipsescout.github.io/6.0/ output directory]
+
 
 +
The progress of the Scout book may be monitored in the following [https://eclipsescout.github.io/7.0/ output directory]
  
 
Status per communication channel
 
Status per communication channel
Line 79: Line 105:
 
== Compatibility with Previous Releases ==
 
== Compatibility with Previous Releases ==
  
'''Scout RT 7.0''' will NOT be compatible with Scout 7.0.  
+
Scout 7.0 ist not compatible with Scout 6.0.  
  
'''Scout SDK 7.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 [[Scout/Contribution_Guidelines|contribution guidelines]] in more detail.
  
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.
+
Migrating from Scout 6.0 to 7.0 Migration corresponds to a two-step approach. see the following Eclipse Scout Migration Guides
 
+
* Scout 6.1: [http://eclipsescout.github.io/6.1/migration-guide.html Migration Guide (6.0 to 6.1)]
API Compatibility rules are described in the [[Scout/Contribution_Guidelines|contribution guidelines]] in more detail.
+
* Scout 7.0: [http://eclipsescout.github.io/7.0/migration-guide.html Migration Guide (6.1 to 7.0)]
 
+
For changes from Scout 6.0 to 7.0 Migration see the Eclipse Scout Migration Guide
+
* Scout 6.1: [http://eclipsescout.github.io/6.1/migration-guide.html Migration Guide (6.1)]
+
* Scout 7.0: [http://eclipsescout.github.io/7.0/migration-guide.html Migration Guide (7.0 estimat April 2017)]
+
  
 
== End-of-Life ==
 
== End-of-Life ==
Line 100: Line 122:
 
== Bugzilla Tickets ==
 
== Bugzilla Tickets ==
  
Bug reports relevant to the Scout 6.0 release
+
For bug reports relevant to the Scout 7.0 release see [https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Scout&query_format=advanced&target_milestone=6.0.100%20RC1&target_milestone=6.0.100%20RC2&target_milestone=6.0.100%20RC3&target_milestone=6.0.100%20RC4&target_milestone=6.0.200%20RC1&target_milestone=7.0.0%20M1&target_milestone=7.0.0%20M2&target_milestone=7.0.0%20M3&target_milestone=7.0.0%20M4&target_milestone=7.0.0%20M5 Bugzilla]
 
+
* Change Requests and Bugfixes, see [https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&columnlist=component%2Cbug_id%2Cbug_severity%2Ctarget_milestone%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Cassigned_to%2Cstatus_whiteboard%2Cop_sys&component=Scout&component=Scout%20Docs&component=Scout%20SDK&list_id=15859563&product=Scout&query_format=advanced&target_milestone=7.0.0%20M1&target_milestone=7.0.0%20M2&target_milestone=7.0.0%20M3&target_milestone=7.0.0%20M4&target_milestone=7.0.0%20M5 Bugzilla tickets]
+
* Overview for severity / status, see [https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_status&y_axis_field=bug_severity&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Scout&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&target_milestone=7.0.0+M1&target_milestone=7.0.0+M2&target_milestone=7.0.0+M3&target_milestone=7.0.0+M4&target_milestone=7.0.0+M5&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap Bugzilla report]
+
  
 
== Target Environment  ==
 
== Target Environment  ==
Line 126: Line 145:
  
 
=== Eclipse Platform  ===
 
=== Eclipse Platform  ===
For Scout 6.0 we recommend developing Scout with Eclipse Neon (4.6).  
+
For Scout 7.0 we recommend developing Scout with Eclipse Oxygen (4.7).  
  
 
The following Eclipse platforms are supported:  
 
The following Eclipse platforms are supported:  
Line 136: Line 155:
 
  ! scope="col" style="background:#efefef;" | Scout SDK
 
  ! scope="col" style="background:#efefef;" | Scout SDK
 
  |-
 
  |-
  |Luna (4.4)
+
  |Mars (4.5)
 
  | -
 
  | -
 
  | supported
 
  | supported
 
  |-
 
  |-
  |Mars (4.5)
+
  |Neon (4.6)
 
  | -
 
  | -
 
  | supported
 
  | supported
 
  |-
 
  |-
  |Neon (4.6)
+
  |Oxygen (4.7)
 
  | -
 
  | -
 
  |recommended
 
  |recommended
Line 154: Line 173:
 
The HTML5 UI for Scout only supports the following browsers and versions:
 
The HTML5 UI for Scout only supports the following browsers and versions:
  
TO BE VERIFIED
+
* Microsoft Internet Explorer >= version 9 (10 or higher recommended)
 
+
* Microsoft Edge (desktop pc, surface tablet) >= 12
* Microsoft Internet Explorer >= version 9
+
 
* Google Chrome >= version 36
 
* Google Chrome >= version 36
 
* Firefox >= version 36
 
* Firefox >= version 36
* Safari >= TBD
+
* Safari >= 7
* iOS >= TBD
+
 
* Android >= TBD
+
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
  
 
=== Tested Platforms  ===
 
=== Tested Platforms  ===
Line 217: Line 239:
  
 
== Current Project Metrics ==
 
== Current Project Metrics ==
project metrics for Eclipse Scout provided on [[https://www.openhub.net/p/eclipsescout openHub]]
+
 
 +
According to the [https://eclipse.biterg.io/app/kibana#/dashboard/Overview Eclipse project dashboard] Scout belongs to the most active repositories hosted at Eclipse.
 +
 
 +
Latest project metrics for Eclipse Scout are provided on [https://www.openhub.net/p/eclipsescout openHub].
  
 
== Community and Support ==
 
== Community and Support ==
Line 231: Line 256:
 
=== Activities 2017 ===
 
=== Activities 2017 ===
  
* Javaland (planned)
+
* Javaland  
* Democamp Munich (planned)
+
* Eclipse Democamp Zurich
* Democamp Zurich (planned)
+
* Eclipse Democamp Munich (planned)
 
* Java Forum Stuttgart (planned)
 
* Java Forum Stuttgart (planned)
  
Line 243: Line 268:
 
* All committers are currently employees from BSI
 
* All committers are currently employees from BSI
  
== IP Issues ==
+
== IP Status ==
 +
 
 +
=== New Components ===
  
=== MOM ===
+
* jackson-core 2.8.7 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13363 CQ13363]
 +
* jackson-databind 2.8.7 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13364 CQ13364]
 +
* jackson-annotations 2.8.7 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13365 CQ13365]
 +
* Apache HttpClient 4.5.3 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13610 CQ13610]
 +
* google-http-client Version 1.22.0 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13611 CQ13611]
  
Runtime Components
+
=== Dependency Upgrades ===
* [https://github.com/FasterXML/jackson-jr Jackson] ([http://www.apache.org/licenses/ Apache 2.0 Licence]), (Latest 2.8.1): <span style="background:orange">-> NEW </span>
+
* Logback classic 1.2.2 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13513 CQ 13513]
 +
* Logback core 1.2.2 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13514 CQ 13514]
 +
* javax.mail 1.5.6 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13523 CQ 13523]
 +
* commons-fileupload 1.3.2 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13113 CQ13113]
 +
* commons-logging 1.1.1 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13114 CQ 13114]
 +
* JAXB-API 2.2.12 Final [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13115 CQ 13115]
 +
* Saaj-api 1.3.8 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13521 CQ13521]
 +
* org.quartz 2.2.3 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13116 CQ13116]
 +
* jul-to-slf4j 1.7.25 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13367 CQ13367]
 +
* slf4j-api 1.7.25 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13368 CQ13368]
 +
* slf4j-jdk14 1.7.25 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13369 CQ13369]
 +
* slf4j-log4j12 1.7.25 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13370 CQ13370]
 +
* xerces 2.11.0 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13117 CQ13117]
  
Components needed for scout tests
+
* yuicompressor 2.4.9-BSI-1 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13322 CQ 13322]
* [http://activemq.apache.org/ ActiveMQ Broker] (https://github.com/apache/activemq/tree/master/activemq-broker Githup) ([http://www.apache.org/licenses/ Apache 2.0 Licence]), (Latest 5.14.0): <span style="background:orange">-> NEW </span>
+
* jQuery 3.2.1 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13531 CQ13531]
 +
* jQuery Mobile 1.4.5 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13452 CQ 13452]
 +
* jasmine 2.5.2 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13532 CQ13532]
  
 
=== IP Log ===
 
=== IP Log ===
The state of the IP log is tracked with [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11427 this bug].
+
The state of the IP log is tracked with [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13647 this bug].
 
Scout's IP Log for Scout has been generated according to the [https://wiki.eclipse.org/Development_Resources/Automatic_IP_Log#Using_the_Automated_IP_Log Wiki description].
 
Scout's IP Log for Scout has been generated according to the [https://wiki.eclipse.org/Development_Resources/Automatic_IP_Log#Using_the_Automated_IP_Log Wiki description].
  
Line 262: Line 307:
  
 
* ant-*
 
* ant-*
 +
* derby*
 +
* junit.jar
 +
* servletbridge.jar
  
 
   
 
   
The Scout IP Log has been approved on May ?. The component leadership verifies that:
+
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.
 
* The about files and use licenses are in place as per the Guidelines to Legal Documentation.

Latest revision as of 09:57, 6 June 2017


Scout
Wiki Home
Website
DownloadGit
Community
ForumsBlogTwitterG+
Bugzilla
Bugzilla


Eclipse Scout DocuWare (Oxygen Release)

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

Additional Links

Overview

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

Features

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

  • Several refactorings in the Scout HTML layer to better separate the Scout JavaScript parts from the rest of the Scout framework (working title "Scout JS")
  • 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+

Scout JS

During the Oxygen release some initial steps under the name “Scout JS” were implemented to decouple the new Scout HTML5 widgets from the rest of the framework. The goal of these efforts is to provide a Scout JS widget library that can be used by classical Scout applications as well as other pure JavaScript consumers. The current State of Scout JS is focused on the requirements of individual customer projects and not intended for productive use outside of the scope of these specific projects.

In the context of the Photon release we expect to complete this refactoring to a point where Scout JS provides a production ready widget library for a more general class of JavaScript applications / web UIs.

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.

Milestone Installations

Please follow the steps below.

  1. Prior to the official Eclipse 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: OK
  • Mailing list: OK for important info to all committers

APIs

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

End-of-Life

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.

Bugzilla Tickets

For bug reports relevant to the Scout 7.0 release see Bugzilla

Target Environment

JRE

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 7.0 we recommend developing Scout with Eclipse Oxygen (4.7).

The following Eclipse platforms are supported:

Eclipse Version Scout Runtime Scout SDK
Mars (4.5) - supported
Neon (4.6) - supported
Oxygen (4.7) - recommended

Browser Versions

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

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 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

Activities 2016

  • 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)

Activities 2017

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

Current Status

  • 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

IP Status

New Components

Dependency Upgrades

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. 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:

  • ant-*
  • derby*
  • junit.jar
  • servletbridge.jar


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.

Previous Release Documentation

Back to the top