Since I had to go ask to be sure what John meant: he's talking about something like the sentinels we use for version branding, and an explicit <outofdate> check on the sentinel against all the jar contents (that is, <sourcefiles> + <artifacts>) before trusting <jar>.
It seems ugly, in that ant and <jar> are supposed to do that for me and we shouldn't need to reinvent, but it would work. :-/ On Wed, Jun 3, 2009 at 3:20 PM, John Tamplin <[email protected]> wrote: > On Wed, Jun 3, 2009 at 3:10 PM, Scott Blum <[email protected]> wrote: > >> One thing we could do: without necessarily modifying gwt.jar right this >> second, we could just manually reorder the existing rules such that we list >> files known to be newer first. Then if we really care, we could update a >> custom ant task later that uses timestamp to choose between identicals. >> Would that be better or worse than the track we're on now? >> > > How about just adding flag files and depending on them? > > -- > John A. Tamplin > Software Engineer (GWT), Google > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
