[Cosmo-dev] Built dojo.js with war:inplace

Travis Vachon travis at osafoundation.org
Mon Sep 24 10:31:38 PDT 2007

Hmm, I don't see this much because I usually use a custom local build  
of dojo.js (a minimal build for developing and a full production  
build when appropriate for testing).

Bear: any thoughts why this might be happening?


On Sep 18, 2007, at 4:46 PM, Matthew Eernisse wrote:

> I've had this problem several times now (and it just happened again).
> I build the app with an in-place war (mvn clean compile  
> war:inplace), start working, and don't see the results of any of my  
> changes. Usually I snap after scratching my head for a couple of  
> minutes, and check the dojo.js file -- and sure enough, it's a  
> cooked version with all the Cosmo code in it.
> I was originally thinking that layered builds might mitigate this  
> problem, but there's no reason to think whatever is getting missed  
> here wouldn't result in built 'layered' files as well.
> Is there some way to automate things in the build so this doesn't  
> keep happening?
> Matthew
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev

More information about the cosmo-dev mailing list