It's difficult to know which places are important to you. If maven changed any default, even defaults you didn't know existed, it could make your old builds no longer reproducible.
With that in mind, reconsider: "Precise details of localisation are *so* business-critical [snip] and you leave the localisation settings at their *defaults*?" There's an immense amount of code that would fall over if Java changed its default locale to Turkish, and I bet yours is included. Not that that case would ever happen, but I'm sure you get the idea. On Sat, Jun 25, 2011 at 12:37 PM, Kevin Wright <[email protected]> wrote: > > > On 25 June 2011 12:21, Ricky Clarkson <[email protected]> wrote: >> >> Just think how many defaults you're 'irresponsibly' relying on in >> maven, for example. > > Indeed, silently trusting Maven to automatically "do the right thing" in > places that are important to me is a recipe for disaster. For example, I > lose count of the number of times that I've tried to perform some task on my > laptop, offline, just to discover that Maven hasn't yet downloaded the > prerequisite plugin... > Then again, you know full well that I'm almost exclusively an SBT user > nowadays; partly because Maven has exactly this awkward habit of shifting > around beneath my feet. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
