Re: [LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Rob Tompkins 
No apologies needed. You’ve been with me on all of these [parent] RCs. And it’s 
not like I’ve been mistake free. 

Thanks :-)

> On Apr 12, 2018, at 6:10 PM, Gary Gregory  wrote:
> 
> I apologize for my mistake here. All is well.
> 
> +1
> 
> Gary
> 
> 
> On Thu, Apr 12, 2018 at 3:52 PM, Gary Gregory 
> wrote:
> 
>> Oops. Testing again with 46...
>> 
>> On Thu, Apr 12, 2018 at 3:52 PM, Gary Gregory 
>> wrote:
>> 
>>> This is how I am testing [collections]:
>>> 
>>> C:\vcs\git\apache\commons\commons-collections>git diff
>>> diff --git a/pom.xml b/pom.xml
>>> index 8cf51948..bc8c446b 100644
>>> --- a/pom.xml
>>> +++ b/pom.xml
>>> @@ -19,7 +19,7 @@
>>>   
>>> org.apache.commons
>>> commons-parent
>>> -43
>>> +46-SNAPSHOT
>>>   
>>>   4.0.0
>>>   commons-collections4
>>> 
>>> C:\vcs\git\apache\commons\commons-collections>mvn -version
>>> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
>>> 2018-02-24T12:49:05-07:00)
>>> Maven home: C:\Java\apache-maven-3.5.3\bin\..
>>> Java version: 1.8.0_162, vendor: Oracle Corporation
>>> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>> 
>>> You?
>>> 
>>> Gary
>>> 
>>> On Thu, Apr 12, 2018 at 11:30 AM, Rob Tompkins 
>>> wrote:
>>> 
 That’s curious. My “mvn clean site" builds successfully with RC3 on
 [collections].
 
> On Apr 12, 2018, at 1:21 PM, Gary Gregory 
 wrote:
> 
> Hi Rob,
> Thank you for preparing this RC.
> 
> Did you try to build Commons Collection with this parent POM?
> 
> Running 'mvn clean site' give me:
> 
> [INFO] Generating "japicmp" report   ---
> japicmp-maven-plugin:0.11.1:cmp-report
> [debug] No packaging support defined, no filtering
> [debug] Searching for versions in versionRange: (,4.2-SNAPSHOT)
> [info] Unable to find a previous version of the project in the
 repository.
> [info] No new version specified and artifact is not a file
> (C:\vcs\git\apache\commons\commons-collections\target\classes).
> [INFO]
> 
 
> [INFO] BUILD FAILURE
> [INFO]
> 
 
> [INFO] Total time: 03:37 min
> [INFO] Finished at: 2018-04-12T11:17:22-06:00
> [INFO]
> 
 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
> project commons-collections4: Error generating
> japicmp-maven-plugin:0.11.1:cmp-report report: Failed to generate
 report:
> Please provide at least one resolvable old version using one of the
> configuration elements  or . -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecuti
 onException
> 
> Should we change something in the Commons Collection POM to make
 proper use
> of japicmp?
> 
> Aside from that: ASC, MD5, SHA1 OK.
> Apache RAT check OK.
> The commons-parent site tries to generate a japicmp report which fails
 as
> you have documented.
> 
> Gary
> 
> On Thu, Apr 12, 2018 at 9:44 AM, Rob Tompkins 
 wrote:
> 
>> Hello all,
>> 
>> 
>> This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from
 RC3).
>> 
>> 
>> Note on validation:
>>  Please read the
>> https://dist.apache.org/repos/dist/dev/commons/commons-
>> parent/RELEASE-NOTES.txt,
>> as there is an erroneous non-failing stack trace that occurs during
 the
>> build.
>> Specifically:
>> 
>> [debug] No packaging support defined, no filtering
>> [info] Skipping execution because packaging of this module is 'pom'.
>> [debug] Searching for versions in versionRange: (,46)
>> [info] Unable to find a previous version of the project in the
 repository.
>> [warn] No new version specified and file
 '//commons-parent/pom.xml' of
>> artifact could not be opened as jar archive: error in opening zip file
>> 
>> java.util.zip.ZipException: error in opening zip file
>>   at java.util.zip.ZipFile.open(Native Method)
>>   at java.util.zip.ZipFile.(ZipFile.java:225)
>>   at java.util.zip.ZipFile.(ZipFile.java:155)
>>   at

Re: [LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Gary Gregory 
I apologize for my mistake here. All is well.

+1

Gary


On Thu, Apr 12, 2018 at 3:52 PM, Gary Gregory 
wrote:

> Oops. Testing again with 46...
>
> On Thu, Apr 12, 2018 at 3:52 PM, Gary Gregory 
> wrote:
>
>> This is how I am testing [collections]:
>>
>> C:\vcs\git\apache\commons\commons-collections>git diff
>> diff --git a/pom.xml b/pom.xml
>> index 8cf51948..bc8c446b 100644
>> --- a/pom.xml
>> +++ b/pom.xml
>> @@ -19,7 +19,7 @@
>>
>>  org.apache.commons
>>  commons-parent
>> -43
>> +46-SNAPSHOT
>>
>>4.0.0
>>commons-collections4
>>
>> C:\vcs\git\apache\commons\commons-collections>mvn -version
>> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
>> 2018-02-24T12:49:05-07:00)
>> Maven home: C:\Java\apache-maven-3.5.3\bin\..
>> Java version: 1.8.0_162, vendor: Oracle Corporation
>> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
>> Default locale: en_US, platform encoding: Cp1252
>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>
>> You?
>>
>> Gary
>>
>> On Thu, Apr 12, 2018 at 11:30 AM, Rob Tompkins 
>> wrote:
>>
>>> That’s curious. My “mvn clean site" builds successfully with RC3 on
>>> [collections].
>>>
>>> > On Apr 12, 2018, at 1:21 PM, Gary Gregory 
>>> wrote:
>>> >
>>> > Hi Rob,
>>> > Thank you for preparing this RC.
>>> >
>>> > Did you try to build Commons Collection with this parent POM?
>>> >
>>> > Running 'mvn clean site' give me:
>>> >
>>> > [INFO] Generating "japicmp" report   ---
>>> > japicmp-maven-plugin:0.11.1:cmp-report
>>> > [debug] No packaging support defined, no filtering
>>> > [debug] Searching for versions in versionRange: (,4.2-SNAPSHOT)
>>> > [info] Unable to find a previous version of the project in the
>>> repository.
>>> > [info] No new version specified and artifact is not a file
>>> > (C:\vcs\git\apache\commons\commons-collections\target\classes).
>>> > [INFO]
>>> > 
>>> 
>>> > [INFO] BUILD FAILURE
>>> > [INFO]
>>> > 
>>> 
>>> > [INFO] Total time: 03:37 min
>>> > [INFO] Finished at: 2018-04-12T11:17:22-06:00
>>> > [INFO]
>>> > 
>>> 
>>> > [ERROR] Failed to execute goal
>>> > org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
>>> > project commons-collections4: Error generating
>>> > japicmp-maven-plugin:0.11.1:cmp-report report: Failed to generate
>>> report:
>>> > Please provide at least one resolvable old version using one of the
>>> > configuration elements  or . -> [Help 1]
>>> > [ERROR]
>>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>>> the -e
>>> > switch.
>>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> > [ERROR]
>>> > [ERROR] For more information about the errors and possible solutions,
>>> > please read the following articles:
>>> > [ERROR] [Help 1]
>>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecuti
>>> onException
>>> >
>>> > Should we change something in the Commons Collection POM to make
>>> proper use
>>> > of japicmp?
>>> >
>>> > Aside from that: ASC, MD5, SHA1 OK.
>>> > Apache RAT check OK.
>>> > The commons-parent site tries to generate a japicmp report which fails
>>> as
>>> > you have documented.
>>> >
>>> > Gary
>>> >
>>> > On Thu, Apr 12, 2018 at 9:44 AM, Rob Tompkins 
>>> wrote:
>>> >
>>> >> Hello all,
>>> >>
>>> >>
>>> >> This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from
>>> RC3).
>>> >>
>>> >>
>>> >> Note on validation:
>>> >>   Please read the
>>> >> https://dist.apache.org/repos/dist/dev/commons/commons-
>>> >> parent/RELEASE-NOTES.txt,
>>> >> as there is an erroneous non-failing stack trace that occurs during
>>> the
>>> >> build.
>>> >> Specifically:
>>> >>
>>> >> [debug] No packaging support defined, no filtering
>>> >> [info] Skipping execution because packaging of this module is 'pom'.
>>> >> [debug] Searching for versions in versionRange: (,46)
>>> >> [info] Unable to find a previous version of the project in the
>>> repository.
>>> >> [warn] No new version specified and file
>>> '//commons-parent/pom.xml' of
>>> >> artifact could not be opened as jar archive: error in opening zip file
>>> >>
>>> >> java.util.zip.ZipException: error in opening zip file
>>> >>at java.util.zip.ZipFile.open(Native Method)
>>> >>at java.util.zip.ZipFile.(ZipFile.java:225)
>>> >>at java.util.zip.ZipFile.(ZipFile.java:155)
>>> >>at java.util.jar.JarFile.(JarFile.java:166)
>>> >>at java.util.jar.JarFile.(JarFile.java:130)
>>> >>at japicmp.maven.JApiCmpMojo.populateArchivesListsFromParam
>>> >> eters(JApiCmpMojo.java:345)
>>> >>at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:708)
>>> >>

Re: [LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Gary Gregory 
This is how I am testing [collections]:

C:\vcs\git\apache\commons\commons-collections>git diff
diff --git a/pom.xml b/pom.xml
index 8cf51948..bc8c446b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -19,7 +19,7 @@
   
 org.apache.commons
 commons-parent
-43
+46-SNAPSHOT
   
   4.0.0
   commons-collections4

C:\vcs\git\apache\commons\commons-collections>mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T12:49:05-07:00)
Maven home: C:\Java\apache-maven-3.5.3\bin\..
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_162\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

You?

Gary

On Thu, Apr 12, 2018 at 11:30 AM, Rob Tompkins  wrote:

> That’s curious. My “mvn clean site" builds successfully with RC3 on
> [collections].
>
> > On Apr 12, 2018, at 1:21 PM, Gary Gregory 
> wrote:
> >
> > Hi Rob,
> > Thank you for preparing this RC.
> >
> > Did you try to build Commons Collection with this parent POM?
> >
> > Running 'mvn clean site' give me:
> >
> > [INFO] Generating "japicmp" report   ---
> > japicmp-maven-plugin:0.11.1:cmp-report
> > [debug] No packaging support defined, no filtering
> > [debug] Searching for versions in versionRange: (,4.2-SNAPSHOT)
> > [info] Unable to find a previous version of the project in the
> repository.
> > [info] No new version specified and artifact is not a file
> > (C:\vcs\git\apache\commons\commons-collections\target\classes).
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Total time: 03:37 min
> > [INFO] Finished at: 2018-04-12T11:17:22-06:00
> > [INFO]
> > 
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
> > project commons-collections4: Error generating
> > japicmp-maven-plugin:0.11.1:cmp-report report: Failed to generate
> report:
> > Please provide at least one resolvable old version using one of the
> > configuration elements  or . -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >
> > Should we change something in the Commons Collection POM to make proper
> use
> > of japicmp?
> >
> > Aside from that: ASC, MD5, SHA1 OK.
> > Apache RAT check OK.
> > The commons-parent site tries to generate a japicmp report which fails as
> > you have documented.
> >
> > Gary
> >
> > On Thu, Apr 12, 2018 at 9:44 AM, Rob Tompkins 
> wrote:
> >
> >> Hello all,
> >>
> >>
> >> This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from
> RC3).
> >>
> >>
> >> Note on validation:
> >>   Please read the
> >> https://dist.apache.org/repos/dist/dev/commons/commons-
> >> parent/RELEASE-NOTES.txt,
> >> as there is an erroneous non-failing stack trace that occurs during the
> >> build.
> >> Specifically:
> >>
> >> [debug] No packaging support defined, no filtering
> >> [info] Skipping execution because packaging of this module is 'pom'.
> >> [debug] Searching for versions in versionRange: (,46)
> >> [info] Unable to find a previous version of the project in the
> repository.
> >> [warn] No new version specified and file '//commons-parent/pom.xml'
> of
> >> artifact could not be opened as jar archive: error in opening zip file
> >>
> >> java.util.zip.ZipException: error in opening zip file
> >>at java.util.zip.ZipFile.open(Native Method)
> >>at java.util.zip.ZipFile.(ZipFile.java:225)
> >>at java.util.zip.ZipFile.(ZipFile.java:155)
> >>at java.util.jar.JarFile.(JarFile.java:166)
> >>at java.util.jar.JarFile.(JarFile.java:130)
> >>at japicmp.maven.JApiCmpMojo.populateArchivesListsFromParam
> >> eters(JApiCmpMojo.java:345)
> >>at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:708)
> >>at japicmp.maven.JApiCmpReport.getOptions(JApiCmpReport.java:
> 108)
> >>at japicmp.maven.JApiCmpReport.getDescription(JApiCmpReport.
> >> java:127)
> >>at org.apache.maven.plugins.site.render.
> >> CategorySummaryDocumentRenderer.renderDocument(
> >> CategorySummaryDocumentRenderer.java:155)
> >>
> >>
> >> Tag name:
> >>   commons-parent-46-RC3
> >>
> >>
> >> Tag URL:
> >>   https://svn.apache.org/repos/asf/commons/proper/commons-
> >> parent/tags/commons-parent-46-RC3/
> >>
> >>
> >> Commit ID the tag points at:
> >>1828984
> >>
> >>
> >>

Re: [LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Gary Gregory 
Oops. Testing again with 46...

On Thu, Apr 12, 2018 at 3:52 PM, Gary Gregory 
wrote:

> This is how I am testing [collections]:
>
> C:\vcs\git\apache\commons\commons-collections>git diff
> diff --git a/pom.xml b/pom.xml
> index 8cf51948..bc8c446b 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -19,7 +19,7 @@
>
>  org.apache.commons
>  commons-parent
> -43
> +46-SNAPSHOT
>
>4.0.0
>commons-collections4
>
> C:\vcs\git\apache\commons\commons-collections>mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> You?
>
> Gary
>
> On Thu, Apr 12, 2018 at 11:30 AM, Rob Tompkins  wrote:
>
>> That’s curious. My “mvn clean site" builds successfully with RC3 on
>> [collections].
>>
>> > On Apr 12, 2018, at 1:21 PM, Gary Gregory 
>> wrote:
>> >
>> > Hi Rob,
>> > Thank you for preparing this RC.
>> >
>> > Did you try to build Commons Collection with this parent POM?
>> >
>> > Running 'mvn clean site' give me:
>> >
>> > [INFO] Generating "japicmp" report   ---
>> > japicmp-maven-plugin:0.11.1:cmp-report
>> > [debug] No packaging support defined, no filtering
>> > [debug] Searching for versions in versionRange: (,4.2-SNAPSHOT)
>> > [info] Unable to find a previous version of the project in the
>> repository.
>> > [info] No new version specified and artifact is not a file
>> > (C:\vcs\git\apache\commons\commons-collections\target\classes).
>> > [INFO]
>> > 
>> 
>> > [INFO] BUILD FAILURE
>> > [INFO]
>> > 
>> 
>> > [INFO] Total time: 03:37 min
>> > [INFO] Finished at: 2018-04-12T11:17:22-06:00
>> > [INFO]
>> > 
>> 
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
>> > project commons-collections4: Error generating
>> > japicmp-maven-plugin:0.11.1:cmp-report report: Failed to generate
>> report:
>> > Please provide at least one resolvable old version using one of the
>> > configuration elements  or . -> [Help 1]
>> > [ERROR]
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e
>> > switch.
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> > [ERROR]
>> > [ERROR] For more information about the errors and possible solutions,
>> > please read the following articles:
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> >
>> > Should we change something in the Commons Collection POM to make proper
>> use
>> > of japicmp?
>> >
>> > Aside from that: ASC, MD5, SHA1 OK.
>> > Apache RAT check OK.
>> > The commons-parent site tries to generate a japicmp report which fails
>> as
>> > you have documented.
>> >
>> > Gary
>> >
>> > On Thu, Apr 12, 2018 at 9:44 AM, Rob Tompkins 
>> wrote:
>> >
>> >> Hello all,
>> >>
>> >>
>> >> This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from
>> RC3).
>> >>
>> >>
>> >> Note on validation:
>> >>   Please read the
>> >> https://dist.apache.org/repos/dist/dev/commons/commons-
>> >> parent/RELEASE-NOTES.txt,
>> >> as there is an erroneous non-failing stack trace that occurs during the
>> >> build.
>> >> Specifically:
>> >>
>> >> [debug] No packaging support defined, no filtering
>> >> [info] Skipping execution because packaging of this module is 'pom'.
>> >> [debug] Searching for versions in versionRange: (,46)
>> >> [info] Unable to find a previous version of the project in the
>> repository.
>> >> [warn] No new version specified and file
>> '//commons-parent/pom.xml' of
>> >> artifact could not be opened as jar archive: error in opening zip file
>> >>
>> >> java.util.zip.ZipException: error in opening zip file
>> >>at java.util.zip.ZipFile.open(Native Method)
>> >>at java.util.zip.ZipFile.(ZipFile.java:225)
>> >>at java.util.zip.ZipFile.(ZipFile.java:155)
>> >>at java.util.jar.JarFile.(JarFile.java:166)
>> >>at java.util.jar.JarFile.(JarFile.java:130)
>> >>at japicmp.maven.JApiCmpMojo.populateArchivesListsFromParam
>> >> eters(JApiCmpMojo.java:345)
>> >>at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:708)
>> >>at japicmp.maven.JApiCmpReport.getOptions(JApiCmpReport.java:10
>> 8)
>> >>at japicmp.maven.JApiCmpReport.getDescription(JApiCmpReport.
>> >> java:127)
>> >>at org.apache.maven.plugins.site.render.
>> >> CategorySummaryDocumentRenderer.renderDocument(
>> >>

Re: [LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Gary Gregory 
I am AFK for about 90 mins...

On Thu, Apr 12, 2018, 11:30 Rob Tompkins  wrote:

> That’s curious. My “mvn clean site" builds successfully with RC3 on
> [collections].
>
> > On Apr 12, 2018, at 1:21 PM, Gary Gregory 
> wrote:
> >
> > Hi Rob,
> > Thank you for preparing this RC.
> >
> > Did you try to build Commons Collection with this parent POM?
> >
> > Running 'mvn clean site' give me:
> >
> > [INFO] Generating "japicmp" report   ---
> > japicmp-maven-plugin:0.11.1:cmp-report
> > [debug] No packaging support defined, no filtering
> > [debug] Searching for versions in versionRange: (,4.2-SNAPSHOT)
> > [info] Unable to find a previous version of the project in the
> repository.
> > [info] No new version specified and artifact is not a file
> > (C:\vcs\git\apache\commons\commons-collections\target\classes).
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Total time: 03:37 min
> > [INFO] Finished at: 2018-04-12T11:17:22-06:00
> > [INFO]
> > 
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
> > project commons-collections4: Error generating
> > japicmp-maven-plugin:0.11.1:cmp-report report: Failed to generate report:
> > Please provide at least one resolvable old version using one of the
> > configuration elements  or . -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >
> > Should we change something in the Commons Collection POM to make proper
> use
> > of japicmp?
> >
> > Aside from that: ASC, MD5, SHA1 OK.
> > Apache RAT check OK.
> > The commons-parent site tries to generate a japicmp report which fails as
> > you have documented.
> >
> > Gary
> >
> > On Thu, Apr 12, 2018 at 9:44 AM, Rob Tompkins 
> wrote:
> >
> >> Hello all,
> >>
> >>
> >> This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from
> RC3).
> >>
> >>
> >> Note on validation:
> >>   Please read the
> >> https://dist.apache.org/repos/dist/dev/commons/commons-
> >> parent/RELEASE-NOTES.txt,
> >> as there is an erroneous non-failing stack trace that occurs during the
> >> build.
> >> Specifically:
> >>
> >> [debug] No packaging support defined, no filtering
> >> [info] Skipping execution because packaging of this module is 'pom'.
> >> [debug] Searching for versions in versionRange: (,46)
> >> [info] Unable to find a previous version of the project in the
> repository.
> >> [warn] No new version specified and file '//commons-parent/pom.xml'
> of
> >> artifact could not be opened as jar archive: error in opening zip file
> >>
> >> java.util.zip.ZipException: error in opening zip file
> >>at java.util.zip.ZipFile.open(Native Method)
> >>at java.util.zip.ZipFile.(ZipFile.java:225)
> >>at java.util.zip.ZipFile.(ZipFile.java:155)
> >>at java.util.jar.JarFile.(JarFile.java:166)
> >>at java.util.jar.JarFile.(JarFile.java:130)
> >>at japicmp.maven.JApiCmpMojo.populateArchivesListsFromParam
> >> eters(JApiCmpMojo.java:345)
> >>at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:708)
> >>at japicmp.maven.JApiCmpReport.getOptions(JApiCmpReport.java:108)
> >>at japicmp.maven.JApiCmpReport.getDescription(JApiCmpReport.
> >> java:127)
> >>at org.apache.maven.plugins.site.render.
> >> CategorySummaryDocumentRenderer.renderDocument(
> >> CategorySummaryDocumentRenderer.java:155)
> >>
> >>
> >> Tag name:
> >>   commons-parent-46-RC3
> >>
> >>
> >> Tag URL:
> >>   https://svn.apache.org/repos/asf/commons/proper/commons-
> >> parent/tags/commons-parent-46-RC3/
> >>
> >>
> >> Commit ID the tag points at:
> >>1828984
> >>
> >>
> >> Site Zip:
> >>
> https://dist.apache.org/repos/dist/dev/commons/commons-parent/site.zip
> >>
> >>
> >> Distribution files (committed at revision 26309):
> >>   https://dist.apache.org/repos/dist/dev/commons/commons-parent/
> >>
> >>
> >> Distribution files hashes (SHA1):
> >>   commons-parent-46-src.tar.gz
> >>   (SHA1: dc6d7fe92c737a55679507e95a99b347234d8844)
> >>   commons-parent-46-src.zip
> >>   (SHA1: 34b4f78afc7d24efc94649286d7c9bfea9ceb83f)
> >>
> >>
> >> These are the Maven artifacts and their hashes:
> >>   commons-parent-46-site.xml
> >>   (SHA1: 02b3b54d26d97a72fd55b20d027040ca0daf52b7)
> >>   commons-parent-46.pom
> >>   (SHA1: 689b04f88f0cedd4c451686b19ad33eefb32a41f)
> >>
> >>
> >> KEYS file to check

Re: [LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Rob Tompkins 
That’s curious. My “mvn clean site" builds successfully with RC3 on 
[collections].

> On Apr 12, 2018, at 1:21 PM, Gary Gregory  wrote:
> 
> Hi Rob,
> Thank you for preparing this RC.
> 
> Did you try to build Commons Collection with this parent POM?
> 
> Running 'mvn clean site' give me:
> 
> [INFO] Generating "japicmp" report   ---
> japicmp-maven-plugin:0.11.1:cmp-report
> [debug] No packaging support defined, no filtering
> [debug] Searching for versions in versionRange: (,4.2-SNAPSHOT)
> [info] Unable to find a previous version of the project in the repository.
> [info] No new version specified and artifact is not a file
> (C:\vcs\git\apache\commons\commons-collections\target\classes).
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 03:37 min
> [INFO] Finished at: 2018-04-12T11:17:22-06:00
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
> project commons-collections4: Error generating
> japicmp-maven-plugin:0.11.1:cmp-report report: Failed to generate report:
> Please provide at least one resolvable old version using one of the
> configuration elements  or . -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 
> Should we change something in the Commons Collection POM to make proper use
> of japicmp?
> 
> Aside from that: ASC, MD5, SHA1 OK.
> Apache RAT check OK.
> The commons-parent site tries to generate a japicmp report which fails as
> you have documented.
> 
> Gary
> 
> On Thu, Apr 12, 2018 at 9:44 AM, Rob Tompkins  wrote:
> 
>> Hello all,
>> 
>> 
>> This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from RC3).
>> 
>> 
>> Note on validation:
>>   Please read the
>> https://dist.apache.org/repos/dist/dev/commons/commons-
>> parent/RELEASE-NOTES.txt,
>> as there is an erroneous non-failing stack trace that occurs during the
>> build.
>> Specifically:
>> 
>> [debug] No packaging support defined, no filtering
>> [info] Skipping execution because packaging of this module is 'pom'.
>> [debug] Searching for versions in versionRange: (,46)
>> [info] Unable to find a previous version of the project in the repository.
>> [warn] No new version specified and file '//commons-parent/pom.xml' of
>> artifact could not be opened as jar archive: error in opening zip file
>> 
>> java.util.zip.ZipException: error in opening zip file
>>at java.util.zip.ZipFile.open(Native Method)
>>at java.util.zip.ZipFile.(ZipFile.java:225)
>>at java.util.zip.ZipFile.(ZipFile.java:155)
>>at java.util.jar.JarFile.(JarFile.java:166)
>>at java.util.jar.JarFile.(JarFile.java:130)
>>at japicmp.maven.JApiCmpMojo.populateArchivesListsFromParam
>> eters(JApiCmpMojo.java:345)
>>at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:708)
>>at japicmp.maven.JApiCmpReport.getOptions(JApiCmpReport.java:108)
>>at japicmp.maven.JApiCmpReport.getDescription(JApiCmpReport.
>> java:127)
>>at org.apache.maven.plugins.site.render.
>> CategorySummaryDocumentRenderer.renderDocument(
>> CategorySummaryDocumentRenderer.java:155)
>> 
>> 
>> Tag name:
>>   commons-parent-46-RC3
>> 
>> 
>> Tag URL:
>>   https://svn.apache.org/repos/asf/commons/proper/commons-
>> parent/tags/commons-parent-46-RC3/
>> 
>> 
>> Commit ID the tag points at:
>>1828984
>> 
>> 
>> Site Zip:
>>   https://dist.apache.org/repos/dist/dev/commons/commons-parent/site.zip
>> 
>> 
>> Distribution files (committed at revision 26309):
>>   https://dist.apache.org/repos/dist/dev/commons/commons-parent/
>> 
>> 
>> Distribution files hashes (SHA1):
>>   commons-parent-46-src.tar.gz
>>   (SHA1: dc6d7fe92c737a55679507e95a99b347234d8844)
>>   commons-parent-46-src.zip
>>   (SHA1: 34b4f78afc7d24efc94649286d7c9bfea9ceb83f)
>> 
>> 
>> These are the Maven artifacts and their hashes:
>>   commons-parent-46-site.xml
>>   (SHA1: 02b3b54d26d97a72fd55b20d027040ca0daf52b7)
>>   commons-parent-46.pom
>>   (SHA1: 689b04f88f0cedd4c451686b19ad33eefb32a41f)
>> 
>> 
>> KEYS file to check signatures:
>>   http://www.apache.org/dist/commons/KEYS
>> 
>> 
>> Maven artifacts:
>>   https://repository.apache.org/content/repositories/
>> orgapachecommons-1325
>> 
>> 
>> Please select one of the following options[1]:
>>  [ ] +1 Release it.
>>  [ ] +0 Go ahead; I don't care.
>>  [ ] -0 There are a few minor glitches: ...
>>  [ ] -1 No,

Re: [LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Rob Tompkins 
Darn again :-) ….Looking now.

> On Apr 12, 2018, at 1:21 PM, Gary Gregory  wrote:
> 
> Hi Rob,
> Thank you for preparing this RC.
> 
> Did you try to build Commons Collection with this parent POM?
> 
> Running 'mvn clean site' give me:
> 
> [INFO] Generating "japicmp" report   ---
> japicmp-maven-plugin:0.11.1:cmp-report
> [debug] No packaging support defined, no filtering
> [debug] Searching for versions in versionRange: (,4.2-SNAPSHOT)
> [info] Unable to find a previous version of the project in the repository.
> [info] No new version specified and artifact is not a file
> (C:\vcs\git\apache\commons\commons-collections\target\classes).
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 03:37 min
> [INFO] Finished at: 2018-04-12T11:17:22-06:00
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
> project commons-collections4: Error generating
> japicmp-maven-plugin:0.11.1:cmp-report report: Failed to generate report:
> Please provide at least one resolvable old version using one of the
> configuration elements  or . -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 
> Should we change something in the Commons Collection POM to make proper use
> of japicmp?
> 
> Aside from that: ASC, MD5, SHA1 OK.
> Apache RAT check OK.
> The commons-parent site tries to generate a japicmp report which fails as
> you have documented.
> 
> Gary
> 
> On Thu, Apr 12, 2018 at 9:44 AM, Rob Tompkins  wrote:
> 
>> Hello all,
>> 
>> 
>> This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from RC3).
>> 
>> 
>> Note on validation:
>>   Please read the
>> https://dist.apache.org/repos/dist/dev/commons/commons-
>> parent/RELEASE-NOTES.txt,
>> as there is an erroneous non-failing stack trace that occurs during the
>> build.
>> Specifically:
>> 
>> [debug] No packaging support defined, no filtering
>> [info] Skipping execution because packaging of this module is 'pom'.
>> [debug] Searching for versions in versionRange: (,46)
>> [info] Unable to find a previous version of the project in the repository.
>> [warn] No new version specified and file '//commons-parent/pom.xml' of
>> artifact could not be opened as jar archive: error in opening zip file
>> 
>> java.util.zip.ZipException: error in opening zip file
>>at java.util.zip.ZipFile.open(Native Method)
>>at java.util.zip.ZipFile.(ZipFile.java:225)
>>at java.util.zip.ZipFile.(ZipFile.java:155)
>>at java.util.jar.JarFile.(JarFile.java:166)
>>at java.util.jar.JarFile.(JarFile.java:130)
>>at japicmp.maven.JApiCmpMojo.populateArchivesListsFromParam
>> eters(JApiCmpMojo.java:345)
>>at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:708)
>>at japicmp.maven.JApiCmpReport.getOptions(JApiCmpReport.java:108)
>>at japicmp.maven.JApiCmpReport.getDescription(JApiCmpReport.
>> java:127)
>>at org.apache.maven.plugins.site.render.
>> CategorySummaryDocumentRenderer.renderDocument(
>> CategorySummaryDocumentRenderer.java:155)
>> 
>> 
>> Tag name:
>>   commons-parent-46-RC3
>> 
>> 
>> Tag URL:
>>   https://svn.apache.org/repos/asf/commons/proper/commons-
>> parent/tags/commons-parent-46-RC3/
>> 
>> 
>> Commit ID the tag points at:
>>1828984
>> 
>> 
>> Site Zip:
>>   https://dist.apache.org/repos/dist/dev/commons/commons-parent/site.zip
>> 
>> 
>> Distribution files (committed at revision 26309):
>>   https://dist.apache.org/repos/dist/dev/commons/commons-parent/
>> 
>> 
>> Distribution files hashes (SHA1):
>>   commons-parent-46-src.tar.gz
>>   (SHA1: dc6d7fe92c737a55679507e95a99b347234d8844)
>>   commons-parent-46-src.zip
>>   (SHA1: 34b4f78afc7d24efc94649286d7c9bfea9ceb83f)
>> 
>> 
>> These are the Maven artifacts and their hashes:
>>   commons-parent-46-site.xml
>>   (SHA1: 02b3b54d26d97a72fd55b20d027040ca0daf52b7)
>>   commons-parent-46.pom
>>   (SHA1: 689b04f88f0cedd4c451686b19ad33eefb32a41f)
>> 
>> 
>> KEYS file to check signatures:
>>   http://www.apache.org/dist/commons/KEYS
>> 
>> 
>> Maven artifacts:
>>   https://repository.apache.org/content/repositories/
>> orgapachecommons-1325
>> 
>> 
>> Please select one of the following options[1]:
>>  [ ] +1 Release it.
>>  [ ] +0 Go ahead; I don't care.
>>  [ ] -0 There are a few minor glitches: ...
>>  [ ] -1 No, do not release it because ...
>> 
>> 
>> This vote

Re: [LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Gary Gregory 
Hi Rob,
Thank you for preparing this RC.

Did you try to build Commons Collection with this parent POM?

Running 'mvn clean site' give me:

[INFO] Generating "japicmp" report   ---
japicmp-maven-plugin:0.11.1:cmp-report
[debug] No packaging support defined, no filtering
[debug] Searching for versions in versionRange: (,4.2-SNAPSHOT)
[info] Unable to find a previous version of the project in the repository.
[info] No new version specified and artifact is not a file
(C:\vcs\git\apache\commons\commons-collections\target\classes).
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 03:37 min
[INFO] Finished at: 2018-04-12T11:17:22-06:00
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on
project commons-collections4: Error generating
japicmp-maven-plugin:0.11.1:cmp-report report: Failed to generate report:
Please provide at least one resolvable old version using one of the
configuration elements  or . -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Should we change something in the Commons Collection POM to make proper use
of japicmp?

Aside from that: ASC, MD5, SHA1 OK.
Apache RAT check OK.
The commons-parent site tries to generate a japicmp report which fails as
you have documented.

Gary

On Thu, Apr 12, 2018 at 9:44 AM, Rob Tompkins  wrote:

> Hello all,
>
>
> This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from RC3).
>
>
> Note on validation:
>Please read the
> https://dist.apache.org/repos/dist/dev/commons/commons-
> parent/RELEASE-NOTES.txt,
> as there is an erroneous non-failing stack trace that occurs during the
> build.
> Specifically:
>
> [debug] No packaging support defined, no filtering
> [info] Skipping execution because packaging of this module is 'pom'.
> [debug] Searching for versions in versionRange: (,46)
> [info] Unable to find a previous version of the project in the repository.
> [warn] No new version specified and file '//commons-parent/pom.xml' of
> artifact could not be opened as jar archive: error in opening zip file
>
> java.util.zip.ZipException: error in opening zip file
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.(ZipFile.java:225)
> at java.util.zip.ZipFile.(ZipFile.java:155)
> at java.util.jar.JarFile.(JarFile.java:166)
> at java.util.jar.JarFile.(JarFile.java:130)
> at japicmp.maven.JApiCmpMojo.populateArchivesListsFromParam
> eters(JApiCmpMojo.java:345)
> at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:708)
> at japicmp.maven.JApiCmpReport.getOptions(JApiCmpReport.java:108)
> at japicmp.maven.JApiCmpReport.getDescription(JApiCmpReport.
> java:127)
> at org.apache.maven.plugins.site.render.
> CategorySummaryDocumentRenderer.renderDocument(
> CategorySummaryDocumentRenderer.java:155)
>
>
> Tag name:
>commons-parent-46-RC3
>
>
> Tag URL:
>https://svn.apache.org/repos/asf/commons/proper/commons-
> parent/tags/commons-parent-46-RC3/
>
>
> Commit ID the tag points at:
> 1828984
>
>
> Site Zip:
>https://dist.apache.org/repos/dist/dev/commons/commons-parent/site.zip
>
>
> Distribution files (committed at revision 26309):
>https://dist.apache.org/repos/dist/dev/commons/commons-parent/
>
>
> Distribution files hashes (SHA1):
>commons-parent-46-src.tar.gz
>(SHA1: dc6d7fe92c737a55679507e95a99b347234d8844)
>commons-parent-46-src.zip
>(SHA1: 34b4f78afc7d24efc94649286d7c9bfea9ceb83f)
>
>
> These are the Maven artifacts and their hashes:
>commons-parent-46-site.xml
>(SHA1: 02b3b54d26d97a72fd55b20d027040ca0daf52b7)
>commons-parent-46.pom
>(SHA1: 689b04f88f0cedd4c451686b19ad33eefb32a41f)
>
>
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS
>
>
> Maven artifacts:
>https://repository.apache.org/content/repositories/
> orgapachecommons-1325
>
>
> Please select one of the following options[1]:
>   [ ] +1 Release it.
>   [ ] +0 Go ahead; I don't care.
>   [ ] -0 There are a few minor glitches: ...
>   [ ] -1 No, do not release it because ...
>
>
> This vote will be open at least 72 hours, i.e. until
> 2018-04-15T16:00:00Z
> (this is UTC time).
>
> 
>
>
> Cheers,
> -Rob
>
>
> [1] http://apache.org/foundation/voting.html
> -
> To unsubscribe, e-mail:

[LAZY][VOTE] Release Commons Parent 46 based on RC3

2018-04-12 Thread Rob Tompkins 
Hello all,


This is a [LAZY][VOTE] for releasing Apache Commons Parent 46 (from RC3).


Note on validation:
   Please read the
https://dist.apache.org/repos/dist/dev/commons/commons-parent/RELEASE-NOTES.txt,
as there is an erroneous non-failing stack trace that occurs during the build.
Specifically:

[debug] No packaging support defined, no filtering
[info] Skipping execution because packaging of this module is 'pom'.
[debug] Searching for versions in versionRange: (,46)
[info] Unable to find a previous version of the project in the repository.
[warn] No new version specified and file '//commons-parent/pom.xml' of 
artifact could not be opened as jar archive: error in opening zip file

java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:225)
at java.util.zip.ZipFile.(ZipFile.java:155)
at java.util.jar.JarFile.(JarFile.java:166)
at java.util.jar.JarFile.(JarFile.java:130)
at 
japicmp.maven.JApiCmpMojo.populateArchivesListsFromParameters(JApiCmpMojo.java:345)
at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:708)
at japicmp.maven.JApiCmpReport.getOptions(JApiCmpReport.java:108)
at japicmp.maven.JApiCmpReport.getDescription(JApiCmpReport.java:127)
at 
org.apache.maven.plugins.site.render.CategorySummaryDocumentRenderer.renderDocument(CategorySummaryDocumentRenderer.java:155)


Tag name:
   commons-parent-46-RC3


Tag URL:
   
https://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-46-RC3/


Commit ID the tag points at:
1828984


Site Zip:
   https://dist.apache.org/repos/dist/dev/commons/commons-parent/site.zip


Distribution files (committed at revision 26309):
   https://dist.apache.org/repos/dist/dev/commons/commons-parent/


Distribution files hashes (SHA1):
   commons-parent-46-src.tar.gz
   (SHA1: dc6d7fe92c737a55679507e95a99b347234d8844)
   commons-parent-46-src.zip
   (SHA1: 34b4f78afc7d24efc94649286d7c9bfea9ceb83f)


These are the Maven artifacts and their hashes:
   commons-parent-46-site.xml
   (SHA1: 02b3b54d26d97a72fd55b20d027040ca0daf52b7)
   commons-parent-46.pom
   (SHA1: 689b04f88f0cedd4c451686b19ad33eefb32a41f)


KEYS file to check signatures:
   http://www.apache.org/dist/commons/KEYS


Maven artifacts:
   https://repository.apache.org/content/repositories/orgapachecommons-1325


Please select one of the following options[1]:
  [ ] +1 Release it.
  [ ] +0 Go ahead; I don't care.
  [ ] -0 There are a few minor glitches: ...
  [ ] -1 No, do not release it because ...


This vote will be open at least 72 hours, i.e. until 
2018-04-15T16:00:00Z
(this is UTC time).




Cheers,
-Rob


[1] http://apache.org/foundation/voting.html
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [geometry] Initial Project Structure

2018-04-12 Thread Gilles 

Hi Matt.

On Sun, 8 Apr 2018 02:40:26 +, Matt Juntunen wrote:

Hi all,

I'm forwarding a conversation I had with Gilles on the project
structure for the new commons-geometry project in order to get
feedback on it from everyone. Basically, Gilles is proposing (and has
initially set up) a multi-module project with the following modules 
so

far:

  *   commons-geometry-bsp
  *   commons-geometry-euclidean-oned
  *   commons-geometry-euclidean-twod
  *   commons-geometry-euclidean-threed

My thought was that this module break up is too fine-grain and would
make development of code that uses more than one dimension more
difficult than it should be. I was initially picturing having a 
single
project for all of the current geometry code since it's all so 
closely
related and there's not much of it. However, I can see where Gilles 
is
coming from with the previous experience on commons-math. So, I'd 
like

to propose an alternative module break up, one that keeps all of the
basic euclidean primitives in one place:

  *   commons-geometry-core -- This would contain the code currently
in the packages
 *   o.a.c.m.geometry
 *   o.a.c.m.partitioning
 *   o.a.c.m.geometry.euclidean.oned
 *   o.a.c.m.geometry.euclidean.twod
 *   o.a.c.m.geometry.euclidean.threed
 *   o.a.c.m.geometry.hull
 *   o.a.c.m.geometry.twod.hull
 *   o.a.c.m.geometry.enclosing (this is the odd-ball in the
group here so I could be convinced to put this elsewhere)
  *   commons-geometry-spherical -- This would contain
 *   o.a.c.m.geometry.spherical.oned
 *   o.a.c.m.geometry.spherical.twod

Basically, core would contain the main geometry interfaces (eg,
Point, Space, Vector) as well as all of the basic euclidean
functionality. Most users would only ever need to pull in this 
module.

The other modules would be for other spaces, such as spherical, and
other special-purpose code that we have yet to develop.

Thoughts?


Could we have the following modules:

 * commons-geometry-core
 * commons-geometry-euclidean
 * commons-geometry-spherical

?

Gilles


Thanks,
Matt Juntunen



From: Gilles 
Sent: Saturday, April 7, 2018 6:39 PM
To: Matt Juntunen
Subject: Re: Commons Geometry Project Structure

Hi Matt.

On Sat, 7 Apr 2018 16:01:32 +, Matt Juntunen wrote:

Hi Gilles,

Yes, I'm picturing a few possible issues with the current structure.
First, I think that splitting everything up into modules at this
point
will inhibit development. For example, each time we add a new
feature,
we'll need to worry about either creating a new module or making it
fit into existing modules. For example, if we make a general utility
class that makes use of 1D, 2D, and 3D, we'd need to make a separate
module for it so that it can pull in all of the other dimension
modules.


Yes. No problem then?


It wouldn't make sense to put it into 3D since it wouldn't
just be 3D. This is actually the case with the GeometryTestUtils
class
I wrote.

Also, the code may be able to be split up now but there's no
guarantee that features we want to add in the future won't introduce
circular dependencies and other issues.


I find it difficult to reason on hypotheticals.
 From a developer's POV, circular dependencies are best avoided.


Second, having a single module for the current functionality will be
much more convenient for users. They would just need to pull in a
single dependency to have access to core functionality for all
standard dimensions. Plus, a single module makes it much easier to
discover the overall functionality of the project. This is actually
how I found out that commons-math had a BSP tree implementation: by
browsing the code from the source jar. Otherwise, I would have had 
no

idea.


I've a bad experience here with "more convenient for users"
arguments: "Commons Math" has remained monolithic primarily
because of it, pulling back development in some packages
because others needed (for some users) to maintain
compatibility with older JVMs.


Another practical point in my particular case is that I work on a
project where every 3rd-party artifact needs to be documented and
approved. Having a bunch of small artifacts makes this really
difficult.


But this is were Java is going (cf. modularization of the JDK
itself in Java 9)!

Moreover, in the context of Apache and Commons, either one
or more artefacts/modules, the notion of "official release"
is the same and concerns the *source*.
If the issue is with one vs several JAR files, it is readily
solved by creating a so-called "uber" JAR.  For user's
convenience, "Commons Geometry" may provide the necessary
maven goal.


In short, I think modules are great but not at this point for this
project. I'm picturing all of the existing geometry code as core
functionality that should be bundled together. As we add more
features, we can then make decisions about splitting off separate
modules. It's too early now.

Re: [complex] What remains for numbers-complex release

2018-04-12 Thread Gilles 

Hi.

On Thu, 12 Apr 2018 13:34:04 +0200, Eric Barnhill wrote:

Based on my review of the JIRA open issues, I think there are three
remaining issues for a numbers-complex release,


Please set the status to "resolved" for issues which you've
handled; mentioning the commit id would be nice.


assuming we proceed with
the plan to leave ComplexUtils out of the first release:

1) a parse method, so that Complex fits all requirements for being a 
VALJO
2) deciding whether we have a lot of constants (such as 
Complex.MINUS_I) or

the minimum necessary for the class to run (such as Complex.ZERO)
3) updated documentation in the user guide


4) Issue NUMBERS-65 must be handled too (as part of the API).[1]

I suggested that the userguide could be rewritten with "apt".
[See discussion in posts by Greg and Brian Driscoll, as part of GSoC.]

If this sounds good to all interested parties I will finish these up. 
As

for (2), I would lean toward just having a minimum for now.


+1

Gilles

[1] https://issues.apache.org/jira/browse/NUMBERS-65


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [Statistics] Port codes from Commons Math

2018-04-12 Thread Eric Barnhill 
HI Gimhana,

Sorry for the delay in response, but you posted this right before our
two-week Easter holiday, for which I was completely absent ; then I needed
a few days back at work to clean up all the mess. :)

Your overall goals look good to me. You have gone right to the heart of the
matter and propose to reinvent the statistics tools to make good use of the
Java 8 API. I think that's great and you should get started. Your goal of
eliminating dependencies on Commons-Math is also right.

I noticed this in the proposal:

*Covariance stats=
> IntStream.of(1,2,3).collect(Covariance::new,Covariance::accept,Covariance::combine);*


Can you explain a bit more what is happening with the method references
"accept" and "combine"?

Also this

*Week 2: Begin porting the code according to the dependency hierarchy
> identified. *
>

Sorry but I cannot see where you identify the dependency hierarchy. Are you
referring to your diagram?

Eric


On Mon, Mar 26, 2018 at 8:07 AM, Gimhana Nadeeshan <
gimhanadesilva...@cse.mrt.ac.lk> wrote:

> Hello devs,
>
> I have updated my draft proposal (Port codes from Commons Math
>  eMnPaBsE9U5YhU/edit?usp=sharing>)
> -Timeline added; before submitting the final at the Google site. Feel free
> to comment and give feedback to improve it.
>
> Best Regards,
> Gimhana.
>
> On 24 March 2018 at 17:35, Gimhana Nadeeshan <
> gimhanadesilva...@cse.mrt.ac.lk> wrote:
>
> > Hello devs,
> >
> >
> >> Note that some of the repositories included in that screen do
> >> not belong to "Commons":
> >>  * sling-*
> >>  * webservices-*
> >>  * xml-*
> >
> >
> > I'm working on it.(Still research on Kibble :-) )
> >
> > Botched alignments...
> >> "cloc" has several output formats from which you could produce
> >> nicer tables.
> >
> >
> > I'm extremely sorry. I'll fix it asap.
> >
> > Best Regards,
> > Gimhana
> >
> > On 23 March 2018 at 17:43, Gilles  wrote:
> >
> >> Hi Gimhana.
> >>
> >> On Thu, 22 Mar 2018 22:11:31 +0530, Gimhana Nadeeshan wrote:
> >>
> >>> Hello devs,
> >>>
> >>> By gone through @Gilles suggestions I found very interesting facts
> about
> >>> Commons projects.
> >>>
> >>> Feel free to check Kibble reports
> >>>
> >>>  >>> bfilter=commons=true=1458585000=1521743399>
> >>> regarding these projects. It will be given a clear picture on the
> >>> progress
> >>> of projects.In the Commons Projects side it seems visible growth of
> >>> contributors and releases.
> >>>
> >>
> >> Note that some of the repositories included in that screen do
> >> not belong to "Commons":
> >>  * sling-*
> >>  * webservices-*
> >>  * xml-*
> >>
> >> There should be a way to filter them out.
> >>
> >> And I created a simple doc using the data collected from CLOC tool to
> get
> >>> an idea of commons projects. I think This kind of document will help
> new
> >>> volunteers to get a rough idea of the scope and the current status of
> >>> projects before go deeper.Histogram of Commons Projects.
> >>>
> >>>  >>> 7V8LSglgsV5hBxVnLiCI/edit?usp=sharing>
> >>>
> >>
> >> Botched alignments...
> >> "cloc" has several output formats from which you could produce
> >> nicer tables.
> >>
> >> Regards,
> >> Gilles
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
> >
>

[complex] What remains for numbers-complex release

2018-04-12 Thread Eric Barnhill 
Based on my review of the JIRA open issues, I think there are three
remaining issues for a numbers-complex release, assuming we proceed with
the plan to leave ComplexUtils out of the first release:

1) a parse method, so that Complex fits all requirements for being a VALJO
2) deciding whether we have a lot of constants (such as Complex.MINUS_I) or
the minimum necessary for the class to run (such as Complex.ZERO)
3) updated documentation in the user guide

If this sounds good to all interested parties I will finish these up. As
for (2), I would lean toward just having a minimum for now.

Eric

JDK 11 Early Access build 8 available

2018-04-12 Thread Rory O'Donnell 


Hi Benedikt,

**JDK 11 EA build 8, *under both the GPL and Oracle EA licenses, is 
now available at **http://jdk.java.net/11**. **

*

 * Newly approved Schedule, status & features
 o http://openjdk.java.net/projects/jdk/11/
 * Release Notes:
 o http://jdk.java.net/11/release-notes
 * Summary of changes
 o https://download.java.net/java/early_access/jdk11/8/jdk-11+8.html

*Notable changes in JDK 11 EA builds since last email:*

 * Build 8:
 o If you have a library that uses the Selector API heavily then
   now would be a good time to test it out. [1]
 * Build 7
 o The VM option "-XX:+AggressiveOpts" is deprecated in JDK 11 and
   will be removed in a future release.
 * Build 6:
 o JDK-8193033 : remove terminally deprecated
   sun.misc.Unsafe.defineClass. Users should use the public
   replacement `java.lang.invoke.MethodHandles.Lookup.defineClass`
   which was added in Java SE 9. [2]

**


*SURVEY: The HotSpot Serviceability Agent (SA) *[3]

 * If you have used, or have (support) processes that utilize the
   Serviceability Agent or related APIs, then we would definitely
   appreciate if you would complete this survey:
   https://www.surveymonkey.com/r/CF3MYDL


Regards,
Rory

[1] http://mail.openjdk.java.net/pipermail/nio-dev/2018-April/004964.html
[2] 
https://docs.oracle.com/javase/9/docs/api/java/lang/invoke/MethodHandles.Lookup.html#defineClass-byte:A- 


[3] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-April/001052.html

--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland