Project

General

Profile

Support #7216

project build improvements to allow standard creation, archive, recreation steps

Added by Greg Shah about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

History

#1 Updated by Greg Shah about 1 year ago

We should have a standardized approach to creating a new project directory:

  • For a fresh conversion from source; OR
  • For installing a pre-converted binary (and optionally the conversion artifacts that would allow incremental conversion).

Our standard project build scripting (ant based build.xml) should have targets that do the following:

  • Create a distribution of the minimum binary runtime code.
  • Archive enough of the conversion artifacts (intermediate and final) to allow an overlay on top of a fresh project install (see above) that the project can be used for incremental conversion.

Anything that can come from the original bzr project, one of the original source code/schema archives, skeletons etc... should NOT be in the binary distribution of the archived results. But that will require us to have a standard for how we name, store and recreate the build's results. I think this means we need a standard properties file that lists these inputs so that our tooling can reuse them when needed.

To be clear: we should not have to overwrite existing files in order to build a artifact-based install. We really should implement #5586 first.

Also available in: Atom PDF