Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Jörg Schaible
Hi Sebb, sebb wrote: > On 26 October 2016 at 17:50, Jörg Schaible wrote: [snip] >> We have commons-build in proper. Don't know what it is used for, but it >> looks like an old Maven 1 project ;-) > > Commons-build is current. > It is even documented. See: > > http://commons.apache.org/proper

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

2016-10-26 Thread Romain Manni-Bucau
2016-10-26 21:55 GMT+02:00 Gary Gregory : > Why not make the component require Java 7 and be done with it? > > no objection from my side > Gary > > On Wed, Oct 26, 2016 at 12:46 PM, Romain Manni-Bucau < > rmannibu...@gmail.com> > wrote: > > > 2016-10-26 21:35 GMT+02:00 Benedikt Ritter : > > > >

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

2016-10-26 Thread Gary Gregory
Why not make the component require Java 7 and be done with it? Gary On Wed, Oct 26, 2016 at 12:46 PM, Romain Manni-Bucau wrote: > 2016-10-26 21:35 GMT+02:00 Benedikt Ritter : > > > Hello Thomas, > > > > Thomas Vandahl schrieb am Fr., 21. Okt. 2016 um 19:42 > Uhr: > > > > > I would like to beta

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

2016-10-26 Thread Romain Manni-Bucau
2016-10-26 21:35 GMT+02:00 Benedikt Ritter : > Hello Thomas, > > Thomas Vandahl schrieb am Fr., 21. Okt. 2016 um 19:42 Uhr: > > > I would like to beta-release the [jcs] component. > > > > Apache Commons JCS 2.0-beta-2 RC1 is available for review at: > > https://dist.apache.org/repos/dist/dev/co

Re: commons-csv git commit: [CSV-201] Do not use RuntimeException in CSVParser.iterator().new Iterator() {...}.getNextRecord(). Use an IllegalStateException instead (KISS for now, no need for a custom

2016-10-26 Thread Benedikt Ritter
Hello, schrieb am Di., 25. Okt. 2016 um 22:59 Uhr: > Repository: commons-csv > Updated Branches: > refs/heads/master b2a50d4a3 -> 1c7a9910b > > > [CSV-201] Do not use RuntimeException in CSVParser.iterator().new > Iterator() {...}.getNextRecord(). Use an IllegalStateException instead > (KISS f

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

2016-10-26 Thread Benedikt Ritter
Hello Thomas, Thomas Vandahl schrieb am Fr., 21. Okt. 2016 um 19:42 Uhr: > I would like to beta-release the [jcs] component. > > Apache Commons JCS 2.0-beta-2 RC1 is available for review at: > https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16621). > > Maven artifacts are at: > https:/

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

2016-10-26 Thread Thomas Vandahl
Am 25.10.2016 um 21:38 schrieb Oliver Heger : > when building on Windows 10 with Java 1.6 I get the error below. The > build with Java 1.8 is successful. > > On the distributions, I found some problems: > - Both the source and the binary distribution deflate in the same > folder. Typically, differ

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

2016-10-26 Thread Thomas Vandahl
> Am 26.10.2016 um 00:19 schrieb sebb : > Reminder: releases cannot be vetoed [1] > They pass if there are at least 3 +1 and more +1 than -1. > You're technically right, however -1 votes tend to keep others from voting. We could need your vote, too. > However I have just noticed that the dist

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

2016-10-26 Thread Benedikt Ritter
Hello Thomas, Thomas Vandahl schrieb am Di., 25. Okt. 2016 um 21:06 Uhr: > Hi Benedikt, > > On 24.10.16 08:34, Benedikt Ritter wrote: > > Sorry, if that has been decided, I must have missed it. I'll take another > > look tonight. > > Could you please reconsider your vote? I fixed the check sums

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC1

2016-10-26 Thread Benedikt Ritter
Hello Sebastian, sebb schrieb am Mi., 26. Okt. 2016 um 00:25 Uhr: > On 25 October 2016 at 20:06, Thomas Vandahl wrote: > > Hi Benedikt, > > > > On 24.10.16 08:34, Benedikt Ritter wrote: > >> Sorry, if that has been decided, I must have missed it. I'll take > another > >> look tonight. > > > > C

Re: [complex] commons-complex module

2016-10-26 Thread Benedikt Ritter
dbrosIus schrieb am Di., 25. Okt. 2016 um 18:26 Uhr: > I think we should let the people doing the work, decide. > I agree with David. Apache is a Do-ocracy. Nevertheless I think we should focus on finishing the first release of RNG instead of starting of the next component. we already have som

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread sebb
On 26 October 2016 at 17:50, Jörg Schaible wrote: > Artem Barger wrote: > >> On Wed, Oct 26, 2016 at 7:14 PM, Gilles >> wrote: >> >>> could not find "commons-rng-build-tools" (posted a question in maven ML > list). > The reactor of Maven does not consider plugins itself or depen

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Artem Barger
On Wed, Oct 26, 2016 at 7:42 PM, Gilles wrote: > > But the modules link are still dead. > [E.g. there is no "apidocs".] ​Added aggregation of javadocs for parent project.​ Best regards, Artem Barger.

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Jörg Schaible
Artem Barger wrote: > On Wed, Oct 26, 2016 at 7:14 PM, Gilles > wrote: > >> could not find "commons-rng-build-tools" (posted a question in maven ML list). >>> >>> The reactor of Maven does not consider plugins itself or dependencies to >>> plugins for its build order (by design). To su

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Jörg Schaible
Artem Barger wrote: > On Wed, Oct 26, 2016 at 6:30 PM, Jörg Schaible < > joerg.schai...@bpm-inspire.com> wrote: > >> >> The reactor of Maven does not consider plugins itself or dependencies to >> plugins for its build order (by design). To support something like this, >> you >> will have to produ

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Gilles
On Wed, 26 Oct 2016 19:31:18 +0300, Artem Barger wrote: On Wed, Oct 26, 2016 at 7:14 PM, Gilles wrote: ​Try "mvn install site" That works but does not build the complete site, for which I'd invoke $ mvn site:stage ​Can you try now? I've pushed some changes.​ $ mvn clean install sit

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Artem Barger
On Wed, Oct 26, 2016 at 7:14 PM, Gilles wrote: > ​Try "mvn install site" >>> >> > That works but does not build the complete site, for which I'd > invoke > > $ mvn site:stage ​Can you try now? I've pushed some changes.​ Best regards, Artem Barger.

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Artem Barger
On Wed, Oct 26, 2016 at 7:14 PM, Gilles wrote: > could not find "commons-rng-build-tools" (posted a question in maven ML >>> list). >>> >> >> The reactor of Maven does not consider plugins itself or dependencies to >> plugins for its build order (by design). To support something like this, >> you

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Gilles
On Wed, 26 Oct 2016 17:30:45 +0200, Jörg Schaible wrote: Hi Artem, Artem Barger wrote: ​Hi, On Wed, Oct 26, 2016 at 5:53 PM, Gilles wrote: What is the command to "build everything"? I tried $ mvn site ​Try "mvn install site" That works but does not build the complete site, for

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Artem Barger
On Wed, Oct 26, 2016 at 6:30 PM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wrote: > > The reactor of Maven does not consider plugins itself or dependencies to > plugins for its build order (by design). To support something like this, > you > will have to produce a released artifact first.

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Jörg Schaible
Hi Artem, Artem Barger wrote: > ​Hi, > > On Wed, Oct 26, 2016 at 5:53 PM, Gilles > wrote: > >> What is the command to "build everything"? >> >> > >> I tried >> $ mvn site >> > > ​Try "mvn install site" > ​ instead. For some reason dependencies between is not sorted out and > maven > could

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Artem Barger
​Hi, ​ On Wed, Oct 26, 2016 at 5:53 PM, Gilles wrote: > What is the command to "build everything"? > > > I tried > $ mvn site > ​Try "mvn install site" ​ instead. For some reason dependencies between is not sorted out and maven could not find "commons-rng-build-tools" (posted a question in

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Gilles
Hello. On Wed, 26 Oct 2016 03:14:59 +0300, Artem Barger wrote: Hi, While working on creating multi module configuration for commons-rng component I've extracted all configurations for maven plugins such as: pmd, findbugs, checkstyle into separate module "commons-rng-build-tools". Such that pa

Re: [complex] commons-complex module

2016-10-26 Thread Gilles
Hi Eric. On Wed, 26 Oct 2016 14:48:17 +0200, Eric Barnhill wrote: On Wed, Oct 26, 2016 at 2:25 PM, Gilles wrote: It sounds like you can create your new component on top of math4, correct? Would you rather reply to the technical arguments put forward in the preceding paragraph? I've al

Re: [complex] commons-complex module

2016-10-26 Thread Eric Barnhill
On Wed, Oct 26, 2016 at 2:25 PM, Gilles wrote: > >> It sounds like you can create your new component on top of math4, correct? >> > > Would you rather reply to the technical arguments put forward in the > preceding paragraph? > > I've already answered your question many times (see the archive). >

Re: [complex] commons-complex module

2016-10-26 Thread Gilles
On Tue, 25 Oct 2016 15:00:55 -0700, Gary Gregory wrote: On Tue, Oct 25, 2016 at 12:07 PM, Eric Barnhill wrote: On Tue, Oct 25, 2016 at 7:32 PM, Gary Gregory wrote: > > I am against this constant spinning out. > > Gary > > The proposed commons-filter is not a spin out. There was one filter

Re: [complex] commons-complex module

2016-10-26 Thread Gilles
Hi Gary. On Tue, 25 Oct 2016 14:59:27 -0700, Gary Gregory wrote: I am against spinning out org.apache.commons.math4.complex out into yet another component. The argument that Gilles refuses to support org.apache.commons.math4.complex because he does not want to support all of org.apache.commons.

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Artem Barger
On Wed, Oct 26, 2016 at 10:36 AM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wrote: > Because you must have a mechanism to trigger the e.g. the PMD plugin > individually, if you put the declarationsof it into the commons parent > (pluginManagement as well as report). > > ​Ok, I see, I didn't

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Jörg Schaible
Hi Artem, Artem Barger wrote: > On Wed, Oct 26, 2016 at 10:08 AM, Jörg Schaible < > joerg.schai...@bpm-inspire.com> wrote: > >> You may put both parts into an own profile that is activated >> automatically at the extistence of pmd/pmd-ruleset.xml. Each component >> has then a chance to use it or

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Artem Barger
On Wed, Oct 26, 2016 at 10:08 AM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wrote: > You may put both parts into an own profile that is activated automatically > at the extistence of pmd/pmd-ruleset.xml. Each component has then a chance > to use it or not simply by providing that file. > ​N

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Artem Barger
On Wed, Oct 26, 2016 at 3:20 AM, sebb wrote: > Why not include it in commons parent? > Because than it will introduce cyclic dependencies I guess. You will declare "commons-parent" is parent module and later add it as dependency for maven plugin config.​ Best regards, Art

Re: [ALL] Maven plugins common configuration.

2016-10-26 Thread Jörg Schaible
Artem Barger wrote: > Hi, > > While working on creating multi module configuration for commons-rng > component I've extracted all configurations for maven plugins such as: > pmd, findbugs, checkstyle into separate module "commons-rng-build-tools". > Such that parent project can now refer to it wi