I've moved the discussion about the solution into a different email thread. You are right about the cause (an Oracle change to the compiler). We don't need the compiler to be strict because of the sniffer plugin, so we can disable the check. I included a snippet and patch that can be used to disable that check in the default parent (and therefore in every Aries project). Regards, Tim Ward ------------------- Apache Aries PMC member & Enterprise OSGi advocate Enterprise OSGi in Action (http://www.manning.com/cummins) -------------------
> From: [email protected] > Date: Thu, 2 May 2013 13:42:00 +0100 > Subject: Re: [VOTE] Apache Aries release util-1.1.1 > To: [email protected] > > I'd +1 if we know the binaries built with Java 6 test ok with Java 7 > JRE. But I can't see that would be very easy to do. > > On 2 May 2013 12:30, Timothy Ward <[email protected]> wrote: > > Having thought I was doing the whole release with Java 7, it turns out that > > an update reset my JAVA_HOME. I can't build with Java 7 either. Looks like > > maybe we need a new parent release? > > Do you mean create a java7-parent pom? Or something else. I don't > think we need a java7-parent as that would be to enable us to write > code that relies on Java 7 specific features. > > I think this is causing the SDK to be (rightly) more sensitive: > > https://blogs.oracle.com/darcy/entry/bootclasspath_older_source > > Trouble is, I can't immediately see how to set the bootclasspath - > rt.jar location of java 5 in maven without changing the java5-parent > pom. What would be nice is a way of setting it in a machine specific > way. I tried configuring it in settings.xml but maven complains that > isn't allowed. > > Still looking... > > > Do we want to kill this release now and try to fix the Java 7 bug, or push > > the fix for util out and do new releases after parent is fixed? > > > > Tim Ward > > ------------------- > > Apache Aries PMC member & Enterprise OSGi advocate > > Enterprise OSGi in Action (http://www.manning.com/cummins) > > ------------------- > > > > > >> From: [email protected] > >> Date: Thu, 2 May 2013 11:06:55 +0100 > >> Subject: Re: [VOTE] Apache Aries release util-1.1.1 > >> To: [email protected] > >> > >> I see we still have the Aries Util tag awkwardness: > >> http://markmail.org/message/cukixfhhwnza773j (not a release stopper > >> though). > >> > >> Also, I get issues building this with Java 7. Is anyone else getting that? > >> > >> This is the error: > >> > >> [ERROR] Failed to execute goal > >> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile > >> (default-compile) on project org.apache.aries.util-r42: Compilation > >> failure: Compilation failure: > >> > >> [ERROR] could not parse error message: warning: [options] bootstrap > >> class path not set in conjunction with -source 1.5 > >> > >> > >> Thanks, > >> Jeremy > >> > >> On 2 May 2013 09:40, Timothy Ward <[email protected]> wrote: > >> > This is a vote for the release of the aries util bundle 1.1.1. This is a > >> > micro increment to aries util 1.1.0, including a bug fix for a > >> > significant issue in the SingleServiceTracker. > >> > The staging area is available here: > >> > https://repository.apache.org/content/repositories/orgapachearies-162/ > >> > > >> > Tags: > >> > http://svn.apache.org/viewvc/aries/tags/org.apache.aries.util-parent-1.1.1/ > >> > > >> > > >> > Note that although the util project only releases a single bundle, there > >> > are actually three sets of source in the repository. This is because the > >> > util project is part compiled under OSGi R4.2 and part under OSGi R4.3, > >> > then aggregated. Please verify the source releases for all three of > >> > util, util-r42 and util-parent. > >> > This vote will remain open for at least 72 hours. > >> > Tim Ward > >> > ------------------- > >> > Apache Aries PMC member & Enterprise OSGi advocate > >> > Enterprise OSGi in Action (http://www.manning.com/cummins) > >> > ------------------- > >> > > >
