Hi
I think your build of yesterday should be O.K. even if you used JDK 1.7
for the build as we instruct the maven-compiler-plugin to make use of
${jdk.version} (which is 1.6) both for the source as well as the target:
https://svn.apache.org/repos/asf/camel/trunk/pom.xml
And you could easily verify this by running one of the distribution
examples we have inside the tarballs using JDK 1.6 to see if they run well
using JDK 1.6.
Another easy way to verify this is to check that the class files major
version is 50 (in Java 7 it would be 51), e.g. on my workspace it's 50
EVEN IF I use JDK 1.7 for the build (because of the reason described
above):
~/dev/workspace/camel/camel-core/target/classes>javap -verbose
org.apache.camel.Route
Compiled from "Route.java"
public interface org.apache.camel.Route
SourceFile: "Route.java"
minor version: 0
major version: 50
Constant pool:
const #1 = class #42; // org/apache/camel/Route
const #2 = class #43; // java/lang/Object
const #3 = Asciz ID_PROPERTY;
const #4 = Asciz Ljava/lang/String;;
const #5 = Asciz ConstantValue;
const #6 = String #44; // id
const #7 = Asciz PARENT_PROPERTY;
const #8 = String #45; // parent
That all said to make it 100% x 100% sure, yes you could initiate another
build.
Babak
Am 10.04.13 09:29 schrieb "Claus Ibsen" unter <claus.ib...@gmail.com>:
>Hi
>
>Yeah this early in the VOTE it could IMHO be a good idea to redo the
>release with JDK6.
>There is a few minor commits on trunk, you can pickup as well.
>
>Is there some way in Maven release plugin or similar to have a way for
>it to fail if not using a specific JDK. Then we could have this
>validated for future. As I assume this can happen again.
>
>Adding a note to the release guide may also help about checking that
>the right JDK version is used.
>
>
>
>
>On Wed, Apr 10, 2013 at 8:58 AM, Christian Müller
><christian.muel...@gmail.com> wrote:
>> Today morning I realized I build the Camel 2.11.0 release with Java 7.
>> Because we didn't drop the support for Java 6 with 2.11.0, I consider to
>> cancel this vote again and build a new release today evening.
>>
>> Comments?
>>
>> Regards,
>> Christian
>>
>>
>> On Tue, Apr 9, 2013 at 7:48 PM, Christian Müller <
>> christian.muel...@gmail.com> wrote:
>>
>>> After 9 month of development, we have a new minor release candidate
>>> apache-camel-2.11.0 ready.
>>> It comes with 656 issues resolved: new features, improvements and bug
>>> fixes [1]. You can find the release notes here [2].
>>>
>>> Please find the staging repo here:
>>> https://repository.apache.org/content/repositories/orgapachecamel-082/
>>>
>>> The tarballs are here
>>>
>>>
>>>https://repository.apache.org/content/repositories/orgapachecamel-082/or
>>>g/apache/camel/apache-camel/2.11.0/
>>>
>>> Tag:
>>> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/
>>>
>>> Please review, help out with testing and vote to approve this release
>>> binary. Please mention what you tested to prevent duplicate work. Your
>>>vote
>>> counts!
>>>
>>> [ ] +1 Release the binary as Apache Camel 2.11.0
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for at least 72 hours.
>>>
>>> Thanks in advance,
>>> Christian
>>>
>>> [1]
>>>
>>>https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%2
>>>0fixVersion%20%3D%20%222.11.0%22
>>> [2]
>>>
>>>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231121
>>>1&version=12321695
>>>
>
>
>
>--
>Claus Ibsen
>-----------------
>Red Hat, Inc.
>FuseSource is now part of Red Hat
>Email: cib...@redhat.com
>Web: http://fusesource.com
>Twitter: davsclaus
>Blog: http://davsclaus.com
>Author of Camel in Action: http://www.manning.com/ibsen
