Jazz Foundation 1.0 M2D1 Milestone

January 23, 2009 | Learn about the project

This is not the most recent version. We recommend Jazz Foundation 3.0 M8

This is a pre-release milestone build. We recommend that you install any pre-release build as an additional instance, in a separate directory, and that you do not "Update" your existing installation to the pre-release build using the IBM Installation Manager.

New & Noteworthy

All Downloads

Jazz Foundation 1.0 FM2D1 News

Jazz Foundation 1.0 Milestone FM2D1 - New and Noteworthy

Here are some of the more noteworthy things appearing in the Foundation 1.0 FM2D1 milestone build (Jan. 23, 2009) which is now available for download.


Simplified project organization	We are working toward enabling a simpler project organization, where team areas are optional. Several changes have been made to enable the simplification: Introduction of `ProcessArea` as a modeled item. Previously, components could only associate their items (e.g. Streams, Plans, etc.) at the team level, and execute their process-enabled operations with that team area context. Items can now be associated with project areas and executed with that project area context. It is recommended that an Item's reference to `TeamArea` be changed to `ProcessArea`, so that the item can be associated with either a project or team area. Team Artifacts navigator (TAN) related API. A TAN domain's content provider typically uses `ConnectedProjectAreaRegistry.getSelectedTeamAreas(...)` in order to respect the TAN filter settings. Now that items may be associated with a project area, a new API must be used. `ConnectedProjectAreaRegistry.getSelectedProcessAreas(...)` will return any selected team areas, in addition to the project area. In the future, the Process UI may add support for filtering the project area artifacts. It is recommended that components switch to this new API, which will automatically do the right thing when project filtering is available in the UI. UI for associating items. Previously, components have used `TeamAreaSelectionDialog` to allow the user to select a team area to be associated with their item. A new API `ProcessAreaSelectionDialog` is now available which allows the user to select a project area or team area.

Team areas without development lines	As part of our ongoing effort to allow simpler project structures, it is now possible to create team areas that don't belong to any development line. Such teams areas will function just as team areas do today with the exception that their process will not be customizable on a per-iteration basis. Components which call the methods `IProcessClientService#getDevelopmentLine(ITeamArea, ...)` or `IProcessServerService#getDevelopmentLine(ITeamArea)` must update their code to handle a possible `null` return value. We are allowing upstream components to get their adoptions in place before we update the team area creation UI, so the ability to create a team area with no development line will not be visible until next milestone.

"Create root team area" project operation eliminated	Creation of root team areas is now governed by the same "Save Team Area" operation as saving non-root areas. Previously, root team area creation was governed by the "Save Project Area" operation.

Jazz Foundation Services component	The code base for the Jazz REST Services (JRS) incubator is now included with Jazz Foundation builds (in a new component called Jazz Foundation Services). The various JRS services will seed the development of the Jazz Foundation Service REST APIs per the Jazz Integration Architecture.

Full text changes	The org.apache.lucene plug-in has moved to the Repository component. This is the first step in a process that will see all full text search facilities integrated at a lower level than they were previously.


User ID:
Password: