Jump to: navigation, search

Difference between revisions of "0.1.0.v20070610 Release Notes (Buckminster)"

(New page: {{Backlink|Buckminster Project}} =What has changed in this build?= <p>A while back, Buckminster switched the way it performed PDE builds from a direct approach using fine grained ant-tasks...)
 
(What has changed in this build?)
Line 1: Line 1:
 
{{Backlink|Buckminster Project}}
 
{{Backlink|Buckminster Project}}
 
=What has changed in this build?=
 
=What has changed in this build?=
<p>A while back, Buckminster switched the way it performed PDE builds from a direct approach using fine grained ant-tasks to using the PDE ant-script generators. The rationale was that the more that could be reused, the better. This approach turned out to be very difficult to maintain as more and more functionality was added. The scripts as such form a monolithic block of things that must be executed in one go for things like version suffix generation to work. Since it cannot be broken apart, it cannot be orchestrated.</p>
+
<p>A while back, Buckminster switched the way it performed PDE builds from a direct approach using fine grained ant-tasks to using the PDE ant-script generators. The rationale was that the more of the existing PDE build system that could be reused, the better. That approach turned out to be very difficult to maintain as more and more functionality was added. The scripts as such form a monolithic block of things that must be executed in one go for things like version-suffix generation to work. Since it cannot be broken apart, it cannot be orchestrated.</p>
<p>Rather then trying to work around the orchestration conflict using various tricks, Buckminster has now reverted to the old approach. The solution is much cleaner and a number of bugs was fixed instantly. Buckminster will still use the PDE logic but instead of first generating scripts and executing them, it will call on a set of well defined ant tasks that exposes the logic in a more fine grained fashion.</p>
+
<p>Rather then trying to work around the orchestration conflict using various tricks, Buckminster has now reverted to the old way of doing things. As a result, the solution is now much cleaner and a number of bugs were fixed instantly. Buckminster will still use the PDE logic but instead of first generating scripts and then executing them, it will call on a set of well defined ant tasks that exposes the logic in a more fine grained fashion.</p>
  
 
The new approach brings the following advantages:
 
The new approach brings the following advantages:

Revision as of 04:08, 11 June 2007

< To: Buckminster Project

What has changed in this build?

A while back, Buckminster switched the way it performed PDE builds from a direct approach using fine grained ant-tasks to using the PDE ant-script generators. The rationale was that the more of the existing PDE build system that could be reused, the better. That approach turned out to be very difficult to maintain as more and more functionality was added. The scripts as such form a monolithic block of things that must be executed in one go for things like version-suffix generation to work. Since it cannot be broken apart, it cannot be orchestrated.

Rather then trying to work around the orchestration conflict using various tricks, Buckminster has now reverted to the old way of doing things. As a result, the solution is now much cleaner and a number of bugs were fixed instantly. Buckminster will still use the PDE logic but instead of first generating scripts and then executing them, it will call on a set of well defined ant tasks that exposes the logic in a more fine grained fashion.

The new approach brings the following advantages:

  • Version suffix generation works as expected
  • Version replacement works on references to bundles that are not part of the current platform (but present in a delta-pack)
  • Actions terminate when errors are encountered
  • Up to date logic works (since new artifacts are created instead of patching existing ones)
  • Major speed up since already compiled artifacts are reused
  • No artifacts are generated in the source project

For more information, see bugs 175519, 175520, 175539, 191869, 191893, and 191894.