On 2006-12-06, at 13:08 EST, Jim Grandy wrote:
On Dec 6, 2006, at 9:48 AM, Max Carlson wrote:
P T Withington wrote:
On 2006-12-05, at 18:45 EST, Max Carlson wrote:
Approved, if you'll recompile the dev console with these changes
- just run http://localhost:8080/legals/lps/admin/dev-
console.lzx and http://localhost:8080/legals/lps/admin/dev-
console.lzx?lzr=dhtml and check in the changed files.
Should this be part of any build, or do we want to keep it a
manual step? (In the past, the dev console was frozen for a long
time under the 'if it works, don't fix it' philosophy.)
I say, keep it manual. It sucks when you're hacking on the LFC
and break something and it takes the console with it.
I think there's a middle ground here:
- 'ant build' should copy the console from a known place in the
source tree (lps/admin/proto?) into place, and 'ant clean' should
delete those copied files -- the console should *not* be checked in
where it is deployed
- the nightly build should rebuild the console from scratch and
compare with what's checked into the source tree. Any differences
trigger a build failure.
We need to fix more things if that is our policy. There are a number
of dirs that mix generated and controlled content. lps/includes/lfc
comes to mind...
