You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Oliver Heger <ol...@oliver-heger.de> on 2016/07/30 20:02:55 UTC
[VOTE] Release Configuration 2.1 based on RC2
Hi all,
after the failed vote for RC1 a new RC has been created. The only
difference is that the checkstyle plugin has been downgraded which
should allow building the project on Java 1.6.
Configuration 2.1 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration
(revision 14582)
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1194/
Details of changes since 2.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
https://home.apache.org/~oheger/configuration-2.1-rc2/changes-report.html
Here is the tag:
http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC2
(revision 1754628)
Site:
https://home.apache.org/~oheger/configuration-2.1-rc2/
(note some links in the menu are not yet working)
KEYS:
http://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now, i.e. after 2000
GMT 02-Aug-2016
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thanks!
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Dennis Kieselhorst <de...@apache.org>.
Hi Oliver!
> so do we have a confirmation that the current state in trunk builds
> correctly on the problematic platforms? Then I could start preparing
> another RC in the next days.
>
As the checkstyle config is now adapted, please prepare another RC.
Cheers
Dennis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Oliver Heger <ol...@oliver-heger.de>.
Hi,
so do we have a confirmation that the current state in trunk builds
correctly on the problematic platforms? Then I could start preparing
another RC in the next days.
Thanks
Oliver
Am 02.08.2016 um 09:08 schrieb Dennis Kieselhorst:
> Hi Gary!
>> We have a mini-mess here:
>>
>> - checkstyle's check is called from the build and it fails.
>> - Did it ever work?
>> - Did it work and then the code degraded between the last release and this
>> code base? The 2.0 checkstyle is clean:
>> https://commons.apache.org/proper/commons-configuration/checkstyle.html
>> - Have the checkstyle default rules changed between the checkstyle version
>> used in 2.0 and now?
>> - Have the checkstyle custom rules we use changed between the checkstyle
>> version used in 2.0 and now?
>> - The code could be fixed to match the rules of course.
>>
> The generated code never matched the ruleset and I think it would be
> hart to fix the code generation so I've added an exclude for that. Could
> you please try trunk and see if it's ok for you?
>
> After that we should build an RC3.
>
> Regards
> Dennis
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Dennis Kieselhorst <de...@apache.org>.
Hi Gary!
> We have a mini-mess here:
>
> - checkstyle's check is called from the build and it fails.
> - Did it ever work?
> - Did it work and then the code degraded between the last release and this
> code base? The 2.0 checkstyle is clean:
> https://commons.apache.org/proper/commons-configuration/checkstyle.html
> - Have the checkstyle default rules changed between the checkstyle version
> used in 2.0 and now?
> - Have the checkstyle custom rules we use changed between the checkstyle
> version used in 2.0 and now?
> - The code could be fixed to match the rules of course.
>
The generated code never matched the ruleset and I think it would be
hart to fix the code generation so I've added an exclude for that. Could
you please try trunk and see if it's ok for you?
After that we should build an RC3.
Regards
Dennis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Gary Gregory <ga...@gmail.com>.
On Mon, Aug 1, 2016 at 2:23 PM, Gary Gregory <ga...@gmail.com> wrote:
> Another thing: The whole point of adding checkstyle check to the build is
> to have the build fail when there are violations. Otherwise, just look at
> the report on the generated site.
>
> It seems to me that the options are:
> - Remove the check from the build
> - Fix the code.
>
> My previous questions still stand but it's not critical WRT blocking a
> release.
>
Well, aside from the fact that I cannot build the thing... so something
needs to be done, the RM can pick IMO but that means another RC :-(
Gary
>
> That's it.
>
> Gary
>
> On Mon, Aug 1, 2016 at 1:30 PM, Oliver Heger <oliver.heger@oliver-heger.de
> > wrote:
>
>>
>>
>> Am 01.08.2016 um 21:50 schrieb Gary Gregory:
>> > On Mon, Aug 1, 2016 at 12:38 PM, Oliver Heger <
>> oliver.heger@oliver-heger.de>
>> > wrote:
>> >
>> >>
>> >>
>> >> Am 01.08.2016 um 11:04 schrieb Dennis Kieselhorst:
>> >>> Hi Benedikt!
>> >>>
>> >>>> The build log is here [1]. It looks like some generated classes are
>> >> checked
>> >>>> by checkstyle which causes the build to fail. The build works with
>> Java
>> >> 7
>> >>>> and Java 8. So my vote again is -1 because I think mvn clean install
>> >> should
>> >>>> work with the minimum required JDK out of the box. Sorry.
>> >>>>
>> >>> That's strange, I don't see why it should behave differently. Anyway
>> >>> I've added an exclude for it (this was already done for rat and
>> clirr).
>> >>> This time I installed the same versions you used to build it, so next
>> >>> time it should be successful. Sorry for being lazy last time...
>> >>
>> >> Many thanks, Dennis.
>> >>
>> >> I see the checkstyle plugin has a failOnViolation flag which is *true*
>> >> per default. Should we set it to *false* (this would be my preference).
>> >>
>> >> I will leave the vote open for now. To make it clear: There is no
>> >> problem with the artifacts, they are fully compatible with Java 1.6.
>> >> There is only an issue when building with 1.6 which should not affect
>> >> many users.
>> >>
>> >> However, I am skeptical whether this vote will pass.
>> >>
>> >
>> > Well, yeah, the build should work out of the box. With Java 6 and 7, for
>> > 'mvn clean site', I get:
>> >
>> > [INFO] --- maven-checkstyle-plugin:2.15:check (default) @
>> > commons-configuration2 ---
>> > [INFO] There are 1238 errors reported by Checkstyle 6.1.1 with
>> > E:\temp\rc\commons-configuration2-2.1-src/conf/checkstyle.xml ruleset.
>> > [ERROR]
>> >
>> target\generated-sources\javacc\org\apache\commons\configuration2\plist\ParseException.java[0]
>> > (javadoc) JavadocPackage: Missing package-info.java file.
>> >
>> > I cannot imagine Java 8 would be any different.
>>
>> This is indeed strange. I do not see these errors when building with
>> Java 7 and 8. I have created the web site for the RC that way.
>>
>> Maybe it depends on the Maven version?
>>
>> Oliver
>>
>> >
>> > We have a mini-mess here:
>> >
>> > - checkstyle's check is called from the build and it fails.
>> > - Did it ever work?
>> > - Did it work and then the code degraded between the last release and
>> this
>> > code base? The 2.0 checkstyle is clean:
>> > https://commons.apache.org/proper/commons-configuration/checkstyle.html
>> > - Have the checkstyle default rules changed between the checkstyle
>> version
>> > used in 2.0 and now?
>> > - Have the checkstyle custom rules we use changed between the checkstyle
>> > version used in 2.0 and now?
>> > - The code could be fixed to match the rules of course.
>> >
>> > Gary
>> >
>> >
>> >> Oliver
>> >>
>> >>>
>> >>> Regards
>> >>> Dennis
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> >>> For additional commands, e-mail: dev-help@commons.apache.org
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> >> For additional commands, e-mail: dev-help@commons.apache.org
>> >>
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Gary Gregory <ga...@gmail.com>.
Another thing: The whole point of adding checkstyle check to the build is
to have the build fail when there are violations. Otherwise, just look at
the report on the generated site.
It seems to me that the options are:
- Remove the check from the build
- Fix the code.
My previous questions still stand but it's not critical WRT blocking a
release.
That's it.
Gary
On Mon, Aug 1, 2016 at 1:30 PM, Oliver Heger <ol...@oliver-heger.de>
wrote:
>
>
> Am 01.08.2016 um 21:50 schrieb Gary Gregory:
> > On Mon, Aug 1, 2016 at 12:38 PM, Oliver Heger <
> oliver.heger@oliver-heger.de>
> > wrote:
> >
> >>
> >>
> >> Am 01.08.2016 um 11:04 schrieb Dennis Kieselhorst:
> >>> Hi Benedikt!
> >>>
> >>>> The build log is here [1]. It looks like some generated classes are
> >> checked
> >>>> by checkstyle which causes the build to fail. The build works with
> Java
> >> 7
> >>>> and Java 8. So my vote again is -1 because I think mvn clean install
> >> should
> >>>> work with the minimum required JDK out of the box. Sorry.
> >>>>
> >>> That's strange, I don't see why it should behave differently. Anyway
> >>> I've added an exclude for it (this was already done for rat and clirr).
> >>> This time I installed the same versions you used to build it, so next
> >>> time it should be successful. Sorry for being lazy last time...
> >>
> >> Many thanks, Dennis.
> >>
> >> I see the checkstyle plugin has a failOnViolation flag which is *true*
> >> per default. Should we set it to *false* (this would be my preference).
> >>
> >> I will leave the vote open for now. To make it clear: There is no
> >> problem with the artifacts, they are fully compatible with Java 1.6.
> >> There is only an issue when building with 1.6 which should not affect
> >> many users.
> >>
> >> However, I am skeptical whether this vote will pass.
> >>
> >
> > Well, yeah, the build should work out of the box. With Java 6 and 7, for
> > 'mvn clean site', I get:
> >
> > [INFO] --- maven-checkstyle-plugin:2.15:check (default) @
> > commons-configuration2 ---
> > [INFO] There are 1238 errors reported by Checkstyle 6.1.1 with
> > E:\temp\rc\commons-configuration2-2.1-src/conf/checkstyle.xml ruleset.
> > [ERROR]
> >
> target\generated-sources\javacc\org\apache\commons\configuration2\plist\ParseException.java[0]
> > (javadoc) JavadocPackage: Missing package-info.java file.
> >
> > I cannot imagine Java 8 would be any different.
>
> This is indeed strange. I do not see these errors when building with
> Java 7 and 8. I have created the web site for the RC that way.
>
> Maybe it depends on the Maven version?
>
> Oliver
>
> >
> > We have a mini-mess here:
> >
> > - checkstyle's check is called from the build and it fails.
> > - Did it ever work?
> > - Did it work and then the code degraded between the last release and
> this
> > code base? The 2.0 checkstyle is clean:
> > https://commons.apache.org/proper/commons-configuration/checkstyle.html
> > - Have the checkstyle default rules changed between the checkstyle
> version
> > used in 2.0 and now?
> > - Have the checkstyle custom rules we use changed between the checkstyle
> > version used in 2.0 and now?
> > - The code could be fixed to match the rules of course.
> >
> > Gary
> >
> >
> >> Oliver
> >>
> >>>
> >>> Regards
> >>> Dennis
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >>> For additional commands, e-mail: dev-help@commons.apache.org
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Oliver Heger <ol...@oliver-heger.de>.
Am 01.08.2016 um 21:50 schrieb Gary Gregory:
> On Mon, Aug 1, 2016 at 12:38 PM, Oliver Heger <ol...@oliver-heger.de>
> wrote:
>
>>
>>
>> Am 01.08.2016 um 11:04 schrieb Dennis Kieselhorst:
>>> Hi Benedikt!
>>>
>>>> The build log is here [1]. It looks like some generated classes are
>> checked
>>>> by checkstyle which causes the build to fail. The build works with Java
>> 7
>>>> and Java 8. So my vote again is -1 because I think mvn clean install
>> should
>>>> work with the minimum required JDK out of the box. Sorry.
>>>>
>>> That's strange, I don't see why it should behave differently. Anyway
>>> I've added an exclude for it (this was already done for rat and clirr).
>>> This time I installed the same versions you used to build it, so next
>>> time it should be successful. Sorry for being lazy last time...
>>
>> Many thanks, Dennis.
>>
>> I see the checkstyle plugin has a failOnViolation flag which is *true*
>> per default. Should we set it to *false* (this would be my preference).
>>
>> I will leave the vote open for now. To make it clear: There is no
>> problem with the artifacts, they are fully compatible with Java 1.6.
>> There is only an issue when building with 1.6 which should not affect
>> many users.
>>
>> However, I am skeptical whether this vote will pass.
>>
>
> Well, yeah, the build should work out of the box. With Java 6 and 7, for
> 'mvn clean site', I get:
>
> [INFO] --- maven-checkstyle-plugin:2.15:check (default) @
> commons-configuration2 ---
> [INFO] There are 1238 errors reported by Checkstyle 6.1.1 with
> E:\temp\rc\commons-configuration2-2.1-src/conf/checkstyle.xml ruleset.
> [ERROR]
> target\generated-sources\javacc\org\apache\commons\configuration2\plist\ParseException.java[0]
> (javadoc) JavadocPackage: Missing package-info.java file.
>
> I cannot imagine Java 8 would be any different.
This is indeed strange. I do not see these errors when building with
Java 7 and 8. I have created the web site for the RC that way.
Maybe it depends on the Maven version?
Oliver
>
> We have a mini-mess here:
>
> - checkstyle's check is called from the build and it fails.
> - Did it ever work?
> - Did it work and then the code degraded between the last release and this
> code base? The 2.0 checkstyle is clean:
> https://commons.apache.org/proper/commons-configuration/checkstyle.html
> - Have the checkstyle default rules changed between the checkstyle version
> used in 2.0 and now?
> - Have the checkstyle custom rules we use changed between the checkstyle
> version used in 2.0 and now?
> - The code could be fixed to match the rules of course.
>
> Gary
>
>
>> Oliver
>>
>>>
>>> Regards
>>> Dennis
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Gary Gregory <ga...@gmail.com>.
On Mon, Aug 1, 2016 at 12:38 PM, Oliver Heger <ol...@oliver-heger.de>
wrote:
>
>
> Am 01.08.2016 um 11:04 schrieb Dennis Kieselhorst:
> > Hi Benedikt!
> >
> >> The build log is here [1]. It looks like some generated classes are
> checked
> >> by checkstyle which causes the build to fail. The build works with Java
> 7
> >> and Java 8. So my vote again is -1 because I think mvn clean install
> should
> >> work with the minimum required JDK out of the box. Sorry.
> >>
> > That's strange, I don't see why it should behave differently. Anyway
> > I've added an exclude for it (this was already done for rat and clirr).
> > This time I installed the same versions you used to build it, so next
> > time it should be successful. Sorry for being lazy last time...
>
> Many thanks, Dennis.
>
> I see the checkstyle plugin has a failOnViolation flag which is *true*
> per default. Should we set it to *false* (this would be my preference).
>
> I will leave the vote open for now. To make it clear: There is no
> problem with the artifacts, they are fully compatible with Java 1.6.
> There is only an issue when building with 1.6 which should not affect
> many users.
>
> However, I am skeptical whether this vote will pass.
>
Well, yeah, the build should work out of the box. With Java 6 and 7, for
'mvn clean site', I get:
[INFO] --- maven-checkstyle-plugin:2.15:check (default) @
commons-configuration2 ---
[INFO] There are 1238 errors reported by Checkstyle 6.1.1 with
E:\temp\rc\commons-configuration2-2.1-src/conf/checkstyle.xml ruleset.
[ERROR]
target\generated-sources\javacc\org\apache\commons\configuration2\plist\ParseException.java[0]
(javadoc) JavadocPackage: Missing package-info.java file.
I cannot imagine Java 8 would be any different.
We have a mini-mess here:
- checkstyle's check is called from the build and it fails.
- Did it ever work?
- Did it work and then the code degraded between the last release and this
code base? The 2.0 checkstyle is clean:
https://commons.apache.org/proper/commons-configuration/checkstyle.html
- Have the checkstyle default rules changed between the checkstyle version
used in 2.0 and now?
- Have the checkstyle custom rules we use changed between the checkstyle
version used in 2.0 and now?
- The code could be fixed to match the rules of course.
Gary
> Oliver
>
> >
> > Regards
> > Dennis
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Oliver Heger <ol...@oliver-heger.de>.
Am 01.08.2016 um 11:04 schrieb Dennis Kieselhorst:
> Hi Benedikt!
>
>> The build log is here [1]. It looks like some generated classes are checked
>> by checkstyle which causes the build to fail. The build works with Java 7
>> and Java 8. So my vote again is -1 because I think mvn clean install should
>> work with the minimum required JDK out of the box. Sorry.
>>
> That's strange, I don't see why it should behave differently. Anyway
> I've added an exclude for it (this was already done for rat and clirr).
> This time I installed the same versions you used to build it, so next
> time it should be successful. Sorry for being lazy last time...
Many thanks, Dennis.
I see the checkstyle plugin has a failOnViolation flag which is *true*
per default. Should we set it to *false* (this would be my preference).
I will leave the vote open for now. To make it clear: There is no
problem with the artifacts, they are fully compatible with Java 1.6.
There is only an issue when building with 1.6 which should not affect
many users.
However, I am skeptical whether this vote will pass.
Oliver
>
> Regards
> Dennis
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Sergio Fernández <wi...@apache.org>.
+1 (non-binding)
So far I've checked: signatures and digests, source releases file layouts,
matched svn commit id, NOTICE
and LICENSE files, license headers, build sources in a clean environment
(Maven 3.3.9, OpenJDK 1.8.0_91 64-Bit, Debian amd64).
On Mon, Aug 1, 2016 at 11:04 AM, Dennis Kieselhorst <de...@apache.org> wrote:
> Hi Benedikt!
>
> > The build log is here [1]. It looks like some generated classes are
> checked
> > by checkstyle which causes the build to fail. The build works with Java 7
> > and Java 8. So my vote again is -1 because I think mvn clean install
> should
> > work with the minimum required JDK out of the box. Sorry.
> >
> That's strange, I don't see why it should behave differently. Anyway
> I've added an exclude for it (this was already done for rat and clirr).
> This time I installed the same versions you used to build it, so next
> time it should be successful. Sorry for being lazy last time...
>
> Regards
> Dennis
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Dennis Kieselhorst <de...@apache.org>.
Hi Benedikt!
> The build log is here [1]. It looks like some generated classes are checked
> by checkstyle which causes the build to fail. The build works with Java 7
> and Java 8. So my vote again is -1 because I think mvn clean install should
> work with the minimum required JDK out of the box. Sorry.
>
That's strange, I don't see why it should behave differently. Anyway
I've added an exclude for it (this was already done for rat and clirr).
This time I installed the same versions you used to build it, so next
time it should be successful. Sorry for being lazy last time...
Regards
Dennis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Benedikt Ritter <br...@apache.org>.
Hello Oliver,
mvn clean install still fails when building with:
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-14T18:29:23+01:00)
Maven home: /usr/local/Cellar/maven/3.2.5/libexec
Java version: 1.6.0_65, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: de_DE, platform encoding: MacRoman
OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
The build log is here [1]. It looks like some generated classes are checked
by checkstyle which causes the build to fail. The build works with Java 7
and Java 8. So my vote again is -1 because I think mvn clean install should
work with the minimum required JDK out of the box. Sorry.
Benedikt
[1] https://paste.apache.org/AkwU
Oliver Heger <ol...@oliver-heger.de> schrieb am Sa., 30. Juli 2016
um 22:03 Uhr:
> Hi all,
>
> after the failed vote for RC1 a new RC has been created. The only
> difference is that the checkstyle plugin has been downgraded which
> should allow building the project on Java 1.6.
>
> Configuration 2.1 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/configuration
> (revision 14582)
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1194/
>
> Details of changes since 2.0 are in the release notes:
>
>
> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
>
> https://home.apache.org/~oheger/configuration-2.1-rc2/changes-report.html
>
> Here is the tag:
>
>
> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC2
> (revision 1754628)
>
> Site:
> https://home.apache.org/~oheger/configuration-2.1-rc2/
> (note some links in the menu are not yet working)
>
> KEYS:
> http://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 2000
> GMT 02-Aug-2016
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
> Thanks!
> Oliver
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [VOTE] Release Configuration 2.1 based on RC2
Posted by Dennis Kieselhorst <de...@apache.org>.
+1
Am 30.07.2016 um 22:02 schrieb Oliver Heger:
> Hi all,
>
> after the failed vote for RC1 a new RC has been created. The only
> difference is that the checkstyle plugin has been downgraded which
> should allow building the project on Java 1.6.
>
> Configuration 2.1 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/configuration
> (revision 14582)
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1194/
>
> Details of changes since 2.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/configuration/RELEASE-NOTES.txt
>
> https://home.apache.org/~oheger/configuration-2.1-rc2/changes-report.html
>
> Here is the tag:
>
> http://svn.apache.org/repos/asf/commons/proper/configuration/tags/CONFIGURATION_2_1_RC2
> (revision 1754628)
>
> Site:
> https://home.apache.org/~oheger/configuration-2.1-rc2/
> (note some links in the menu are not yet working)
>
> KEYS:
> http://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 2000
> GMT 02-Aug-2016
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
> Thanks!
> Oliver
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org