This changes how we reference the toolchain to use a Maven property. This will 
allow us to be more flexible and generic when configuring builds in Jenkins and 
we can avoid having a dedicated maven profile for each JDK version we want to 
support. A property can be overridden in the command-line, so it looks more 
convenient to configure it this way.

/cc @demobox
You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds/pull/1152

-- Commit Summary --

  * Define the JDK version in a Maven property

-- File Changes --

    M project/pom.xml (33)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/1152.patch
https://github.com/jclouds/jclouds/pull/1152.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1152

Reply via email to