I agree it's not ideal, but I'm open to suggestions as to how to guarantee code from a particular project works in a java 1.4 environment?
-----Original Message----- From: Graham Leggett [mailto:[EMAIL PROTECTED] Sent: 29 March 2008 00:25 To: Maven Users List Subject: Re: Best practices for java version? Richard Chamberlain wrote: > It works internally at our company as we all have build tools (jdk etc) > in a standard place. This makes it repeatable and > guaranteed not to blow up on a 1.4 environment. There is no such thing as a "standard" place for build tools - a new contractor comes in, and suddenly has to rearrange their laptop to accommodate some weird directory structure that is different to their existing setup. That's a significant waste of time and money. Then you decide to upgrade from Win2k to XP, and from XP to Vista, and Vista to whatever, and suddenly the default location of the JDK changes for whatever reason and all your code breaks. Hard coding paths is one of the exact things that was rife in ant builds and that maven moves away from, and that makes code management significantly less painful and more robust. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
