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: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: [VOTE] Release Apache Camel 2.12.3
From: Daniel Kulp <dkulp@apache.org>
In-Reply-To: <001201cf2e07$5ccb7480$16625d80$@de>
Date: Thu, 20 Feb 2014 09:29:15 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <812E5217-AF43-4E99-92FB-52DF15D58A67@apache.org>
References: <53003B9C.1040807@gmail.com>
	<1392545183398-5747366.post@n5.nabble.com>
	<1392564927340-5747375.post@n5.nabble.com>
	<etPan.530169df.6b8b4567.158@dhcp-16-106.nay.redhat.com>
	<1392631591037-5747421.post@n5.nabble.com>	<5304BBD4.8060505@gmail.com>
	<1392823196265-5747563.post@n5.nabble.com>	<5304D004.8060601@gmail.com>
 <CAD0r13esLTQ9qmQ867HcqQ+35wveRgD-tsdPxoX33VANacNE=g@mail.gmail.com>
 <001201cf2e07$5ccb7480$16625d80$@de>
To: dev@camel.apache.org


On Feb 20, 2014, at 1:45 AM, Jan Mat=E8rne (jhm) <apache@materne.de> =
wrote:
>> I'll give it another 12 hours and if nothing changes I will close
>> the vote and release 2.12.3. If within this time you convince another
>> PMC member to change his vote I will cancel this vote.
>=20
> I am also a fan a building against the oldest supported platform.
> Would it be possible to=20
> - build Camel against Java6 for getting the "right" class file format
> - generate the html using Java7
> - jar them using Java6?

We could easily make the annotations be RetentionPolicy.RUNTIME so they =
are kept in the compiled classes.   At that point, we have two options =
that could work with java6:

1)  Write a utility class that would take a Class object and generate =
the appropriate HTML.   Tools could easily use this.   This could be =
designed with protected methods or something so that they could override =
parts of it to customize what is generated as they need.

2) Create a maven plugin that runs in process-classes to generate static =
HTML.  It could possibly even use the utility from (1).

Again, both would work fine with java 6.

In any case, I also strongly believe that anything that is NOT built as =
part of using our lowest supported JDK is =93optional=94.    If it is or =
is not part of the convenience artifacts is irrelevant from a release =
standpoint.    If people want that functionality, find a way to make it =
not optional.


Dan


> Another option would drop Java6 ... But as Oracle writes [2] for =
Java6:
> - Feb 2011: End of Public Updates Notification
> - Feb 2013: End of Public Updates
> - Dec 2013: Premier Support Until
> BUT
> - Jun 2017: Extended Support Until
>=20
>=20
> [2] http://www.oracle.com/technetwork/java/eol-135779.html
>=20
> Jan
>=20

--=20
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com