Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.220.47 as permitted sender)
Date: Fri, 21 Feb 2014 01:18:58 +0800
From: Willem Jiang <willem.jiang@gmail.com>
To: dev@camel.apache.org, Daniel Kulp <dkulp@apache.org>
Message-ID: <etPan.53086010.19495cff.ac@Willems-MacBook-Pro.local>
Subject: Re: [VOTE] Release Apache Camel 2.12.3
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="53086010_2ae8944a_ac"

--53086010_2ae8944a_ac
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


Hi Dan,

Thanks for the inputs.

Current the html generator is based the APT processor, But it looks JDK6 =
have some trouble to load the APT processor when compile the code, I=E2=80=
=99m not sure if I can fix it tomorrow.

At mean while, I suggest we can spend some time to address this JDK compi=
le issue after Camel 2.12.3 is released, so it won=E2=80=99t block the Ac=
tiveMQ release.


-- =20
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (=
English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang =20
Weibo: =E5=A7=9C=E5=AE=81willem


On =46ebruary 20, 2014 at 10:29:47 PM, Daniel Kulp (dkulp=40apache.org) w=
rote:
> =20
> =20
> On =46eb 20, 2014, at 1:45 AM, Jan Mat=C3=A8rne (jhm) =20
> wrote:
> >> I'll give it another 12 hours and if nothing changes I will close =20
> >> the vote and release 2.12.3. If within this time you convince =20
> another
> >> PMC member to change his vote I will cancel this vote.
> >
> > I am also a fan a building against the oldest supported platform. =20
> > Would it be possible to
> > - build Camel against Java6 for getting the =22right=22 class file =20
> format
> > - generate the html using Java7
> > - jar them using Java6=3F
> =20
> We could easily make the annotations be RetentionPolicy.RUNTIME =20
> so they are kept in the compiled classes. At that point, we have =20
> two options that could work with java6:
> =20
> 1) Write a utility class that would take a Class object and generate =20
> the appropriate HTML. Tools could easily use this. This could =20
> be designed with protected methods or something so that they =20
> could override parts of it to customize what is generated as they =20
> need.
> =20
> 2) Create a maven plugin that runs in process-classes to generate =20
> static HTML. It could possibly even use the utility from (1). =20
> =20
> Again, both would work fine with java 6.
> =20
> In any case, I also strongly believe that anything that is NOT =20
> built as part of using our lowest supported JDK is =E2=80=9Coptional=E2=
=80=9D. =20
> If it is or is not part of the convenience artifacts is irrelevant =20
> from a release standpoint. If people want that functionality, =20
> find a way to make it not optional.
> =20
> =20
> Dan
> =20
> =20
> =20
> > Another option would drop Java6 ... But as Oracle writes =5B2=5D =20
> for Java6:
> > - =46eb 2011: End of Public Updates Notification
> > - =46eb 2013: End of Public Updates
> > - Dec 2013: Premier Support Until
> > BUT
> > - Jun 2017: Extended Support Until
> >
> >
> > =5B2=5D http://www.oracle.com/technetwork/java/eol-135779.html =20
> >
> > Jan
> >
> =20
> --
> Daniel Kulp
> dkulp=40apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
> =20
> =20

--53086010_2ae8944a_ac--