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 <[email protected]>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 <[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]
> >> Phone: 978-899-3041
> >> developerWorks Profile
> >>
> >>
> >>
> >> From:   Paul Lindner <[email protected]>
> >> To:     [email protected],
> >> 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 -- [email protected] -- linkedin.com/in/plindner
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Paul Lindner -- [email protected] -- linkedin.com/in/plindner
>
>


-- 
Paul Lindner -- [email protected] -- linkedin.com/in/plindner

Reply via email to