Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
10/29/13 19:15:11 (10 years ago)
- Author:
-
jamoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
- Property Cc rleigh bpindelski sbesson added
-
Property
Component
changed from
to
Deployment
-
Property
Summary
changed from
Build improvements
to
Build revamp
-
Property
Priority
changed from
to
critical
-
Property
Milestone
changed from
Unscheduled
to
5.0.0
-
initial
|
v1
|
|
| 1 | After years of layering one requirement one build requirement on top of another (if not one build system on top of another), there's a substantial amount of cruft. Areas which particularly need reworking include: |
| 2 | |
| 3 | * C++ build (scons, cmake, ...) |
| 4 | * Maven/ant build and separation |
| 5 | * Integration with git (src releases) |
| 6 | * Automatic download of artifacts (ivy) |
| 7 | * Size of repositories |
| 8 | * Support for plugins/extensions (e.g. [https://github.com/joshmoore/ome-cmd-example omero-cmd-example]) |
| 9 | |
| 10 | Some of these may be achievable independently of one another, several others may need to go together. Regardless, we will need to pin down the requirements which originally led to all the many different combinations, whether or not those requirements still hold, and then start to rework or rewrite the build. |
| 11 | |
| 12 | A very incomplete list of design goals would include: |
| 13 | * no hard-coding of platform-specific hacks |
| 14 | * removal of all binaries from source code |
| 15 | * reduction of rebuilds (i.e. increase re-use of built components) |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.28447 sec.)