Re: [rng] prepping for release?

[Gilles]

On Wed, 21 Mar 2018 20:23:12 -0400, Rob Tompkins wrote:

Hello all or really just Gilles,

Is the [rng] project in a state where I can try to release it?


I hope so.


I
figure better to use myself as the guinea pig for the release plugin.


Please. :-)
[But see also my post about "japicmp" and CP 45.]

Gilles


-Rob



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

[rng] prepping for release?

[Rob Tompkins]

Hello all or really just Gilles,

Is the [rng] project in a state where I can try to release it? I figure better 
to use myself as the guinea pig for the release plugin.

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

[All][RNG] "japicmp" by default in CP 45?

[Gilles]

Hi.

Using CP 45, "mvn site" runs "japicmp" even though the repository
does not contain a profile-triggering file.
Moreover it seems to find partial configuration settings, but with
wrong values.
See console log below.

---CUT---
[INFO] Generating "japicmp" report  --- 
japicmp-maven-plugin:0.11.0:cmp-report

[debug] No packaging support defined, no filtering
[debug] Searching for versions in versionRange: (,1.1-SNAPSHOT)
[debug] Parameter  not configured, i.e. no version 
filtered.
[warn] No new version specified and file 
'/home/gilles/devel/java/apache/commons-rng/trunk/commons-rng-sampling/target/classes' 
of artifact could not be opened as jar archive: 
/home/gilles/devel/java/apache/commons-rng/trunk/commons-rng-sampling/target/classes 
(Is a directory)


java.io.FileNotFoundException: 
/home/gilles/devel/java/apache/commons-rng/trunk/commons-rng-sampling/target/classes 
(Is a directory)

at java.base/java.io.RandomAccessFile.open0(Native Method)
at java.base/java.io.RandomAccessFile.open(RandomAccessFile.java:343)
	at 
java.base/java.io.RandomAccessFile.(RandomAccessFile.java:259)
	at 
java.base/java.io.RandomAccessFile.(RandomAccessFile.java:214)

at java.base/java.util.zip.ZipFile$Source.(ZipFile.java:994)
at java.base/java.util.zip.ZipFile$Source.get(ZipFile.java:960)
at java.base/java.util.zip.ZipFile.(ZipFile.java:216)
at java.base/java.util.zip.ZipFile.(ZipFile.java:148)
at java.base/java.util.jar.JarFile.(JarFile.java:324)
at java.base/java.util.jar.JarFile.(JarFile.java:295)
at java.base/java.util.jar.JarFile.(JarFile.java:261)
	at 
japicmp.maven.JApiCmpMojo.populateArchivesListsFromParameters(JApiCmpMojo.java:341)

at japicmp.maven.JApiCmpMojo.getOptions(JApiCmpMojo.java:704)
	at 
japicmp.maven.JApiCmpMojo.executeWithParameters(JApiCmpMojo.java:136)

at japicmp.maven.JApiCmpReport.executeReport(JApiCmpReport.java:71)
	at 
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
	at 
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:230)
	at 
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:349)
	at 
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:184)
	at 
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:133)
	at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
	at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
	at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:564)
	at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)


[warn] Please provide at least one resolvable new version using one of 
the configuration elements  or .
[warn] Skipping execution because no new version could be 
resolved/found.

---CUT---

Regards,
Gilles


-
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

[Gilles]

Hi Gimhana.

On Tue, 20 Mar 2018 14:36:10 +0530, Gimhana Nadeeshan wrote:

Hello devs,

I have updated my draft proposal with @Gilles's suggestions[Draft 
Proposal

V1.1

]
and I think I need some more clarifications on below suggestions


I haven't read the new version yet; I'll try to answer
some of the below questions.





== "Background" section ==






number of listed/active contributors

histogram of component's sizes (lines of code)



How to recognize "active contributors" ?


Good question!
Perhaps organize a survey? :-)


In the ML


A possible source, but probably not very efficient.  I certainly
do not suggest to perform a "manual" counting of who talks about
what. ;-)
Actually I don't know how to make automated queries (if possible).

You might want to have a look at "kibble":
  http://kibble.apache.org/
I asked that "Commons" projects be added to their "live demo".
But never got much time to explore the information it extracts
from various data sources.
I'd guess that it would be quite interesting to get more acquainted
with that tool.  Don't hesitate to subscribe to their ML (I'm not);
you might then report here what you found useful and which a lot of
us may not be aware of.


or GitHub?


AFAICT, it would be completely biased.  Indeed if one looks at
that page, for example:
  https://github.com/apache/commons-rng/graphs/contributors
there is absolutely no trace that someone not mentioned there
performed 88% of all commits. [And this is much lower than the
actual number of deletions/additions...]


What do you
mean by "histogram of component's sizes (lines of code)" ?


There is a (command-line) tool called "cloc".
You could "clone" the repositories (of a selection of the
active or popular components) and run it on the "src/main"
directory to get some indication of the size of the projects.


== "Deliverables" section ==


 * less dependencies" (an example?)
 * "Advanced mathematical functionalities": other than what
   exists now?  Or do you mean new interfaces (e.g. in
   accordance with the APIs provided by JDK8)?



Most of the classes in "math4.stat" contains "math4.exception" 
classes. And
some classes in "correlations module" dependent to "RealMatix" 
interfaces.

Can those be considered as dependencies ?


Yes.  And we don't want that any of the new component to depend
on "Commons Math" code. [With perhaps an exception for the "test"
scope.]


Can't exceptions be substituted
with inbuilt java exceptions ?


Certainly.  You should take a look at what is done in "Commons
Numbers".


@Gilles would you please explain this matrix
issue because I didn't get it much


Design issues were identified a long time ago.
You should be able to find them by doing a "Search issues"
in JIRA.
Bottom-line is we don't want to depend on an API that must
be changed (at some point).
Although not ideal, a workaround is to copy the necessary
functionality over to the new component but ensure that it
is *not* part of the API.
Better would be to tackle the issues themselves but it has
proven difficult and was postponed several times...


== "Implementation" section ==


* "Design goals": give concrete examples.


I noted some examples for Design Goals in my proposal.  But I'm not 
sure I

that I wrote it correctly. (And don't know those are the examples you
expect me to mention.) Please clarify those too.


IIRC, you mention streams. So for example, you could show how
the contribution would enhance usage (comparing "before"/"after").



== "Results" section ==


Hope to get comment from PMC...
[Wish list, design requirements, mentor(s), etc.]



mentor(s)?? @Gilles,@Eric wont't you guys be the mentors of this 
project ??
I'm asking this because I'm new to ASF and GSoC !! And I'm appreciate 
to

know how this is working !!


I don't know whether there is an official "mentor" role for GSoC,
and if so, what that implies.  This is also new for me; so I hope
that people can give advice about the "administrative" side.

For the contents, Eric indeed proposed to participate, but I
don't know how available he is (and how this will fit with
the GSoC timetable, which I also don't know).
It seems that Eric's contributions are currently extremely
asynchronous... :-}


In the meantime, you could also review the open issues for "Commons

Numbers":
  https://issues.apache.org/jira/projects/NUMBERS/

This is quite important as almost all other "Commons Math"
spin-offs will have some dependency on this new component;
hence a release of "Commons Numbers" must precede a release
of either "Commons Statistics" or "Commons Geometry".



Yep Wow sure...I'm on my way right now CM Numbers!!


Whenever you find something you can handle tackle, please
submit a PR.

Thanks,
Gilles


[...]



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

Release Announcement: General Availability of JDK 10

[Rory O'Donnell]

Hi Benedikt,

A number of items to share with you today :

*1) JDK 10 General Availability *

JDK 10, the first release produced under the six-month rapid-cadence 
release model [1][2], is now Generally Available.
We've identified no P1 bugs since we promoted build 46 almost two weeks 
ago, so that is the official GA release, ready for production use.

GPL'd binaries from Oracle are available here: http://jdk.java.net/10

This release includes twelve features:

 * 286: Local-Variable Type Inference 
 * 296: Consolidate the JDK Forest into a Single Repository
   
 * 304: Garbage-Collector Interface 
 * 307: Parallel Full GC for G1 
 * 310: Application Class-Data Sharing 
 * 312: Thread-Local Handshakes 
 * 313: Remove the Native-Header Generation Tool (javah)
   
 * 314: Additional Unicode Language-Tag Extensions
   
 * 316: Heap Allocation on Alternative Memory Devices
   
 * 317: Experimental Java-Based JIT Compiler
   
 * 319: Root Certificates 
 * 322: Time-Based Release Versioning 


*2) JDK 11 EA build 5, under both the GPL and Oracle EA licenses, are 
now available at **http://jdk.java.net/11**.*


 * 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/5/jdk-11+5.html

*3) The Z Garbage Collector Project, early access builds available : *

The first EA binary from from The Z Garbage Collector Project, also 
known as ZGC, is now available. ZGC is a scalable low latency garbage 
collector. For information on how to enable and use ZGC, please see the 
project wiki.


 * Project page: http://openjdk.java.net/projects/zgc/
 * Wiki: https://wiki.openjdk.java.net/display/zgc/Main

*4) Quality Outreach Report for **March 2018 **is available
*

 * 
https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+March+2018

*5) **Java Client Roadmap Update
*

 * We posted a blog [3] and related white paper [4] detailing our plans
   for the Java Client.

Rgds,Rory

[1] https://mreinhold.org/blog/forward-faster
[2] 
http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html
[3] Blog: 
https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates
[4] Whitepaper: 
http://www.oracle.com/technetwork/java/javase/javaclientroadmapupdate2018mar-4414431.pdf


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