forked from ohinckel/build-core
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTODO
executable file
·56 lines (40 loc) · 1.39 KB
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
$Id$
This file collects things that still need to be implemented / decided / ...
Implementation
===============
* Introduce new artifact type "bootstrap" and replace "zip" with it
. all "bootstrap" types should indicate they're needed before any XP
execution takes places
. extension should remain "zip", though
Status: DONE
* Improve "install.xml" build file
. could this use ivy already to fetch dependencies?
Status: TODO
* Implement build "complete" web application zip:
. add all required files & dependencies
Status: DONE
. create Web container configuration (eg. apache vhost config)
. define set of replaceable tokens, if any
Status: TODO
* Implement build command line application zip:
. add all required files & dependencies
Status: DONE
* Add support for code generation
. simple frontend for `cgen`
. added to "generate-sources" target
* Implement syntax checks
. `php -l` for .php in "validate" phase
. xmllint for .xml, .xsl
Documentation
==============
* "public" variables
. which ant settings may a user change
* Targets / phases and their idea
. may one add new targets? phases?
. overrideing allowed?
Open decisions
===============
* Custom targets
. should these be allowed? Eg. this could be a proprietary deployment
mechanism, or some proprietary custom tasks
("make install")