You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Paul Lindner <li...@inuus.com> on 2011/03/24 18:16:05 UTC
Java 5/6 compatible builds
Please see
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 -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Java 5/6 compatible builds
Posted by Bob Balfe <ba...@us.ibm.com>.
You can do that in maven on a plugin basis.
http://maven.apache.org/general.html
...
<build>
...
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.0.2</version>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
</plugins>
...
</build>
- Bob
____________________________________________________________
STSM • IBM • US East Commerce Solutions • 720-395-2897 • Tie - 676-2897 •
http://blog.balfes.net
From: John Hjelmstad <fa...@google.com>
To: dev@shindig.apache.org,
Cc: Ryan J Baxter/Westford/IBM@Lotus
Date: 03/24/2011 01:50 PM
Subject: Re: Java 5/6 compatible builds
That's my general understanding from Paul. It allows us (though I don't
quite understand all the Maven juju) to write code and include dependencies
against 1.6, while falling back to 1.5 if needed.
One motivating use case for this in the immediate term is my and Michael's
reintroduction of Closure Compiler into the JS serving pipeline. It is
written against 1.6. My hope w/ these changes is to allow 1.6 users to get
the full Closure treatment, while falling back to a default (ie. using the
build-time JS YUICompressor).
@Paul, does this sound right? If so, can you give a brief primer on how
this
stuff works and what's required of both implementors and users?
--j
On Thu, Mar 24, 2011 at 10:25 AM, Ryan J Baxter <rj...@us.ibm.com>
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: rjbaxter@us.ibm.com
> Phone: 978-899-3041
> developerWorks Profile
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org,
> Date: 03/24/2011 01:19 PM
> Subject: Java 5/6 compatible builds
>
>
>
> Please see
>
> 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 -- lindner@inuus.com -- linkedin.com/in/plindner
>
>
>
>
Re: Java 5/6 compatible builds
Posted by John Hjelmstad <fa...@google.com>.
That's my general understanding from Paul. It allows us (though I don't
quite understand all the Maven juju) to write code and include dependencies
against 1.6, while falling back to 1.5 if needed.
One motivating use case for this in the immediate term is my and Michael's
reintroduction of Closure Compiler into the JS serving pipeline. It is
written against 1.6. My hope w/ these changes is to allow 1.6 users to get
the full Closure treatment, while falling back to a default (ie. using the
build-time JS YUICompressor).
@Paul, does this sound right? If so, can you give a brief primer on how this
stuff works and what's required of both implementors and users?
--j
On Thu, Mar 24, 2011 at 10:25 AM, Ryan J Baxter <rj...@us.ibm.com> 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: rjbaxter@us.ibm.com
> Phone: 978-899-3041
> developerWorks Profile
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org,
> Date: 03/24/2011 01:19 PM
> Subject: Java 5/6 compatible builds
>
>
>
> Please see
>
> 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 -- lindner@inuus.com -- linkedin.com/in/plindner
>
>
>
>
Re: Java 5/6 compatible builds
Posted by Ryan J Baxter <rj...@us.ibm.com>.
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: rjbaxter@us.ibm.com
Phone: 978-899-3041
developerWorks Profile
From: Paul Lindner <li...@inuus.com>
To: dev@shindig.apache.org,
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 <rj...@us.ibm.com>
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: rjbaxter@us.ibm.com
Phone: 978-899-3041
developerWorks Profile
From: Paul Lindner <li...@inuus.com>
To: dev@shindig.apache.org,
Date: 03/24/2011 01:19 PM
Subject: Java 5/6 compatible builds
Please see
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 -- lindner@inuus.com -- linkedin.com/in/plindner
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Java 5/6 compatible builds
Posted by Paul Lindner <li...@inuus.com>.
Java 5 will not have much loss of functionality. For now all we're doing is
adding runtime javascript compiler support via closure-compiler (which is
java6 only..)
There may be other tweaks depending on how upstream projects move.
Personally I'd rather just drop java 5 support -- but I know it's important
to a number of people here, so I hope this technical solution allows us to
make progress for everyone involved.
On Fri, Mar 25, 2011 at 8:55 AM, Michael Young <mi...@liferay.com>wrote:
> Will there be any loss of functionality in the OOB build if Java 5 is
> required?
>
> - Mike
> --
> Follow us on Twitter: liferay
>
> On Mar 24, 2011, at 10:50 AM, Paul Lindner wrote:
>
> > 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 <rj...@us.ibm.com>
> 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: rjbaxter@us.ibm.com
> >> Phone: 978-899-3041
> >> developerWorks Profile
> >>
> >>
> >>
> >> From: Paul Lindner <li...@inuus.com>
> >> To: dev@shindig.apache.org,
> >> Date: 03/24/2011 01:19 PM
> >> Subject: Java 5/6 compatible builds
> >>
> >>
> >>
> >> Please see
> >>
> >> 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 -- lindner@inuus.com -- linkedin.com/in/plindner
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
>
>
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Java 5/6 compatible builds
Posted by Michael Young <mi...@liferay.com>.
Will there be any loss of functionality in the OOB build if Java 5 is required?
- Mike
--
Follow us on Twitter: liferay
On Mar 24, 2011, at 10:50 AM, Paul Lindner wrote:
> 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 <rj...@us.ibm.com> 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: rjbaxter@us.ibm.com
>> Phone: 978-899-3041
>> developerWorks Profile
>>
>>
>>
>> From: Paul Lindner <li...@inuus.com>
>> To: dev@shindig.apache.org,
>> Date: 03/24/2011 01:19 PM
>> Subject: Java 5/6 compatible builds
>>
>>
>>
>> Please see
>>
>> 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 -- lindner@inuus.com -- linkedin.com/in/plindner
>>
>>
>>
>>
>
>
> --
> Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Java 5/6 compatible builds
Posted by Han Nguyen <hn...@us.ibm.com>.
+ 1 for Java upgrade and Shindig 3.0 release, thanks Paul for working on
this.
As I seem to be obsessed with Guice 3.0 and its JSR330 support :), I'm
still working through the tests for our own internal JSR330 distribution.
Since JSR330 is introduced in Java6 and doesn't exist in Java5, to provide
back level support we want to make sure that any Guice 3.0 JSR 330
artifacts won't be introduced in the java5 build.
Thanks,
-Han
From: Paul Lindner <li...@inuus.com>
To: Ryan J Baxter/Westford/IBM@Lotus
Cc: dev@shindig.apache.org
Date: 03/24/2011 02:02 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 <rj...@us.ibm.com>
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: rjbaxter@us.ibm.com
> Phone: 978-899-3041
> developerWorks Profile<
http://www.ibm.com/developerworks/mydeveloperworks/profiles/user/RyanJBaxter
>
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org,
> 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
<*r...@us.ibm.com>>
> 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: *rjbaxter@us.ibm.com* <rj...@us.ibm.com>
> Phone: *978-899-3041* <978-899-3041>
> developerWorks Profile
>
>
>
> From: Paul Lindner <*lindner@inuus.com* <li...@inuus.com>>
> To: *dev@shindig.apache.org* <de...@shindig.apache.org>,
> 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 -- *lindner@inuus.com* <li...@inuus.com> -- *
> linkedin.com/in/plindner* <http://linkedin.com/in/plindner>
>
>
>
>
>
>
> --
> Paul Lindner -- *lindner@inuus.com* <li...@inuus.com> -- *
> linkedin.com/in/plindner* <http://linkedin.com/in/plindner>
>
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Java 5/6 compatible builds
Posted by Ryan J Baxter <rj...@us.ibm.com>.
Thanks for the explanation Paul. My only suggestion then would be to
document all of this information.
-Ryan
Email: rjbaxter@us.ibm.com
Phone: 978-899-3041
developerWorks Profile
From: Paul Lindner <li...@inuus.com>
To: Ryan J Baxter/Westford/IBM@Lotus,
Cc: dev@shindig.apache.org
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 <rj...@us.ibm.com>
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: rjbaxter@us.ibm.com
> Phone: 978-899-3041
> developerWorks Profile<
http://www.ibm.com/developerworks/mydeveloperworks/profiles/user/RyanJBaxter
>
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org,
> 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
<*r...@us.ibm.com>>
> 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: *rjbaxter@us.ibm.com* <rj...@us.ibm.com>
> Phone: *978-899-3041* <978-899-3041>
> developerWorks Profile
>
>
>
> From: Paul Lindner <*lindner@inuus.com* <li...@inuus.com>>
> To: *dev@shindig.apache.org* <de...@shindig.apache.org>,
> 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 -- *lindner@inuus.com* <li...@inuus.com> -- *
> linkedin.com/in/plindner* <http://linkedin.com/in/plindner>
>
>
>
>
>
>
> --
> Paul Lindner -- *lindner@inuus.com* <li...@inuus.com> -- *
> linkedin.com/in/plindner* <http://linkedin.com/in/plindner>
>
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Java 5/6 compatible builds
Posted by Paul Lindner <li...@inuus.com>.
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 <rj...@us.ibm.com> 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: rjbaxter@us.ibm.com
> Phone: 978-899-3041
> developerWorks Profile<http://www.ibm.com/developerworks/mydeveloperworks/profiles/user/RyanJBaxter>
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org,
> 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 <*r...@us.ibm.com>>
> 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: *rjbaxter@us.ibm.com* <rj...@us.ibm.com>
> Phone: *978-899-3041* <978-899-3041>
> developerWorks Profile
>
>
>
> From: Paul Lindner <*lindner@inuus.com* <li...@inuus.com>>
> To: *dev@shindig.apache.org* <de...@shindig.apache.org>,
> 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 -- *lindner@inuus.com* <li...@inuus.com> -- *
> linkedin.com/in/plindner* <http://linkedin.com/in/plindner>
>
>
>
>
>
>
> --
> Paul Lindner -- *lindner@inuus.com* <li...@inuus.com> -- *
> linkedin.com/in/plindner* <http://linkedin.com/in/plindner>
>
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Java 5/6 compatible builds
Posted by Paul Lindner <li...@inuus.com>.
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 <rj...@us.ibm.com> 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: rjbaxter@us.ibm.com
> Phone: 978-899-3041
> developerWorks Profile
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org,
> Date: 03/24/2011 01:19 PM
> Subject: Java 5/6 compatible builds
>
>
>
> Please see
>
> 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 -- lindner@inuus.com -- linkedin.com/in/plindner
>
>
>
>
--
Paul Lindner -- lindner@inuus.com -- linkedin.com/in/plindner
Re: Java 5/6 compatible builds
Posted by Ryan J Baxter <rj...@us.ibm.com>.
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: rjbaxter@us.ibm.com
Phone: 978-899-3041
developerWorks Profile
From: Paul Lindner <li...@inuus.com>
To: dev@shindig.apache.org,
Date: 03/24/2011 01:19 PM
Subject: Java 5/6 compatible builds
Please see
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 -- lindner@inuus.com -- linkedin.com/in/plindner