Re: Camel 2.11.0 release

Hi Could it be that your ISP assigns you a dynamic (not a static) IP and somewhere along the release process you rebooted your box? See the first paragraph of "10.4.1. Closing an Open Repository": http://www.sonatype.com/books/nexus-book/reference/staging-sect-managing-staging.html You can see

Camel 2.11.0 release

The second time, Nexus created two staging repositories for the Camel 2.11.0 release candidate. Does somebody know why or how I can prevent this? Best, Christian

Re: Nexus: Staging Completed.

Hi guys, > I think we still support Java 6 in Camel extra 2.11.0. I'm afraid we have to > redo this release (happens to me with the Camel 2.11.0 release too :-( ). You even didn't give me a chance to announce release staged :) . I'm not sure why we should drop the staged release. The byte code h

Re: camel-quartz 2.10.4 against quartz 2.1.7 bug?

Thanks for the update. Recommend putting this information on the documentation page to prevent future inquiries. http://camel.apache.org/quartz.html has no information about version (in-)compatibility. Thanks, -mox -- View this message in context: http://camel.465427.n5.nabble.com/camel-qua

[CANCEL][VOTE] Release Apache Camel 2.11.0 (take 2)

Because the last release candidate was build using Java 7 and the PDF was messed up, I cancel this vote. I corrected my Prince XML installation and it works now. Please expect a new release candidate later today or tomorrow morning. Sorry for the noise... Best, Christian On Wed, Apr 10, 2013 at

Re: [VOTE] Release Apache Camel 2.11.0 (take 2)

At present I'm using: cmueller$ /usr/local/lib/prince/bin/prince --version Prince 8.1 rev 5 Copyright 2002-2013 YesLogic Pty. Ltd. Non-commercial License Will downgrade and build again. If it works, I will cancel this this vote and start a new build... Best, Christian On Wed, Apr 10, 2013 at 1

Re: [VOTE] Release Apache Camel 2.11.0 (take 2)

And also the links of TOC don't work by the staging repo version, e.g. click on: Introduction... 23 Nothing happens, in contrast to the one from my box where it JUMPS to the Introduction pa

Re: [VOTE] Release Apache Camel 2.11.0 (take 2)

The PDF is readable but TOC is scattered through 21 pages! See the pages 2…22 As well look at the formatting of the page 23. For a better comparison for you this is the one from the staging repo: camel-manual-2.11.0.pdf

Re: [VOTE] Release Apache Camel 2.11.0 (take 2)

I can check my price version later. What do you exactlymean with "corrup"? Can you open the PDF (I can)? Formatting issues? I can redo the release later today... Best, Christian On Wed, Apr 10, 2013 at 11:09 AM, Babak Vahdat wrote: > Hi Christian, > > sorry for the noise again but the PDF manu

Camel.trunk.notest - Build # 1839 - Fixed

The Apache Jenkins build system has built Camel.trunk.notest (build #1839) Status: Fixed Check console output at https://builds.apache.org/job/Camel.trunk.notest/1839/ to view the results.

Re: [VOTE] Release Apache Camel 2.11.0 (take 2)

Hi Christian, sorry for the noise again but the PDF manual still seems to be corrupt! The generated PDF on my box seems much better. Which version do you have? I've got the following: ~/dev/prince>prince --version Prince 8.0 Copyright 2002-2011 YesLogic Pty. Ltd. Non-commercial License Babak C

Re: [VOTE] Release Apache Camel 2.11.0 (take 2)

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 veri

Re: [VOTE] Release Apache Camel 2.11.0 (take 2)

You can use the enforcer plugin to enforce stuff (and optionally have it active in a profile to only run when you want/during preparing a release): http://maven.apache.org/enforcer/maven-enforcer-plugin/ Animal sniffer could be something to look into as an alternative if you in fact want to build

Re: [VOTE] Release Apache Camel 2.11.0 (take 2)

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 validate

Re: Nexus: Staging Completed.

I think we still support Java 6 in Camel extra 2.11.0. I'm afraid we have to redo this release (happens to me with the Camel 2.11.0 release too :-( ). Best, Christian On Wed, Apr 10, 2013 at 4:42 AM, Nexus Repository Manager < ne...@oss.sonatype.org> wrote: > > > *Deployer properties:* > >-