On Thu, Nov 18, 2010 at 6:07 PM, Jeroen Vermeulen <[email protected]> wrote: > On 2010-11-18 23:48, Jonathan Lange wrote: > >> AIUI, we need it for some tests, and we need it for deployment. Why >> not get the tests to generate the wadl just-in-time, and have a >> separate make target for things that need to be done on deployment? > > Did you really just juxtapose the phrases "generate the wadl" and "just in > time" in a proper sentence? My compliments. ;) > > But that aside, much as I like the thought of not building the wadl during > development, wouldn't it invite hiccups in deployment? > > >> Also note that there's a 'make compile' step which builds practically >> everything you need for most tests, and does *not* build wadl. > > That does sound like it justifies what you said earlier. Developers > shouldn't have to predict such subtleties. Is the WADL secretly a test > resource that we set up too aggressively? >
To my mind, yes. However I believe it is also something that needs to be present on a deployed production system. I don't see how having a clear step "make deploy" that depends on "make build" would invite hiccoughs in production. jml _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
