On Mon, May 3, 2010 at 2:35 PM, Arvid Huss <[email protected]> wrote: > Hi Paul, > > inside Streamflow development we solved such problems by letting our build > server build the Qi4j snapshots on it's own. > Works pretty well. Never experienced any hickups the last 5 months and we > always have the newest code.
Considering the aversion to SNAPSHOT dependencies at Maven community, I tend to lean on dropping SNAPSHOT build publish from now on. It served a purpose when things were less stable. And the few that needs this 'bleeding edge' version, seems that there is a working solution for them (StreamFlow must be the most extreme case I think). So, can we agree on NOT putting up SNAPSHOT builds? Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
