Thanks for the explanation Paul. My only suggestion then would be to document all of this information.
-Ryan Email: [email protected] Phone: 978-899-3041 developerWorks Profile From: Paul Lindner <[email protected]> To: Ryan J Baxter/Westford/IBM@Lotus, Cc: [email protected] Date: 03/24/2011 01:59 PM Subject: Re: Java 5/6 compatible builds Java 1.6 code goes only into src/main/java16 You should only reference stuff in there via a Guice module that binds those classes at a very high level while leaving the default to use a no-op implementation. For example John has a runtime compiler interface he injects. For Java 1.6 that will get bound to the Closure Compiler. On Thu, Mar 24, 2011 at 10:53 AM, Ryan J Baxter <[email protected]> wrote: > OK so what's going to happen if I deliver code that uses functionality in > 1.6 that is not available in 1.5? People who build against 1.5 will have > problems building the code. > > -Ryan > > Email: [email protected] > Phone: 978-899-3041 > developerWorks Profile< http://www.ibm.com/developerworks/mydeveloperworks/profiles/user/RyanJBaxter > > > > > From: Paul Lindner <[email protected]> > To: [email protected], > Cc: Ryan J Baxter/Westford/IBM@Lotus > Date: 03/24/2011 01:50 PM > Subject: Re: Java 5/6 compatible builds > ------------------------------ > > > > This defines two profiles, java5 and java6 which are activated by the jdk > you build with. > > For 1.6 artifacts are compiled for -source/-target 1.6 and for certain > directories we enable a src/main/java16 and can enable 1.6-only dependencies > like closure compiler. > > For 1.5 the artifacts use a classifier 'java5' so you'd have > shindig-common-3.0.0-java5.jar, which will live beside the 1.6 versions. > > Thus for anyone wanting to use the java5 artifacts you will need to add > <classifier>java5</classifier> to your pom to get that particular version. > > It *should* be fairly seemless. The only tricky bits will be pushing the > artifacts into maven central, which might take a couple of tries. > > > On Thu, Mar 24, 2011 at 10:25 AM, Ryan J Baxter <*[email protected]*<[email protected]>> > wrote: > Paul, I am not so familiar with Maven so excuse me if the answer to this > questions is obvious.... > > Are these changes to allow us to choose whether we want to build against > Java 5 or 6? > > -Ryan > > Email: *[email protected]* <[email protected]> > Phone: *978-899-3041* <978-899-3041> > developerWorks Profile > > > > From: Paul Lindner <*[email protected]* <[email protected]>> > To: *[email protected]* <[email protected]>, > Date: 03/24/2011 01:19 PM > Subject: Java 5/6 compatible builds > > > > Please see > * > **http://codereview.appspot.com/4276074/*< http://codereview.appspot.com/4276074/> > > This is another reason I want to push out a 3.0.0 beta since this would > entail adjusting the release process to accomodate compatibility artifacts > classified as 'java5' and moving the baseline to java6. > > > -- > Paul Lindner -- *[email protected]* <[email protected]> -- * > linkedin.com/in/plindner* <http://linkedin.com/in/plindner> > > > > > > > -- > Paul Lindner -- *[email protected]* <[email protected]> -- * > linkedin.com/in/plindner* <http://linkedin.com/in/plindner> > -- Paul Lindner -- [email protected] -- linkedin.com/in/plindner
