Apache Software Foundation Blogs

NetBeans Status at FossBack '18

Geertjan — Fri, 22 Jun 2018 19:58:02 +0000

Go here: https://www.youtube.com/watch?v=Bnznard9Nls

Apache Maven Release 3.5.4

khmarbaise — Fri, 22 Jun 2018 18:57:38 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven 3.5.4.

Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project’s build, reporting and documentation from a central piece of information.

You can find out more about Apache Maven at https://maven.apache.org

You can download the appropriate sources etc. from the download page: https://maven.apache.org/download.cgi

Contributors

The Apache Maven value community before code and so firstly the team would like to thank the following contributors, without whom this release would not have been possible:

Code contributors:

https://github.com/eis
Florian Brunner
Łukasz Dywicki
Sylwester Lachiewicz

Issue reporters:

Falko Modler
Jarkko Rantavuori
Łukasz Dywicki
Mike Kelly
Sylwester Lachiewicz

Community testers participating in voting for this release:

Dejan Stojadinovic
Enrico Olivelli
Romain Manni-Bucau

Thank you all for your time and feedback (and apologies if we have missed anyone)

Release Notes – Maven – Version 3.5.4

Bugs:

MNG-6370 – ConcurrencyDependencyGraph#getNumberOfBuilds() does not remove finished projects from unfinished ones
MNG-6372 – On Windows Maven can output spurious ANSI escapes such as [0m [0m
MNG-6382 – JANSI fails frequently with NumberFormatException when building in parallel
MNG-6386 – ${project.baseUri} is not a valid URI (according to RFC 3986)
MNG-6388 – Error Fetching Artifacts: “[B cannot be cast to java.lang.String”
MNG-6403 – Artifact#VERSION_FILE_PATTERN does not escape period between date and time
MNG-6410 – Add groupId to —resume-from suggestion if artifactId is not unique in reactor

Improvements:

MNG-5756 – Java home output in mvn -v is misleading
MNG-5940 – Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
MNG-6362 – Add documentation information for GitHub
MNG-6363 – Remove secret thread configuration property from code
MNG-6364 – Enhanced Jenkinsfile to test Core with JDK 9
MNG-6411 – Improve readability of project list returned when —resume-from option value is invalid

Task:

MNG-6377 – switch from Git-WIP to Gitbox

Dependency upgrades:

MNG-6344 – Upgrade Guice to 4.2.0
MNG-6423 – Upgrade to Wagon 3.1.0

Share and Enjoy,

-The Apache Maven team

The Apache News Round-up: week ending 22 June 2018

Sally — Fri, 22 Jun 2018 04:23:52 +0000

We're ending the week with the following activities from the Apache community:

Support Apache –help offset the ASF's day-to-day operating expenses. Every dollar counts.
- Increase your support of the ASF with a corporate matching gift http://apache.org/foundation/contributing.html#CorporateGiving

ASF Board –management and oversight of the business affairs of the corporation in accordance with the Foundation's bylaws.
- Next Board Meeting: 18 July. Board calendar and minutes http://apache.org/foundation/board/calendar.html

ApacheCon™ –the ASF's official global conference series.
- 24-27 September: Registration open for ApacheCon North America/Montreal http://apachecon.com/acna18/
- 8 October: Apache Roadshow and Open Source Job Fair/Fairfax, VA --Save The Date!
- We are seeking Media and Community Partners for ApacheCon: contact press@apache.org for details.

ASF Infrastructure –our distributed team on three continents keeps the ASF's infrastructure running around the clock.
- 7M+ weekly checks yield popping performance at 99.76% uptime. http://status.apache.org/

ASF Operations Factoid –this week, 479 Apache contributors changed 889,905 lines of code over 2,869 commits. Top 5 contributors, in order, are: Hervé Boutemy, Martin Desruisseaux, Stephen Mallette, Gary Gregory, and Mark Thomas.

Apache BookKeeper™ –a scalable, fault-tolerant, and low-latency storage service optimized for real-time workloads.
- Apache BookKeeper 4.7.1 released https://bookkeeper.apache.org/

Apache Commons™ DBCP –implements Database Connection Pooling.
- Apache Commons DBCP 2.4.0 released http://commons.apache.org/

Apache HBase™ –an Open Source, distributed, versioned, non-relational database.
- Apache HBase 2.0.1 released http://hbase.apache.org/

Apache Qpid™ –JMS client supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org), based around the Apache Qpid Proton protocol engine and implementing the AMQP JMS Mapping as it evolves at OASIS.
- Apache Qpid JMS 0.33.0 and Qpid Broker-J 7.0.5 released http://qpid.apache.org/
- [CVE-2018-8030] Apache Qpid Broker-J Denial of Service Vulnerability when AMQP 0-8...0-91 messages exceed maximum size limit http://mail-archives.apache.org/mod_mbox/www-announce/201806.mbox/%3CCAP3WMuQfUAc9pP95Et_aQN5ko%2B6EYe4nYD7zwNXp8%2B5KPsz8XQ%40mail.gmail.com%3E

Apache Tomcat™ Native –provides portable API for features not found in contemporary JDKs.
- Apache Tomcat Native 1.2.17 released http://tomcat.apache.org/

Did You Know?

- Did you know that you can subscribe to the Apache Feathercast podcast feed to receive the latest recordings as they are published? Hear the voice of the ASF! https://feathercast.apache.org/

- Did you know that the Apache Flink website has been updated with more details about Flink's features and use cases? http://flink.apache.org

- Did you know that Indeed is using Apache Mesos to help their teams control their own deployment infrastructure? http://mesos.apache.org/

Apache Community Notices:

- The Apache Software Foundation Celebrates 19 Years of Open Source Leadership "The Apache Way" https://s.apache.org/gK4Q

- Read "Open – For Business – At the ASF" by Merv Adrian, VP Research at Gartner https://blogs.gartner.com/merv-adrian/2018/03/27/open-for-business-at-the-asf/

- The Apache Software Foundation 2018 Vision Statement https://s.apache.org/zqC3

- Apache in 2017 - By The Digits https://s.apache.org/h8do

- Foundation Statement –Apache Is Open. https://s.apache.org/PIRA

- "Success at Apache" focuses on the processes behind why the ASF "just works". https://blogs.apache.org/foundation/category/SuccessAtApache

- Please follow/like/re-tweet the ASF on social media: @TheASF on Twitter and on LinkedIn at https://www.linkedin.com/company/the-apache-software-foundation

- Do friend and follow us on the Apache Community Facebook page https://www.facebook.com/ApacheSoftwareFoundation/and Twitter account https://twitter.com/ApacheCommunity

- The list of Apache project-related MeetUps can be found at http://apache.org/events/meetups.html

- ApacheCon North America will be held 24-27 September in Montreal http://apachecon.com/

- Save the Date: Apache Roadshow DC and Open Source/Government/Cyber/Job Fair - 8 October 2018 in Fairfax, VA http://apachecon.com/

- ASF Quarterly Report: Operations Summary: November 2017 - January 2018 https://s.apache.org/UtBD

- ASF FY 2017 Annual Report is available at https://s.apache.org/FY2017AnnualReport

- Find out how you can participate with Apache community/projects/activities --opportunities open with Apache HTTP Server, Avro, ComDev (community development), Directory, Incubator, OODT, POI, Polygene, Syncope, Tika, Trafodion, and more! https://helpwanted.apache.org/

- Are your software solutions Powered by Apache? Download & use our "Powered By" logos http://www.apache.org/foundation/press/kit/#poweredby

= = =

For real-time updates, sign up for Apache-related news by sending mail to announce-subscribe@apache.org and follow @TheASF on Twitter. For a broader spectrum from the Apache community, https://twitter.com/PlanetApache provides an aggregate of Project activities as well as the personal blogs and tweets of select ASF Committers.

# # #

1.5M Lines of NetBeans Code from Oracle to Apache

Geertjan — Thu, 21 Jun 2018 12:12:55 +0000

Great news: the process of completing the 2nd donation is now done and Oracle has made available a ZIP file constituting the 2nd donation. Oracle donated around 4,000,000 lines of code in the 1st donation last year and has now completed the 2nd donation constituting around 1,500,000 lines of code. This donation constitutes the modules of NetBeans dealing with enterprise Java, JavaScript, PHP, Groovy, as well as miscellaneous features applicable to Mobile and Web development.

We will continue to wrap up the final release of Apache NetBeans (incubating) 9.0, which will be focused on Java SE only. After that, or at least separate from that process, we will start relicensing the new code, i.e., from the 2nd donation, once it is in Apache NetBeans Git. Right now, it is a ZIP file, it needs to be moved to Apache NetBeans Git, and we need to do that in the right way, and figure out what the right way is.

This is a significant step forward in the transition of NetBeans from Oracle to Apache.

Apache Maven Surefire Plugin 2.22.0 Released

khmarbaise — Sun, 17 Jun 2018 10:39:55 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven Surefire Plugin, version 2.22.0.

The release contains 33 bug fixes. Again we received contributions from the community in form of bug reports and bug fixes. Thank you and keep them coming!

You should specify the version in your project’s plugin configuration:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>2.22.0</version>
</plugin>

or for failsafe:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-failsafe-plugin</artifactId>
  <version>2.22.0</version>
</plugin>

or for surefire-report:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-report-plugin</artifactId>
  <version>2.22.0</version>
</plugin>

Release Notes – Maven Surefire – Version 2.22.0

Bugs:

SUREFIRE-1383 – dependenciesToScan Does Not Leverage Classpath Elements
SUREFIRE-1479 – SurefireBooterForkException: The forked VM terminated without properly saying goodbye since 2.20.1
SUREFIRE-1498 – Surefire prints own logs “Couldn’t load group class” to native stream.
SUREFIRE-1503 – Forked JVM immediately crashed on Unix/Linux due to new shutdown mechanism does not turn to the old shutdown mechanism
SUREFIRE-1506 – Sporadic NullPointerException in ConsoleOutputFileReporter#close()
SUREFIRE-1512 – ProcessInfo for Windows is prone to timezone offset changes
SUREFIRE-1515 – Standard output write fails for empty array
SUREFIRE-1522 – IndexOutOfBoundsException for System.out.write

New Features:

SUREFIRE-1330 – JUnit 5 surefire-provider code donation
SUREFIRE-1495 – Encoding of TXT report file should be configured by ${project.reporting.outputEncoding} and MOJO parameter encoding

Improvement:

SUREFIRE-1490 – Change header of the Failsafe Report

Tasks:

SUREFIRE-1487 – ParallelComputerBuilderTest fails on overloaded system because internal delay are shorter than blocking time of JVM
SUREFIRE-1504 – switch from Git-WIP to Gitbox
SUREFIRE-1510 – Jenkins CI fails due to performance of Windows break concurrency of forked JVMs
SUREFIRE-1518 – Upgrade version of plexus-java to 0.9.8

Enjoy,

-The Apache Maven team

Apache Maven Enforcer Plugin Version 3.0.0-M2

khmarbaise — Sun, 17 Jun 2018 10:00:00 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.0.0-M2.

You should specify the version in your project’s plugin configuration:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-enforcer-plugin</artifactId>
  <version>3.0.0-M2</version>
</plugin>

You can download the appropriate sources etc. from the download page:

https://maven.apache.org/enforcer/download.cgi

Release Notes – Maven Enforcer Plugin Version 3.0.0-M2 (including 3.0.0-M1)

Bugs:

MENFORCER-234 – Link to plugin’s web site is reported as redirected by maven linkcheck plugin.
MENFORCER-239 – Fix link in navigation (enforcer/maven-enforcer-plugin/index.html) RESOURCES
MENFORCER-240 – Link to page does not work
MENFORCER-265 – Get site generation working
MENFORCER-268 – Usage of CI friendly version placeholders does not work
MENFORCER-274 – Use of RequireJavaVersion with Java-9 breaking starting at b175
MENFORCER-281 – RequirePluginVersions broken with “CI Friendly versions”

New Features:

MENFORCER-204 – Add new rule: should be able to make sure that project artifact is a Snapshot
MENFORCER-247 – Add a “require file checksum” rule
MENFORCER-273 – RequireUpperBoundDeps.excludes
MENFORCER-282 – Add RequireProfileIdsExist to ensure al mentioned cmdline profiles exist

Improvements:

MENFORCER-228 – DependencyConvergence: Simplify logging errors
MENFORCER-253 – Upgrade maven-shared-components parent to version 30
MENFORCER-259 – The rule BanDuplicatePomDependencyVersions is not documented
MENFORCER-263 – Upgrade mrm-maven-plugin to 1.0.0
MENFORCER-266 – Remove usage of prerequisites in parent pom
MENFORCER-291 – Cleanup ReactorModuleConvergence implementation
MENFORCER-292 – Remove getModelsRecursively from EnforcerRuleUtils
MENFORCER-293 – Remove deprecated marked ignoreParent from BanDistributionManagement

Tasks:

MENFORCER-221 – Removed deprecated marked constructor from EnforcerExpressionEvaluator
MENFORCER-272 – Allow site generation to work
MENFORCER-284 – switch to Git
MENFORCER-296 – Update URL for CI System

Dependency upgrades:

MENFORCER-278 – Upgrade mockito to 2.X to prevent JDK 9 WARNINGs
MENFORCER-289 – Upgrade maven-plugin-plugin to 3.5
MENFORCER-290 – Upgrade plexus-utils 3.1.0
MENFORCER-297 – Upgrade parent to 31
MENFORCER-303 – Upgrade mave-surefire/failsafe-plugin 2.21.0

Enjoy,

-The Apache Maven team

The Apache News Round-up: week ending 15 June 2018

Sally — Fri, 15 Jun 2018 16:15:15 +0000

Happy Friday! Let's review what the Apache community has worked on over the past week:

ASF Board –management and oversight of the business affairs of the corporation in accordance with the Foundation's bylaws.
- Next Board Meeting: 20 June. Board calendar and minutes http://apache.org/foundation/board/calendar.html

ASF Infrastructure –our distributed team on three continents keeps the ASF's infrastructure running around the clock.
- 7M+ weekly checks yield crackling performance at 99.83% uptime. http://status.apache.org/

ASF Operations Factoid –this week, 561 Apache contributors changed 1,111,834 lines of code over 3,486 commits. Top 5 contributors, in order, are: Gary Gregory, Dan Klco, Dewayne Richardson, Andrea Cosentino, and Carlos Sanchez Gonzalez.

Apache Crail (incubating) –a high-performance distributed data store designed for fast sharing of ephemeral data in distributed data processing workloads.
- Apache Crail 1.0-incubating released http://crail.apache.org/

Apache Geode™ –low latency, high concurrency Big Data management solutions.
- CVE-2017-15695 Apache Geode remote code execution vulnerability http://mail-archives.apache.org/mod_mbox/www-announce/201806.mbox/%3CCAEwge-GY_F0BJk33EFcY2czTwM%3DOkgrqN2%3DaWHV0bafLf6hgfw%40mail.gmail.com%3E

Apache Jackrabbit™ Oak–a scalable, high-performance hierarchical content repository designed for use as the foundation of modern world-class Web sites and other demanding content applications.
- Apache Jackrabbit Oak 1.9.3 released http://jackrabbit.apache.org/

Apache MINA™ –a network application framework that helps users easily develop high performance and high scalability network applications.
- Apache MINA 2.0.19 released http://mina.apache.org/

Apache Qpid™ Dispatch –is a router for the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org).
- Apache Qpid Dispatch 1.1.0 released is a router for the Advanced Message Queuing Protocol 1.0

Did You Know?

- Did you know that Feathercast highlights Apache projects, people, and communities, often records during events such as ApacheCon and Apache Roadshows? Hear the voice of the ASF! https://feathercast.apache.org/

- Did you know that you can learn about Apache projects history and evolution at https://projects.apache.org/ ?

- Did you know that those with use cases for running Apache Groovy on JDK7 can help shape the project's future roadmap? https://lists.apache.org/thread.html/dfd5198431f62c90b6c5e0a5554017310395f99557b22054f4aa1b5e@%3Cusers.groovy.apache.org%3E

Apache Community Notices:

- The Apache Software Foundation Celebrates 19 Years of Open Source Leadership "The Apache Way" https://s.apache.org/gK4Q

- Read "Open – For Business – At the ASF" by Merv Adrian, VP Research at Gartner https://blogs.gartner.com/merv-adrian/2018/03/27/open-for-business-at-the-asf/

- The Apache Software Foundation 2018 Vision Statement https://s.apache.org/zqC3

- Apache in 2017 - By The Digits https://s.apache.org/h8do

- Foundation Statement –Apache Is Open. https://s.apache.org/PIRA

- "Success at Apache" focuses on the processes behind why the ASF "just works". https://blogs.apache.org/foundation/category/SuccessAtApache

- Please follow/like/re-tweet the ASF on social media: @TheASF on Twitter and on LinkedIn at https://www.linkedin.com/company/the-apache-software-foundation

- Do friend and follow us on the Apache Community Facebook page https://www.facebook.com/ApacheSoftwareFoundation/and Twitter account https://twitter.com/ApacheCommunity

- The list of Apache project-related MeetUps can be found at http://apache.org/events/meetups.html

- Apache Big Data project communities will be participating at DataWorks Summit 17-21 June 2018 in San Jose https://dataworkssummit.com/

- ApacheCon North America will be held 24-27 September in Montreal http://apachecon.com/

- Save the Date: Apache Roadshow DC and Open Source/Government/Cyber/Job Fair - 8 October 2018 in Fairfax, VA http://apachecon.com/

- ASF Quarterly Report: Operations Summary: November 2017 - January 2018 https://s.apache.org/UtBD

- ASF FY 2017 Annual Report is available at https://s.apache.org/FY2017AnnualReport

- Are your software solutions Powered by Apache? Download & use our "Powered By" logos http://www.apache.org/foundation/press/kit/#poweredby

= = =

# # #

Apache NetBeans at FOSS Backstage 2018

Geertjan — Thu, 14 Jun 2018 08:48:50 +0000

Yesterday I attended FOSS Backstage in Berlin. FOSS Backstage is a "conference on everything governance, collaboration, legal & economics within the scope of FOSS". I went there to present my session, based on the Apache NetBeans experiences of the past two years or so, entitled 10 Tips for Moving Large Corporate Projects to Apache. I also went because I knew that several people from the Apache Software Foundation who have been instrumental in the transition of NetBeans to Apache would also be there and I thought it was time to put some faces to the many new names that we've been confronted with during the transition process!

The event began for me with a wonderful speakers dinner, where I met three of the absolute key Apache people involved in the Apache NetBeans project — Emmanuel Lecharny, Bertrand Delacretaz, and Mark Struberg. Here we are, literally about 5 minutes after meeting, discussing the current status of the transition process (click the image below to increase size):

Bertrand and Mark are two of the Apache NetBeans mentors, while Emmanuel was a mentor during the beginning phase of the transition. Both Bertrand and Emmanuel were involved really in the pre-start phase of the donation, with many thanks to Emmanuel Hugonnet who introduced us, after a very nice and long conversation some years ago in Athens!

During the event, I also met several others who I have seen on Apache mailing lists — Justin McLean, Shane Curcuru, and Jim Jagielski. Really amazing to meet all these names in person — and not to forget, I also met Mark Thomas, who is the Apache VP for Brand Management, i.e., who we need to work with for the brand/domain donation, and Malcolm Bain, a lawyer specialising in ICT law, based in Barcelona, with a special focus on Open Source Projects. I also spoke with Kevin A. McGrail, who is Apache VP Fundraising, who later sent me this very nice and welcome message: "Did I hear you correct and you wanted to talk about how I can help NetBeans with sponsorship?" Yes, you did, Kevin!

What really struck me is how positive everyone at Apache is about the Apache NetBeans project. Everyone mentioned how great and active the Apache NetBeans community is, i.e., active mailing lists, several discussion threads, voting in new PPMC members, and of course also doing releases already, with everyone positive and committed to the project. I realized, especially as I was doing my presentation, when I was talking about the history of NetBeans, that the reason why Apache NetBeans is going so well in many respects is because we've been working on our community from the very beginning. I.e., even while NetBeans was part of commercial entities (i.e., Sun and Oracle), we had an army of volunteers all over the world, organized in structures such as NetCAT (i.e., volunteer testers), and the NetBeans Dream Team (i.e., volunteer evangelists), while we've also been organizing NetBeans Days all over the world for several years, i.e., we've come to Apache with a ready-made community, whereas for the majority of other projects coming to Apache the reason that they're coming to Apache is because they don't yet have a community and are looking to Apache to provide the infrastructure for doing so.

Also, really crucially, we've spent years educating developers everywhere about the NetBeans APIs, the NetBeans source structure, etc. That's been massively impactful now that we're in Apache, since those who are most active right now are those that have been involved with NetBeans for around 20 years or so. In short, there are definitely advantages to being a large corporate project in terms of transitioning to Apache — just like NetBeans, you may take a long time to get all your code across (because the donating company needs to spend time auditing and cleaning the code etc), though on the other hand you'll potentially be bringing a massive amount of existing knowledge and a vibrant community along with you.

In short, it was great to be at FOSS Backstage and I am sure more and more Apache NetBeans community members will be submitting sessions to similar Apache events around the world and sharing their experiences, too.

Notice: Java 6 and 7 users: SSL Protocol upgrades coming to Central

khmarbaise — Wed, 13 Jun 2018 07:57:53 +0000

The march of standards continues unabated. Legacy TLS protocols 1.0 and 1.1 have varying weaknesses that could lead to a false sense of security.

In June, in an effort to raise security and comply with modern standards, the insecure TLS 1.0 & 1.1 protocols will no longer be supported for SSL connections to Central. This should only affect users of Java 6 that are also using https to access central, which by our metrics is less than .2% of users.

At the same time, this conversion will allow Central to support HTTP/2 with potential performance gains for modern http clients.

The details about why, when and what you need to do are documented at the link below. As questions come up, we will continue to update this faq.

If there is specific information required for non-maven build systems, please send it along and we will include that as well.

https://central.sonatype.org/articles/2018/May/04/discontinue-support-for-tlsv11-and-below/

The same content has been posted as a blog to make it easier to disseminate here: https://blog.sonatype.com/enhancing-ssl-security-and-http/2-support-for-central

Announcing Phoenix 4.14 released

jamestaylor — Tue, 12 Jun 2018 01:14:23 +0000

The Apache Phoenix team is pleased to announce the immediate availability of the 4.14.0 release. Apache Phoenix enables SQL-based OLTP and operational analytics for Apache Hadoop using Apache HBase as its backing store and providing integration with other projects in the Apache ecosystem such as Spark, Hive, Pig, Flume, and MapReduce. This 4.x release is compatible with HBase 0.98, 1.1, 1.2, 1.3, 1.4, and CDH 5.11.2, 5.12.2, 5.13.2, and 5.14.2

Highlights of the release include:

Over 90 bug fixes
Support for HBase 1.4
Support for CDH 5.11.2, 5.12.2, 5.13.2, and 5.14.2
Support for GRANT and REVOKE
Avoid server retries for mutable indexes
Pure client side index maintenance for transactional tables
Prune local index regions scanned during query execution
Support NOT NULL constraint for any columns of immutable tables

Source and binary downloads are available here.

Apache Maven WAR Plugin, version 3.2.2

khmarbaise — Sun, 10 Jun 2018 10:48:26 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven WAR Plugin, version 3.2.2.

The WAR Plugin is responsible for collecting all artifact dependencies, classes and resources of the web application and packaging them into a web application archive.

You should specify the version in your project’s plugin configuration:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-war-plugin</artifactId>
  <version>3.2.2</version>
</plugin>

You can download the appropriate sources etc. from the download page.

Important Note:

Maven 3.X only
JDK 7 minimum requirement

Release Notes – Maven WAR Plugin – Version 3.2.2

Bug:

MWAR-303 – filtering of ${project.developers[0].id} does not work

Dependency upgrade:

MWAR-417 – Upgrade to plexus-interpolation to version 1.25

Many thanks to all reporters/contributors/testers of this release.

Voters:

Gabriel Belingueres

Enjoy,

-The Apache Maven team

Apache Maven Help Plugin, version 3.1.0

khmarbaise — Sat, 9 Jun 2018 13:49:29 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven Help Plugin, version 3.1.0

The Maven Help Plugin is used to get relative information about a project or the system. It can be used to get a description of a particular plugin, including the plugin’s goals with their parameters and component requirements, the effective POM and effective settings of the current build, and the profiles applied to the current project being built.

Important Notes since Version 3.0.0

Maven 3+ only
JDK 7 minimum requirement

You should specify the version in your project’s plugin configuration:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-help-plugin</artifactId>
  <version>3.1.0</version>
</plugin>

You can download the appropriate sources etc. from the download page.

Release Notes – Maven Help Plugin – Version 3.1.0

New Feature:

MPH-144 – Add ability to print mvn help:evaluate output to stdout in quiet mode

Improvement:

MPH-151 – Add documentation information for GitHub

Tasks:

MPH-145 – Upgrade mave-surefire/failsafe-plugin 2.21.0
MPH-146 – JavaDoc Issues / Code cleanups

Dependency upgrades:

MPH-147 – plexus-interactivity-api to 1.0-alpha-6
MPH-148 – Upgrade xstream to 1.4.10
MPH-149 – Upgrade jdom-legacy to jdom2 2.0.6

Enjoy,

-The Apache Maven team

Apache Maven Wagon 3.1.0 Released

khmarbaise — Sat, 9 Jun 2018 10:59:14 +0000

The Apache Maven team is pleased to announce the release of Apache Maven Wagon 3.1.0.

Apache Maven Wagon is a transport abstraction that is used in Mavens artifact and repository handling code.

You can download the appropriate sources etc. from the download page:

https://maven.apache.org/wagon/download.cgi

Release Notes – Maven Wagon – Version 3.1.0

Bugs:

WAGON-452 – RelaxedTrustStrategy does not handle multiple certificates
WAGON-493 – Maven wagon-scm documentation is erroneous
WAGON-495 – Fix checkoutDirectory leak
WAGON-496 – site-deploy using wagon-ssh broke in 2.12 because of the fix for WAGON-465
WAGON-497 – ScmWagon#put() strips parent dirs from the target path if they already exist in SCM
WAGON-498 – ScmWagon should work in binary and shallow mode when possible
WAGON-499 – apache-rat complains about Eclipse .checkstyle files
WAGON-503 – Directory gives out of date error in putDirectory() to a non-empty Subversion repo
WAGON-518 – AbstractHttpClientWagon#putFromStream() reads entire content to memory

New Feature:

WAGON-501 – Add ScmGitExeWagonTest

Improvement:

WAGON-482 – Use sparse files in HugeFileDownloadTest with Java 7

Task:

WAGON-504 – switch from Git-WIP to Gitbox

Dependency upgrades:

WAGON-505 – Upgrade SLF4J to 1.7.25
WAGON-506 – Upgrade Jetty to 9.2.24.v20180105
WAGON-507 – Upgrade Plexus Utils to 3.1.0
WAGON-508 – Upgrade JUnit to 4.12
WAGON-509 – Upgrade Commons IO to 2.6
WAGON-510 – Upgrade parent to 31
WAGON-511 – Upgrade Plexus Container Default to 1.7.1
WAGON-512 – Upgrade EasyMock to 3.5.1
WAGON-513 – Upgrade HttpClient to 4.5.5
WAGON-514 – Upgrade HttpCore to 4.4.9
WAGON-515 – Upgrade JSoup to 1.11.2
WAGON-516 – Upgrade Jackrabbit WebDAV to 2.14.4
WAGON-519 – Upgrade to SCM 1.10.0

Enjoy,

-The Apache Maven team

The Apache News Round-up: week ending 8 June 2018

Sally — Fri, 8 Jun 2018 16:05:26 +0000

The week has skipped by, and the Apache community has been active with the following projects:

Success at Apache –a monthly blog series that focuses on the processes behind why the ASF "just works".
- The Chance to Influence the World by Weiwei Yang https://s.apache.org/MfuS

ApacheCon™ –the ASF's official global conference series.
- 11-14 June: Apache Roadshow Europe/Berlin --co-located within FOSS Backstage https://foss-backstage.de/
- 24-27 September: ApacheCon North America/Montreal http://apachecon.com/acna18/
- 8 October: Apache Roadshow and Open Source Job Fair/Fairfax, VA --Save The Date!
- We are seeking Media and Community Partners for ApacheCon: contact press@apache.org for details.

ASF Infrastructure –our distributed team on three continents keeps the ASF's infrastructure running around the clock.
- 7M+ weekly checks yield smashing performance at 99.74% uptime. http://status.apache.org/

ASF Operations Factoid –this week, 473 Apache contributors changed 712,261 lines of code over 2,857 commits. Top 5 contributors, in order, are: Jean-Baptiste Onofré, Robert Butts, Nick Couchman, Daniel Sun, and Colm O hEigeartaigh.

Apache Atlas™ –a scalable and extensible set of core foundational governance services.
- Apache Atlas 1.0.0 released http://atlas.apache.org/

Apache Commons™ Compress –defines an API for working with compression and archive formats.
- Apache Commons Compress 1.17 released http://commons.apache.org/

Apache Ignite™ –an In-Memory Data Fabric providing in-memory data caching, partitioning, processing, and querying components.
- [CVE-2014-0114]: Apache Ignite is vulnerable to existing CVE-2014-0114 http://mail-archives.apache.org/mod_mbox/www-announce/201806.mbox/%3CCAK0qHnrDU3PVMWdeBEZjatHGjiB8SBbmk1UMuPEphvMuCHkbhA%40mail.gmail.com%3E

Apache Jackrabbit™ –a fully compliant implementation of the Content Repository for Java(TM) Technology API, version 2.0 (JCR 2.0) as specified in the Java Specification Request 283 (JSR 283).
- Apache Jackrabbit 2.10.8 released http://jackrabbit.apache.org/

Apache JSPWiki™ –a feature-rich and extensible WikiWiki engine built around the standard JEE components (Java, servlets, JSP).
- Apache JSPWiki 2.10.4 released http://jspwiki.apache.org/

Apache MINA™ –a network application framework that helps users easily develop high performance and high scalability network applications.
- Apache MINA 2.0.18 released http://mina.apache.org/

Apache NiFi™ MiNiFi –a subproject of Apache NiFi that is a complementary data collection approach that supplements the core tenets of NiFi in dataflow management, focusing on the collection of data at the source of its creation.
- Apache NiFi MiNiFi C++ 0.5.0 released https://nifi.apache.org/

Apache Qpid™ Broker –implements the latest AMQP specification, the first open standard for enterprise messaging, and provides transaction management, queuing, distribution, security, management, clustering, federation and heterogeneous multi-platform support and more.
- Apache Qpid Broker-J 7.0.4 released https://qpid.apache.org/

Apache Storm™ –a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data.
- Apache Storm 1.1.3 and 1.2.2 released http://storm.apache.org/

Apache Traffic Control™ –Open Source Content Delivery Network used by Cisco, Comcast, Cox, Qwilt, and others serves 30+ petabytes of content each day.
- The Apache Software Foundation Announces Apache® Traffic Control™ as a Top-Level Project

Did You Know?

- Did you know that Apache Mynewt is the ASF's first operating system for building, deploying, and securely managing billions of devices? Yes: Apache has IoT projects! http://mynewt.apache.org/

- Did you know that you can see the roster of committers on Apache projects at http://home.apache.org/ ?

- Did you know that next week is All Apache Week in Berlin? Starting with Berlin Buzzwords, followed by Apache Roadshow Europe, co-located with FOSS Backstage? https://berlinbuzzwords.de/ https://foss-backstage.de/ http://apachecon.com/

Apache Community Notices:

- The Apache Software Foundation Celebrates 19 Years of Open Source Leadership "The Apache Way" https://s.apache.org/gK4Q

- Read "Open – For Business – At the ASF" by Merv Adrian, VP Research at Gartner https://blogs.gartner.com/merv-adrian/2018/03/27/open-for-business-at-the-asf/

- The Apache Software Foundation 2018 Vision Statement https://s.apache.org/zqC3

- Apache in 2017 - By The Digits https://s.apache.org/h8do

- Foundation Statement –Apache Is Open. https://s.apache.org/PIRA

- "Success at Apache" focuses on the processes behind why the ASF "just works". https://blogs.apache.org/foundation/category/SuccessAtApache

- Please follow/like/re-tweet the ASF on social media: @TheASF on Twitter and on LinkedIn at https://www.linkedin.com/company/the-apache-software-foundation

- Do friend and follow us on the Apache Community Facebook page https://www.facebook.com/ApacheSoftwareFoundation/and Twitter account https://twitter.com/ApacheCommunity

- The list of Apache project-related MeetUps can be found at http://apache.org/events/meetups.html

- We're teaming up the Apache Roadshow Europe with Berlin Buzzwords - 10-12 June 2018 (Apache Lounge dates: 11-12 June) https://berlinbuzzwords.de/

- The 2018 Apache EU Roadshow will be held during FOSS Backstage in Berlin 13-14 June 2018 https://foss-backstage.de/

- Apache Big Data project communities will be participating at DataWorks Summit 17-21 June 2018 in San Jose https://dataworkssummit.com/

- ApacheCon North America will be held 24-27 September in Montreal http://apachecon.com/

- Save the Date: Apache Roadshow DC and Open Source/Government/Cyber/Job Fair - 8 October 2018 in Fairfax, VA http://apachecon.com/

- ASF Quarterly Report: Operations Summary: November 2017 - January 2018 https://s.apache.org/UtBD

- ASF FY 2017 Annual Report is available at https://s.apache.org/FY2017AnnualReport

- Are your software solutions Powered by Apache? Download & use our "Powered By" logos http://www.apache.org/foundation/press/kit/#poweredby

= = =

# # #

Apache Maven PMD Plugin Version 3.10.0 Released

khmarbaise — Thu, 7 Jun 2018 06:17:06 +0000

The Maven team is pleased to announce the release of the Apache Maven PMD Plugin, version 3.10.0

A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics.

You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-pmd-plugin/download.cgi

You should specify the version in your project’s plugin configuration:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-pmd-plugin</artifactId>
  <version>3.10.0</version>
</plugin>

Release Notes – Apache Maven PMD Plugin – Version 3.9

Bugs:

[MPMD-253] – PMD links to java Xref fail in aggregated report
[MPMD-257] – Allow to disable analysisCache completely, avoid warnings
[MPMD-258] – PMD output multiplies with every module in multi module projects
[MPMD-259] – FileNotFoundException with analysisCache=true, includeTests=true and no test classes

New Feature:

[MPMD-256] – Add maxAllowedViolations property for PMD

Improvements:

[MPMD-261] – Upgrade to PMD 6.4.0
[MPMD-263] – Add documentation information for GitHub
[MPMD-264] – Add rule priority to HTML report

Dependency upgrades:

[MPMD-252] – Upgrade parent to 31
[MPMD-262] – Upgrade maven-surefire/failsafe-plugin 2.21.0

Enjoy,

-The Maven team

Success at Apache: the Chance to Influence the World

Sally — Mon, 4 Jun 2018 10:05:39 +0000

by Weiwei Yang

I submitted my first patch to Apache Hadoop in 2015, a very simple bug fix with just a few lines of changes. However the feeling is still vivid to me when the patch was accepted, I felt great accomplishment. It was not about how big the change was, but rather because I knew even a small change would help a lot of people. This is the best thing I like about working in Open Source, the work I've done has the chance to influence the world.

As of today, I have contributed nearly 200 patches to Apache Hadoop, over 20k lines of code. I still feel happy when the community accepts my patches. I believe that having such passion is an essential for an individual contributor to make the way to Apache. Unless your company paid you to work on Open Source, you must find yourself such accomplishment during the work, otherwise the commitment won't last. Like me, I spent over 3 years until I received commit privileges for Hadoop. In retrospect, it was a tough, challenging but fast growth journey. I am glad I did not give up and finally get where I am now.

If you are hired by a commercial company that sells products or services powered by Open Source software, then congratulations, you are on a shortcut to Apache. Such companies usually have a strong team working directly on Open Source projects and a lot of committers. Being a member of such organization, you will have more time working on the project, get faster feedback of your patches, opportunities to participate more discussions and much deeper involvement. Unfortunately, I was not working for such companies. Moreover, my native language is not English and I have a big timezone gap with the majority people from the community. That makes my path to Apache much more difficult. I believe there are many people, just like me at 3 years ago, who are willing to contribute but finding it hard to. In this post, I will share some tips how to work with the Apache community and how to grow up to a committer.

First, it's important that you know things that are public to everyone. Every Open Source project has its own tutorials introducing how to contribute, be sure you have read that before working on any patches. Those documents generally tell you how to contribute code in the "Apache" way, and how to collaborate with the community.

Second, don't mind fixing bugs. Actually I suggest to begin with fixing bugs. You may find bugs in your daily work, or somebody reported to the community. No matter if they are big or not, bugs must be fixed so that it's easier to get attention from the community. In an Open Source community, everyone volunteers to review some other ones' patches. So don't be upset if nobody gets to your patch quickly, try to soft ping committers around this area. But never push them for anything. And always be polite.

More involvement. There are many ways to get more involvement. First, if a community sets up a MeetUp once in a while, try to attend even you are remote or in an inconvenient local time. Such MeetUps can help you gather information of the development status, current community focus etc. It also helps others to get familiar with your face; second, try to participate in more discussions. This could be discussions on mailing lists, issue tracking systems or a Web conference that discusses a particular issue/design. In my opinion, this is the hardest part especially for contributors from overseas.

Be self-motivated and passionate. Nobody forces you to work on Open Source projects, you need to keep motivating yourself. Like I first mentioned in this post, there are more ways to be self-motivated than just feeling accomplished. Working in the community gives you the chance to work in a diverse environment, meet people from different companies and different countries; you can get as many chances as you want to solve difficult real problems, and improve your skills; you can build your reputation in the community which also helps your career development.

I truly hope my experiences would help people. Now I am working at Alibaba Group, and it gives me more reason to write this post. I see a lot of talented people around, they have solid skills, they have done and are doing a lot work to make Hadoop better. They are open to contributing back but are having various of difficulties to work with the community. I am committed to helping grow this community, and I do believe an open and diverse community will help the project thrive.

Weiwei Yang is a Staff Engineer working at Alibaba Group. He has been working on Big Data area for over 8 years, most of time working on Apache Hadoop. He contributed to several Apache projects such as YARN, HDFS, MapReduce, Ambari and Slider, and an active Hadoop committer. At present, he is working in Alibaba’s data infrastructure team and is focusing on evolving Apache YARN to support mixed workloads, improve performance and cluster utilization. Prior to that, he worked in IBM for several years and won multiple Open Source contribution awards.

= = =

"Success at Apache" is a monthly blog series that focuses on the processes behind why the ASF "just works" https://blogs.apache.org/foundation/category/SuccessAtApache

# # #

The Apache Software Foundation Announces Apache® Traffic Control™ as a Top-Level Project

Sally — Mon, 4 Jun 2018 09:00:53 +0000

Open Source Content Delivery Network used by Cisco, Comcast, Cox, Qwilt, and others serves 30+ petabytes of content each day.

Wakefield, MA —4 June 2018— The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of more than 350 Open Source projects and initiatives, announced today Apache^® Traffic Control™ as a Top-Level Project (TLP).

Apache Traffic Control can be used to build, monitor, configure, and provision a large-scale content delivery network (CDN). Traffic Control originated at Comcast and was released as an Open Source project in April 2015; the project was donated to the Apache Incubator in July 2016.

"We are extremely excited to be an Apache Top-Level Project," said Dave Neuman, Vice President of Apache Traffic Control. "This is an amazing milestone for Traffic Control, and a testament to scale, strength and dedication of everyone in our community."

Traffic Control is a CDN control plane originally built around Apache Traffic Server as the caching software. Traffic Control implements all the core functions of a modern CDN using the following components:

Traffic Router — Routes clients to the best available cache on the CDN using HTTP(s) redirects or DNS;
Traffic Monitor — Monitors caches for both system and application metrics and uses those to make health decisions on the CDN;
Traffic Ops — Configuration, tenant, and inventory management for all CDN components;
Traffic Stats — Calculates and stores statistics about CDNs managed by Traffic Control; and
Traffic Portal — User interface for managing and operating Traffic Control CDNs

Every day, Traffic Control CDNs serve over 50 billion transactions amounting to over 30 petabytes of content worldwide. Apache Traffic Control is in use at Comcast, Cisco, Cox, and Qwilt, among others.

"Traffic Control unlocks significant innovation in the CDN space," said Mark Torluemke, Director of CDN Engineering at Comcast. "The ASF is the perfect place for that innovation to thrive."

"Having Traffic Control become an Apache Top-Level Project is a testament to the technology's functional breadth, performance, and scalability in building Content Delivery Networks," said Eric Friedrich, OMD Technical Leader at Cisco. "As an active contributor to Traffic Control, Cisco is very excited to continue incorporating Traffic Control into its Open Media Distribution offering for Service Provider video distribution solutions."

"Qwilt is thrilled to see Traffic Control receive this hard-earned and well-deserved status as an Apache Top-Level Project. TLP status recognizes the extraordinary work and progress of the Traffic Control community of contributors," said Alon Maor, CEO at Qwilt. "We are proud to be part of this community and particularly pleased to see Traffic Control's stature continue to rise within the Apache Software Foundation. As we go to market with Traffic Control, we consistently get feedback from prospects and customers about the value of an Open Source approach to the modern CDN. The Apache Traffic Control Project embodies the Web-scale innovation that service providers are so eager to embrace."

"Cox has been involved with this project since 2014 and has over 4 years of experience with running it in a large national network. Apache Traffic Control is the first CDN platform in the Open Source domain and really brings something that was missing in the market," said Steve Malenfant, Principal Engineer at Cox. "We love the flexibility of the system and the ease to scale up as well as being able to collaborate with peers that have similar challenges."

"As great as this accomplishment is, it's only the beginning," added Neuman. "We are looking forward to growing our community, attracting new contributors, and continuing to be a leader in the CDN space."

The Traffic Control community holds summits twice a year and is very active on Slack as well as its official project user and developer mailing lists. Catch Apache Traffic Control in action at ApacheCon North America 24-27 September 2018.

Availability and Oversight
Apache Traffic Control software is released under the Apache License v2.0 and is overseen by a self-selected team of active contributors to the project. A Project Management Committee (PMC) guides the Project's day-to-day operations, including community development and product releases. For downloads, documentation, and ways to become involved with Apache Traffic Control, visit http://trafficcontrol.apache.org/

About The Apache Software Foundation (ASF)
Established in 1999, the all-volunteer Foundation oversees more than 350 leading Open Source projects, including Apache HTTP Server --the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 730 individual Members and 6,800 Committers across six continents successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(c)(3) charitable organization, funded by individual donations and corporate sponsors including Aetna, Anonymous, ARM, Bloomberg, Budget Direct, Capital One, Cerner, Cloudera, Comcast, Facebook, Google, Hortonworks, Huawei, IBM, Indeed, Inspur, LeaseWeb, Microsoft, Oath, ODPi, Pineapple Fund, Pivotal, Private Internet Access, Red Hat, Target, and Union Investment. For more information, visit http://apache.org/ and https://twitter.com/TheASF

© The Apache Software Foundation. "Apache", "Traffic Control", "Apache Traffic Control", and "ApacheCon" are registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. All other brands and trademarks are the property of their respective owners.

# # #

Apache Maven Invoker Plugin Version 3.1.0 Released

khmarbaise — Fri, 1 Jun 2018 19:04:39 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven Invoker Plugin, version 3.1.0.

The Invoker Plugin is used to run a set of Maven projects. The plugin can determine whether each project execution is successful, and optionally can verify the output generated from a given project execution.

This plugin is in particular handy to perform integration tests for other Maven plugins. The Invoker Plugin can be employed to run a set of test projects that have been designed to assert certain features of the plugin under test.

You should specify the version in your project’s plugin configuration:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-invoker-plugin</artifactId>
  <version>3.1.0</version>
</plugin>

You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-invoker-plugin/download.cgi

Release Notes – Maven Invoker Plugin – Version 3.1.0

Bugs:

MINVOKER-191 – “Artifact is not fully assembled” error with maven-invoker-plugin in parallel/multi thread build
MINVOKER-224 – Unable to set cloneProjectsTo to null

New Feature:

MINVOKER-233 – Call an invoker with a given timeout

Improvement:

MINVOKER-236 – improve display of setup jobs

Tasks:

MINVOKER-228 – Improve documentation: “Using with other integration test frameworks” page
MINVOKER-237 – Upgrade to JDK 7 minimum.

Dependency upgrades:

MINVOKER-232 – Upgrade parent to 31
MINVOKER-234 – Upgrade maven-shared-utils to 3.2.1
MINVOKER-235 – Upgrade plexus-utils 3.1.0
MINVOKER-238 – Upgrade maven-invoker to 3.0.1

Enjoy,

-The Apache Maven team

Apache Maven Shared Maven Invoker Version 3.1.0 Released

khmarbaise — Fri, 1 Jun 2018 19:03:03 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven Shared Maven Invoker, version 3.1.0

This API is concerned with firing a Maven build in a new JVM. It accomplishes its task by building up a conventional Maven command line from options given in the current request, along with those global options specified in the invoker itself. Once it has the command line, the invoker will execute it, and capture the resulting exit code or any exception thrown to signal a failure to execute. Input/output control can be specified using an InputStream and up to two InvocationOutputHandlers.

You can download the appropriate sources etc. from the download page.

<dependencies>
  <dependency>
    <groupId>org.apache.maven.shared</groupId>
    <artifactId>maven-invoker</artifactId>
    <version>3.1.0</version>
  </dependency>
</dependencies>

Release Notes – Maven Shared Components – Version maven-invoker-3.1.0

Improvement:

MSHARED-702 – Remove hard coded versions for plexus-component-annotations/plexus-component-metadata

Tasks:

MSHARED-625 – Refactored to use ‘maven-shared-utils’ instead of ‘plexus-utils’.
MSHARED-729 – Upgrade to JDK 7 minimum.

Dependency upgrades:

MSHARED-700 – Upgrade parent to 31
MSHARED-728 – Upgrade maven-shared-utils to 3.2.1

Enjoy,

-The Apache Maven team

Apache Maven JavaDoc Plugin Version 3.0.1 Released

khmarbaise — Fri, 1 Jun 2018 18:48:34 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven JavaDoc Plugin, version 3.0.1.

The Javadoc Plugin uses the Javadoc tool to generate javadocs for the specified project.

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-javadoc-plugin</artifactId>
  <version>3.0.1</version>
</plugin>

You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-javadoc-plugin/download.cgi

Release Notes – Apache Maven JavaDoc Plugin – Version 3.0.1

Bugs:

MJAVADOC-427 – “Error fetching URL” for valid non-Java API links
MJAVADOC-504 – NullPointerException in JavadocUtil.getJavaHome() when JAVA_HOME isn’t set
MJAVADOC-512 – Even when 1.8.0 matches there still is a warning.
MJAVADOC-517 – NPE under Java 10 RC

Improvements:

MJAVADOC-487 – Follow redirects
MJAVADOC-508 – Option to fail in case of javadoc warning

Dependency upgrades:

MJAVADOC-515 – Upgrade parent to 31
MJAVADOC-520 – Upgrade plexus-utils/qdox/plexus-archiver/
MJAVADOC-521 – Add documentation information for GitHub

Enjoy,

-The Apache Maven team

The Apache News Round-up: week ending 1 June 2018

Sally — Fri, 1 Jun 2018 15:45:30 +0000

Welcome, June! The Apache community is wrapping up the week with the following activities:

ASF Sponsorship –individual donors and corporate sponsors who support the ASF.
- The Apache^® Software Foundation Announces Added Support by Oath to Help Apache Infrastructure https://s.apache.org/eTNY

ApacheCon™ –the ASF's official global conference series.
- 11-14 June: Apache Roadshow Europe/Berlin --event within FOSS Backstage https://foss-backstage.de/
- 24-27 September: ApacheCon North America/Montreal http://apachecon.com/acna18/
- 8 October: Apache Roadshow and Open Source Job Fair/Fairfax, VA --Save The Date!

ASF Infrastructure –our distributed team on three continents keeps the ASF's infrastructure running around the clock.
- 7M+ weekly checks yield thriving performance at 98.87% uptime. http://status.apache.org/

ASF Operations Factoid –this week, 517 Apache contributors changed 1,105,368 lines of code over 3,240 commits. Top 5 contributors, in order, are: Zhang Duo, Gary Gregory, Stephen Mallette, Jesus Camacho Rodriguez, and Willem Jiang.

Apache Flink™ –an Open Source stream processing framework for distributed, high-performing, always-available, and accurate data streaming applications.
- Apache Flink 1.5.0 released https://flink.apache.org/

Apache Groovy™ –a multi-facet programming language for the JVM.
- Apache Groovy 2.5.0 released http://groovy-lang.org/

Apache Ignite™ –a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale.
- Apache Ignite 2.5.0 released https://ignite.apache.org/

Apache Jackrabbit™ Oak – a scalable, high-performance hierarchical content repository designed for use as the foundation of modern world-class Web sites and other demanding content applications.
- Apache Jackrabbit Oak 1.6.12 released http://jackrabbit.apache.org/

Apache NetBeans (incubating) –a full IDE for Java SE development.
- Apache NetBeans incubating 9.0 RC1 released https://netbeans.apache.org/

Apache OpenMeetings™ –provides video conferencing, instant messaging, white board, collaborative document editing and other groupware tools using API functions of the Red5 Streaming Server for Remoting and Streaming.
- Apache OpenMeetings 4.0.4 released http://openmeetings.apache.org/

Apache Pulsar (incubating) –a highly scalable, low latency messaging platform running on commodity hardware.
- Apache Pulsar 2.0.0-rc1-incubating released https://pulsar.incubator.apache.org/

Apache Qpid™ Proton –a messaging library for the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org).
- Apache Qpid Proton 0.23.0 released http://qpid.apache.org

Did You Know?

- Did you know that project-specific tracks and dedicated events co-located at ApacheCon North America include CloudStack Collaboration, Geospatial track, and TomcatCon? http://apachecon.com/acna18/

- Did you know that Apache Ignite v2.5 scales to thousands-nodes clusters to meet the demands of massive mission-critical deployments? https://ignite.apache.org/

- Did you know that Amazon Web Services' Neptune uses Apache Tinkerpop graph computing framework? http://superset.incubator.apache.org/

Apache Community Notices:

- The Apache Software Foundation Celebrates 19 Years of Open Source Leadership "The Apache Way" https://s.apache.org/gK4Q

- Read "Open – For Business – At the ASF" by Merv Adrian, VP Research at Gartner https://blogs.gartner.com/merv-adrian/2018/03/27/open-for-business-at-the-asf/

- The Apache Software Foundation 2018 Vision Statement https://s.apache.org/zqC3

- Apache in 2017 - By The Digits https://s.apache.org/h8do

- Foundation Statement –Apache Is Open. https://s.apache.org/PIRA

- "Success at Apache" focuses on the processes behind why the ASF "just works". https://blogs.apache.org/foundation/category/SuccessAtApache

- Please follow/like/re-tweet the ASF on social media: @TheASF on Twitter and on LinkedIn at https://www.linkedin.com/company/the-apache-software-foundation

- Do friend and follow us on the Apache Community Facebook page https://www.facebook.com/ApacheSoftwareFoundation/and Twitter account https://twitter.com/ApacheCommunity

- The list of Apache project-related MeetUps can be found at http://apache.org/events/meetups.html

- Open Expo Europe - 6-7 June 2018 in Madrid https://openexpoeurope.com/

- We're teaming up the Apache Roadshow Europe with Berlin Buzzwords - 10-12 June 2018 (Apache Lounge dates: 11-12 June) https://berlinbuzzwords.de/

- The 2018 Apache EU Roadshow will be held during FOSS Backstage in Berlin 13-14 June 2018 https://foss-backstage.de/

- Apache Big Data project communities will be participating at DataWorks Summit 17-21 June 2018 in San Jose https://dataworkssummit.com/

- ApacheCon North America will be held 24-27 September in Montreal http://apachecon.com/

- Save the Date: Apache Roadshow DC and Open Source/Government/Cyber/Job Fair - 8 October 2018 in Fairfax, VA http://apachecon.com/

- ASF Quarterly Report: Operations Summary: November 2017 - January 2018 https://s.apache.org/UtBD

- ASF Annual Report is available at https://s.apache.org/FY2017AnnualReport

- Are your software solutions Powered by Apache? Download & use our "Powered By" logos http://www.apache.org/foundation/press/kit/#poweredby

= = =

# # #

Apache Ignite 2.5: Scaling to 1000s Nodes Clusters

Denis Magda — Thu, 31 May 2018 22:17:35 +0000

Apache Ignite was always appreciated by its users for two primary things it delivers - scalability and performance. Throughout the lifetime many distributed systems tend to do performance optimizations from a release to release while making scalability related improvements just a couple of times. It's not because the scalability is of no interest. Usually, scalability requirements are set and solved once by a distributed system and don't require significant additional interventions by engineers.

However, Apache Ignite grew to the point when the community decided to revisit its discovery subsystem that influences how well and far Ignite scales out. The goal was pretty clear - Ignite has to scale to 1000s of nodes as good as it scales to 100s now.

It took many months to get the task implemented. So, please join me in welcoming Apache Ignite 2.5 that now can be scaled easily to 1000s of nodes and goes with other exciting capabilities. Let's check out the most prominent ones.

Massive Scalability

There are two components of Ignite that were modified in Ignite 2.5 to improve its scalability capabilities. The first one is related to 1000s nodes clusters while the other is related to the way we train machine learning (ML) models in Ignite. Let's start with the first.

Marrying Apache Ignite and ZooKeeper

Right, that 1000s nodes scalability goal was solved with the help of Apache ZooKeeper. Why did we turn to it?

Apache Ignite default TCP/IP Discovery organizes cluster nodes into a ring-topology form that has its advantages and disadvantages. For instance, on topologies with hundreds of cluster nodes, it can take many seconds why a system message traverse through all the nodes. As a result, necessary processing of events such as joining of new nodes or detecting of failed ones can take a while affecting overall cluster responsiveness and performance. That is a big deal if you'd like to run 1000s nodes clusters.

The new ZooKeeper Discovery uses ZooKeeper as a single point of synchronization where Ignite nodes are exchanging discovery events through it. It solved the issue with long-to-be-processed discovery messages and, as a result, allowed Ignite scaling to large cluster topologies.

As a rule of thumb, keep using default TCP/IP Discovery if it's unlikely that your Ignite cluster scales beyond 300s nodes and switch to ZooKeeper Discovery if that's the case.

Machine Learning: Partition-Based Datasets

That's the second prominent feature of Ignite 2.5 that improves the way of how far you can scale your Ignite clusters to train ML models over terabytes or petabytes of data. The partition-based datasets moved us closer to the implementation of Zero-ETL concept which implies that Ignite can be used as a single storage where ML models and algorithms are being improved iteratively and online without ETLing data back and forth between Ignite and another storage.

Read more about the datasets from this documentation page.

Genetic Algorithms

Ignite's ML component is ramping up and in the version 2.5 it accepted a contribution of genetic algorithms (GAs) which help to solve optimization problems by simulating the process of biological evolution. GAs are excellent for searching through large and complex data sets for an optimal solution. Real world applications of GAs include automotive design, computer gaming, robotics, investments, traffic/shipment routing and more.

Refer to excessive articles of my community-mates Turik Campbell and Akmal B. Chaudhri which cover main benefits of GAs:

Travel Like MacGyver: Solve Knapsack Problem with GA Grid

Genetic Algorithms with Apache® Ignite

Continuous Self-Healing and Consistency Checks

It's a known fact that many companies and businesses trusted Ignite its mission-critical deployments and solutions. As a result, sometimes Ignite doesn't even have a right to "misfire" and should be able to handle critical or unpredictable situations automatically or provide facilities to do deal with them manually.

With Ignite 2.5, we've kicked off the realization of continuous self-healing concept that implies that no matter what happens with Ignite in production it should be able to tolerate unexpected failures and stay up and running. The following was done in 2.5:

Critical Failures Handling

Long running transactions monitoring and termination

Data Consistency Check Facilities

SQL: Security and Fast Data Loading

The community stays strong and determined in its goal of making Ignite SQL engine undistinguishable from SQL engines of famous and mature SQL database. What's the purpose? We want to make it easy for you to migrate from a relational database to Ignite, so that you can reuse all your skills gained before. Overall, this is what our SQL engine got in 2.5:

Fast data loading with COPY command and streaming mode using SQL APIs.

Long running transactions monitoring and termination

Secured Ignite cluster. Use CREATE USER, DROP USER and ALTER USER commands to manage who is allowed to connect to your clusters.

In-place Execution of Spark DataFrame Queries

Apache Spark users can applaud because the following ticket got merged in 2.5. In short, it means that from now on Ignite will be able to execute as many DataFrames SQL queries as it can in-place on Ignite servers side avoiding data movement from Ignite to Spark. The performance of your DataFrames queries should boost significantly. Enjoy!

DEB and RPM packages

Last but not least, if you're a Linux user, now you can install the latest Ignite versions directly from DEB and RPM repositories. Refer to how-to and share your feedback with us.

Finally, I have no more paper left to cover other optimizations and improvements. So, go ahead and check out our release notes.

The Apache® Software Foundation Announces Added Support by Oath to Help Apache Infrastructure

Sally — Thu, 31 May 2018 13:00:27 +0000

Augments ASF Platinum Sponsorship with Targeted Sponsorship at the Platinum Level

Wakefield, MA —31 May 2018— The Apache^® Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of more than 350 Open Source projects and initiatives, announced today expanded support provided by Oath, a long-term ASF Platinum Sponsor.

Oath, a subsidiary of Verizon, reaches over one billion people around the world with a house of brands including Yahoo, AOL, HuffPost, TechCrunch, Tumblr, and more. Oath is an active Apache community supporter, and, through its brands, has a long history of technical excellence and leadership in Open Source. In particular, Yahoo engineers have made significant contributions to numerous Apache projects, including Hadoop, Storm, Spark, HBase, Oozie, Hive, Pig, Tez, Zookeeper, Bookkeeper, and Traffic Server. Dozens of Oath employees are recognized Apache Committers, many of whom have been and continue to be elected as ASF Members, serve on Project Management Committees (PMCs), and chair PMCs.

The ASF recently announced its new Targeted Sponsors, who provide the Foundation with contributions for specific activities or programs, such as donating cloud services, funding a project hackathon, providing legal services, offering community member benefits, underwriting expenses for ApacheCon, as well as other means of supporting the ASF.

In addition to Oath's Platinum-level sponsorship of the ASF, the company is helping boost the efforts of the ASF's infrastructure team by donating colocation space, machines, and onsite technical support.

"As dedicated ASF participants who have benefitted from and given back to the community, we know how important the Foundation’s work is to the advancement of technology for all," said Mark Holderbaugh, VP of software development at Oath. "Our multipronged support is a declaration of the Foundation's value and we are very pleased to continue to lend our expertise and resources to further The Apache Way."

"ASF Sponsors such as Oath help us run our day-to-day operations," said Phil Steitz, ASF Chairman. "Targeted Sponsorships allows us the ability to provide support in additional areas of need. Each day, more than 300 Apache projects and their communities rely on build services that are maintained by the ASF Infrastructure Team. The generosity provided by Oath helps us expand our infrastructure services beyond continuous integration and testing, to enable automated website generation and more. Their efforts, in turn, help our community at-large, and benefit the billions of Apache users around the world."

The ASF Infrastructure Team is distributed across three continents, and keeps the Foundation's services running 24x7x365 at near 100% uptime at less than US$5,000 per project. As the ASF is a purely virtual organization, it does not have offices or buildings; its only physical existence is the technical infrastructure that enables it to operate. For performance statistics that reflect 7M+ weekly checks and project mail volume across 1,131 lists, visit http://status.apache.org/

About Oath

Oath, a subsidiary of Verizon, is a values-led company committed to building brands people love. Oath reaches one billion people around the world with a dynamic house of media and technology brands. A global leader in digital and mobile, Oath is shaping the future of media and technology. For more on Oath, visit www.oath.com.

About The Apache Software Foundation (ASF)

Established in 1999, the all-volunteer Foundation oversees more than 350 leading Open Source projects, including Apache HTTP Server --the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 730 individual Members and 6,800 Committers across six continents successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(c)(3) charitable organization, funded by individual donations and corporate sponsors including Aetna, Anonymous, ARM, Bloomberg, Budget Direct, Capital One, Cerner, Cloudera, Comcast, Facebook, Google, Hortonworks, Huawei, IBM, Indeed, Inspur, LeaseWeb, Microsoft, Oath, ODPi, Pineapple Fund, Pivotal, Private Internet Access, Red Hat, Target, and Union Investment. For more information, visit http://www.apache.org/ and https://twitter.com/TheASF

© The Apache Software Foundation. "Apache", "Apache HTTP Server", and "ApacheCon" are registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. All other brands and trademarks are the property of their respective owners.

# # #

MEDIA CONTACTS:

Sally Khudairi

Vice President

The Apache Software Foundation

+1 617 921 8656

press@apache.org

Mike Sefanov

Corporate Communications, Technology

Oath

+1 650 281 8099

sefanov@oath.com

Announcing Apache JSPWiki 2.10.4

Dave Koelmeyer — Thu, 31 May 2018 10:59:05 +0000

We're pleased to announce the availability of Apache JSPWiki version 2.10.4. Following are the notable changes included in this release.

Improvements to the Haddock template

Haddock is JSPWiki's next generation template. Building on the huge number of new features shipped in 2.10.3, changes in 2.10.4 include a floating editing toolbar (JSPWIKI-1058). This is especially useful when editing long pages, as the toolbar is always visible without having to scroll to the top of the page:

Work is also continuing to improve support for mobile devices (JSPWIKI-835), and a new favicon has been added.

Fixes for ACLs

JSPWIKI-1039 – ACLs are not taken into account when cache is disabled
JSPWIKI-1047 – Access Control Lists do not work if page cache is deactivated
JSPWIKI-1067 – View-only ACLs are not enforced

Other fixes

JSPWiki 2.10.4 corrects German language translation errors, and a rendering cache fix.

For more information

For a full list of changes see the ChangeLog file or our issue tracker.

The release is available for download at:

http://www.apache.org/dyn/closer.cgi/jspwiki/

JSPWiki Maven artifacts are available under org.apache.jspwiki groupId, version 2.10.4

All JSPWiki site administrators are encouraged to update. To get involved, visit the project website at http://jspwiki.apache.org. For feedback, help, and developer queries please visit us on the mailing lists.

Groovy 2.5 CliBuilder Renewal

Remko Popma — Wed, 30 May 2018 11:39:52 +0000

The CliBuilder class for quickly and concisely building command line applications has been renewed in Apache Groovy 2.5. This article highlights what is new.

The `groovy.util.CliBuilder` Class is Deprecated

Previous versions of CliBuilder used Apache Commons CLI as the underlying parser library. From Groovy 2.5, there is an alternative version of CliBuilder based on the picocli parser.

It is recommended that applications explicitly import either groovy.cli.picocli.CliBuilder or groovy.cli.commons.CliBuilder. The groovy.util.CliBuilder class is deprecated and delegates to the Commons CLI version for backwards compatibility.

New features will likely only be added to the picocli version, and groovy.util.CliBuilder may be removed in a future version of Groovy. The Commons CLI version is intended for applications that rely on the internals of the Commons CLI implementation of CliBuilder and cannot easily migrate to the picocli version.

Next, let’s look at some new features in Groovy 2.5 CliBuilder.

Typed Options

Options can be boolean flags or they can take one or more option parameters. In previous versions of CliBuilder, you would have to specify args: 1 for options that need a parameter, or args: '+' for options that accept multiple parameters.

This version of CliBuilder adds support for typed options. This is convenient when processing parse results, but additionally, the number of arguments is inferred from the type, so if the type is specified, args can be omitted.

For example:

def cli = new CliBuilder()
cli.a(type: String, 'a-arg')
cli.b(type: boolean, 'b-arg')
cli.c(type: Boolean, 'c-arg')
cli.d(type: int, 'd-arg')
cli.e(type: Long, 'e-arg')
cli.f(type: Float, 'f-arg')
cli.g(type: BigDecimal, 'g-arg')
cli.h(type: File, 'h-arg')
cli.i(type: RoundingMode, 'i-arg')

def argz = '''-a John -b -d 21 -e 1980 -f 3.5 -g 3.14159
    -h cv.txt -i DOWN and some more'''.split()

def options = cli.parse(argz)
assert options.a == 'John'
assert options.b
assert !options.c
assert options.d == 21
assert options.e == 1980L
assert options.f == 3.5f
assert options.g == 3.14159
assert options.h == new File('cv.txt')
assert options.i == RoundingMode.DOWN
assert options.arguments() == ['and', 'some', 'more']

Supported Types

The Commons CLI-based CliBuilder supports primitives, numeric types, files, enums and arrays thereof (using StringGroovyMethods#asType(String, Class)). The picocli-based CliBuilder supports those and more.

Adding More Types

If the built-in types don’t meet your needs, it is easy to register a custom converter. Specify a convert Closure to convert the String argument to any other type. For example:

import java.nio.file.Paths
import java.time.LocalTime

def cli = new CliBuilder()
cli.a(convert: { it.toUpperCase() }, 'a-arg')    // (1)
cli.p(convert: { Paths.get(it) }, 'p-arg')       // (2)
cli.t(convert: { LocalTime.parse(it) }, 't-arg') // (3)

def options = cli.parse('-a abc -p /usr/home -t 15:31:59'.split())
assert options.a == 'ABC'
assert options.p.absolute && options.p.parent == Paths.get('/usr')
assert options.t.hour == 15 && options.t.minute == 31

1	Convert one String to another
2	Option value is converted to a `java.nio.file.Path`
3	Option value is converted to a `java.time.LocalTime`

Annotations

From this release, Groovy offers an annotation API for processing command line arguments.

Applications can annotate fields or methods with @groovy.cli.Option for named options or @groovy.cli.Unparsed for positional parameters. When the parser matches a command line argument with an option name or positional parameter, the value is converted to the correct type and injected into the field or method.

Annotating Methods of an Interface

One way to use the annotations is on "getter-like" methods (methods that return a value) of an interface. For example:

import groovy.cli.*

interface IHello {
    @Option(shortName='h', description='display usage') Boolean help()   // (1)
    @Option(shortName='u', description='user name')     String user()    // (2)
    @Unparsed(description = 'positional parameters')    List remaining() // (3)
}

1	Method returns `true` if `-h` or `--help` was specified on the command line.
2	Method returns the parameter value that was specified for the `-u` or `--user` option.
3	Any remaining parameters will be returned as a list from this method.

How to use this interface (using the picocli version to demonstrate its usage help):

import groovy.cli.picocli.CliBuilder

def cli = new CliBuilder(name: 'groovy Greeter')
def argz = '--user abc'.split()
IHello hello = cli.parseFromSpec(IHello, argz)
assert hello.user() == 'abc'

hello = cli.parseFromSpec(GreeterI, ['--help', 'Some', 'Other', 'Args'] as String[])
assert hello.help()
cli.usage()
assert hello.remaining() == ['Some', 'Other', 'Args']

This prints the following usage help message:

Usage: groovy Greeter [-h] [-u=<user>] [<remaining>...]
      [<remaining>...]   positional parameters
  -u, --user=<user>      user name
  -h, --help             display usage

When parseFromSpec is called, CliBuilder reads the annotations, parses the command line arguments and returns an instance of the interface. The interface methods return the option values matched on the command line.

Annotating Properties or Setter Methods of a Class

Another way to use the annotations is on the properties or "setter-like" methods (void methods with a single parameter) of a class. For example:

class Hello {
    @Option(shortName='h', description='display usage') // (1)
    Boolean help

    private String user
    @Option(shortName='u', description='user name')     // (2)
    void setUser(String user) {
        this.user = user
    }
    String getUser() { user }

    @Unparsed(description = 'positional parameters')    // (3)
    List remaining
}

1	The `help` Boolean property is set to `true` if `-h` or `--help` was specified on the command line.
2	The `setUser` property setter method is invoked with the `-u` or `--user` option parameter value.
3	The `remaining` property is set to a new `List` containing the remaining args, if any.

The annotated class can be used as follows:

String[] argz = ['--user', 'abc', 'foo']

def cli = new CliBuilder(usage: 'groovy Greeter [option]') // (1)
Hello greeter = cli.parseFromInstance(new Hello(), argz)   // (2)
assert greeter.user == 'abc'                               // (3)
assert greeter.remaining == ['foo']                        // (4)

1	Create a `CliBuilder` instance.
2	Extract options from the annotated instance, parse arguments, and populate and return the supplied instance.
3	Verify that the String option value has been assigned to the property.
4	Verify the remaining arguments property.

When parseFromInstance is called, CliBuilder again reads the annotations, parses the command line arguments and finally returns the instance. The annotated fields and setter methods are initialized with the values matched for the associated option.

Script Annotations

Groovy 2.5 also offers new annotations for Groovy scripts.

@OptionField is equivalent to combining @groovy.transform.Field and @Option, whereas @UnparsedField is equivalent to combining @Field and @Unparsed.

Use these annotations to turn script variables into fields so that the variables can be populated by CliBuilder. For example:

import groovy.cli.OptionField
import groovy.cli.UnparsedField

@OptionField String user
@OptionField Boolean help
@UnparsedField List remaining

String[] argz = ['--user', 'abc', 'foo']

new CliBuilder().parseFromInstance(this, argz)
assert user == 'abc'
assert remaining == ['foo']

Typed Positional Parameters

This version of CliBuilder offers some limited support for strongly typed positional parameters.

If all positional parameters have the same type, the @Unparsed annotation can be used with an array type other than String[]. Again, the type conversion is done using StringGroovyMethods#asType(String, Class) in the Commons CLI version, while the picocli version of CliBuilder supports a superset of those types.

This functionality is only available for the annotations API, not for the dynamic API. Here is an example of an interface that can capture strongly typed positional parameters:

interface TypedPositionals {
    @Unparsed Integer[] nums()
}

The code below demonstrates the type conversion:

def argz = '12 34 56'.split()
def cli = new CliBuilder()
def options = cli.parseFromSpec(TypedPositionals, argz)
assert options.nums() == [12, 34, 56]

Apache Commons CLI Features

Sometimes you may want to use advanced features of the underlying parsing library. For example, you may have a command line application with mutually exclusive options. The below code shows how to achieve this using the Apache Commons CLI OptionGroup API:

import groovy.cli.commons.CliBuilder
import org.apache.commons.cli.*

def cli = new CliBuilder()
def optionGroup = new OptionGroup()
optionGroup.with {
  addOption cli.option('s', [longOpt: 'silent'], 's option')
  addOption cli.option('v', [longOpt: 'verbose'], 'v option')
}
cli.options.addOptionGroup optionGroup

assert !cli.parse('--silent --verbose'.split()) (1)

1	Parsing this input will fail because two mutually exclusive options were specified.

Picocli CliBuilder Features

Strongly Typed Lists

Options with multiple values often use an array or a List to capture the values. Arrays can be strongly typed, that is, contain elements other than String. The picocli version of CliBuilder lets you do the same with Lists. The auxiliaryType specifies the type that the elements should be converted to. For example:

import groovy.cli.picocli.CliBuilder

def cli = new CliBuilder()
cli.T(type: List, auxiliaryTypes: Long, 'typed list')  // (1)

def options = cli.parse('-T 1 -T 2 -T 3'.split())      // (2)
assert options.Ts == [ 1L, 2L, 3L ]                    // (3)

1	Define an option that can have multiple integer values.
2	An example command line.
3	The option values as a `List<Integer>`.

Strongly Typed Maps

The picocli version of CliBuilder offers native support for Map options. This is as simple as specifying Map as the option type. By default, both keys and values are stored as Strings in the Map, but it’s possible to use auxiliaryType to specify the types that the keys and values should be converted to.

import groovy.cli.picocli.CliBuilder

def cli = new CliBuilder()
cli.D(args: 2,   valueSeparator: '=', 'Commons CLI style map')                 // (1)
cli.X(type: Map, 'picocli style map support')                                  // (2)
cli.Z(type: Map, auxiliaryTypes: [TimeUnit, Integer].toArray(), 'typed map')   // (3)

def options = cli.parse('-Da=b -Dc=d -Xx=y -Xi=j -ZDAYS=2 -ZHOURS=23'.split()) // (4)
assert options.Ds == ['a', 'b', 'c', 'd']                                      // (5)
assert options.Xs == [ 'x':'y', 'i':'j' ]                                      // (6)
assert options.Zs == [ (DAYS as TimeUnit):2, (HOURS as TimeUnit):23 ]          // (7)

1	Commons CLI has map-like options by specifying that each option must have two parameters, with some separator.
2	The picocli version of CliBuilder has native support for Map options.
3	The key type and value type can be specified for strongly-typed maps.
4	An example command line.
5	The Commons CLI style option gives a list of [key, value, key, value, …] objects.
6	The picocli style option gives the result as a `Map<String, String>`.
7	When `auxiliaryTypes` are specified, the keys and values of the map are converted to the specified types, giving you a `Map<TimeUnit, Integer>`.

Usage Help with Detailed Synopsis

CliBuilder has always supported a usage property to display the usage help synopsis of a command:

// the old way
new CliBuilder(usage: 'myapp [options]').usage()

The above program prints:

Usage: myapp [options]

This still works, but the picocli version has a better alternative with the name property. If you specify name instead of usage, picocli will show all options in a succinct synopsis with square brackets [ and ] for optional elements and ellipsis … for elements that can be repeated one or more times. For example:

def cli = new CliBuilder(name: 'myapp') // detailed synopsis
cli.a('option a description')
cli.b('option b description')
cli.c(type: List, 'option c description')
cli.usage()

The above program prints:

Usage: myapp [-ab] [-c=PARAM]...
the new way
  -a           option a description
  -b           option b description
  -c= PARAM    option c description

Use Any Option Names

Image credit: (c) PsychoShadow - www.bigstockphoto.com

Before, if an option had multiple names with a single hyphen, you had no choice but to declare the option multiple times:

// before: split -cp, -classpath into two options
def cli = new CliBuilder(usage: 'groovyConsole [options] [filename]')
cli.classpath('Where to find the class files')
cli.cp(longOpt: 'classpath', 'Aliases for '-classpath')

The picocli version of CliBuilder supports a names property that can have any number of option names that can take any prefix. For example:

// after: an option can have many names with any prefix
def cli = new CliBuilder(usage: 'groovyConsole [options] [filename]')
cli._(names: ['-cp', '-classpath', '--classpath'], 'Where to find the class files')

Fine-grained Usage Help Message

Picocli offers fine-grained control over the usage help message format and this functionality is exposed via the usageMessage CliBuilder property.

The usage message has a number of sections: header, synopsis, description, parameters, options and finally the footer. Each section has a heading, that precedes the first line of its section. For example:

import groovy.cli.picocli.CliBuilder

def cli = new CliBuilder()
cli.name = "groovy clidemo"
cli.usageMessage.with {                // (1)
    headerHeading("Header heading:%n") // (2)
    header("header 1", "header 2")     // (3)
    synopsisHeading("%nUSAGE: ")
    descriptionHeading("%nDescription heading:%n")
    description("description 1", "description 2")
    optionListHeading("%nOPTIONS:%n")
    footerHeading("%nFooter heading:%n")
    footer("footer 1", "footer 2")
}
cli.a(longOpt: 'aaa', 'a-arg')         // (4)
cli.b(longOpt: 'bbb', 'b-arg')
cli.usage()

1	Use the `usageMessage` CliBuilder property to customize the usage help message.
2	Headings can contain string format specifiers like the `%n` newline.
3	Sections are multi-line: each string will be rendered on a separate line.
4	Define some options.

This prints the following output:

Header heading:
header 1
header 2

USAGE: groovy clidemo [-ab]

Description heading:
description 1
description 2

OPTIONS:
  -a, --aaa    a-arg
  -b, --bbb    b-arg

Footer heading:
footer 1
footer 2

Usage Help with ANSI Colors

Out of the box, the command name, option names and parameter labels in the usage help message are rendered with ANSI styles and colors. The color scheme for these elements can be configured with system properties.

Other than that, you can use colors and styles in the descriptions and other sections of the usage help message, using a simple markup notation. The example below demonstrates:

def cli = new groovy.cli.picocli.CliBuilder(name: 'myapp')
cli.usageMessage.with {
    headerHeading("@|bold,red,underline Header heading|@:%n")
    header($/@|bold,green \
  ___ _ _ ___      _ _    _
 / __| (_) _ )_  _(_) |__| |___ _ _
| (__| | | _ \ || | | / _` / -_) '_|
 \___|_|_|___/\_,_|_|_\__,_\___|_|
|@/$)
    synopsisHeading("@|bold,underline Usage|@: ")
    descriptionHeading("%n@|bold,underline Description heading|@:%n")
    description("Description 1", "Description 2")      // after the synopsis
    optionListHeading("%n@|bold,underline Options heading|@:%n")
    footerHeading("%n@|bold,underline Footer heading|@:%n")
    footer($/@|bold,blue \
   ___                         ___   ___
  / __|_ _ ___  _____ ___  _  |_  ) | __|
 | (_ | '_/ _ \/ _ \ V / || |  / / _|__ \
  \___|_| \___/\___/\_/ \_, | /___(_)___/
                        |__/             |@/$)
}
cli.a('option a description')
cli.b('option b description')
cli.c(type: List, 'option c description')
cli.usage()

The code above gives the following output:

(Credit to http://patorjk.com/software/taag/ for the ASCII art.)

New `errorWriter` Property

When the user provided invalid input, the picocli version of CliBuilder writes an error message and the usage help message to the new errorWriter property (set to System.err by default). When the user requests help, and the application calls CliBuilder.usage(), the usage help message is printed to the writer property (System.out by default).

Previous versions of CliBuilder used the writer property for both invalid input and user-requested help.

Why this change? This helps command line application authors to follow standard practice and separate diagnostic output from the program output: If the output of a Groovy program is piped to another program, sending error messages to STDERR prevents the downstream program from inadvertently trying to parse error output. On the other hand, when users request help with --help or --version, the output should be sent to STDOUT, because the user may want to pipe the output to a utility like less or grep.

For backwards compatibility, setting the writer property to another value will also set the errorWriter to the same value. (You can still set the errorWriter to another value afterwards if desired.)

Gotchas/Incompatibilities

There are a few areas where the new versions of CliBuilder are not compatible with previous versions or with each other.

Properties `options` and `formatter` Unavailable in Picocli Version

The Commons CLI version of CliBuilder, and previous versions of CliBuilder, expose an options property of type org.apache.commons.cli.Options, that can be used to configure the underlying Commons CLI parser without going through the CliBuilder API. This property is not available in the picocli version of CliBuilder. Applications that read or write this property must import groovy.cli.commons.CliBuilder or modify the application.

Additionally, the formatter property of type org.apache.commons.cli.HelpFormatter is not available in the picocli version of CliBuilder. If your application uses this property, consider using the usageMessage property instead, or import groovy.cli.commons.CliBuilder.

Property `parser` Differs in Picocli and Commons CLI Versions

The picocli version of CliBuilder has a parser property that exposes a picocli.CommandLine.Model.ParserSpec object that can be used to configure the parser behavior.

The Commons CLI version of CliBuilder, and previous versions of CliBuilder, expose a parser property of type org.apache.commons.cli.CommandLineParser. This functionality is not available in the picocli version of CliBuilder.

If your application uses the parser property to set a different Commons CLI parser, consider using the posix property instead, or import groovy.cli.commons.CliBuilder.

Different Parser Behavior for `longOption`

The Commons CLI DefaultParser recognizes longOption option names prefixed with a single hypen (e.g., -option) as well as options prefixed with a double hyphen (e.g., --option). This is not always obvious since the usage help message only shows the double hyphen prefix for longOption option names.

For backwards compatibility, the picocli version of CliBuilder has an acceptLongOptionsWithSingleHyphen property: set this property to true if the parser should recognize long option names with both a single hyphen and a double hyphen prefix. The default is false, so only long option names with a double hypen prefix (--option) are recognized.

Conclusion

Groovy 2.5 CliBuilder offers a host of exciting new features. Try it out and let us know what you think!

For reference: Groovy site and GitHub project, picocli site and picocli GitHub project. Please star the projects if you like what you see!

A copy of this article was previously published on the picocli web site. See the original article here.

[ANNOUNCE] Apache Groovy 2.5.0 released

Remko Popma — Wed, 30 May 2018 11:28:57 +0000

[ANNOUNCE] Apache Groovy 2.5.0 released

Dear community,

The Apache Groovy team is pleased to announce version 2.5.0 of Apache Groovy! Apache Groovy is a multi-facet programming language for the JVM. Further details can be found at the http://groovy.apache.org website.

We are sure you'll enjoy the features in this new version of Groovy. Your feedback on any unintentional glitches is welcome.

This release includes 12 bug fixes/improvements since the last RC as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12343341

The full list of over 300 bug fixes/improvements since 2.4 can be found here: http://groovy-lang.org/changelogs/changelog-2.5.0.html

The full release notes can be found here: http://groovy-lang.org/releasenotes/groovy-2.5.html

Sources, convenience binaries, downloadable documentation and an SDK bundle can be found at: http://www.groovy-lang.org/download.html We recommend you verify your installation using the information on that page.

Jars are also available within the major binary repositories.

We welcome your help and feedback and in particular want to thank everyone who contributed to this release.

For more information on how to report problems, and to get involved, visit the project website at https://groovy.apache.org/

Best regards,

The Apache Groovy team.

[ANNOUNCE] Apache NetBeans (incubating) 9.0 RC1 released

Geertjan — Tue, 29 May 2018 13:22:41 +0000

The Apache NetBeans team is proud to announce the release of Apache NetBeans (incubating) 9.0 RC1.

Apache NetBeans (incubating) 9.0 RC1 constitutes all the modules in the 'release90' branch of the Apache NetBeans Git repo (https://github.com/apache/incubator-netbeans), which together provide the NetBeans Platform (i.e., the underlying application framework), which was released as Apache NetBeans 9.0 Alpha (incubating), as well as all the modules that provide the Java SE-related features of Apache NetBeans. In short, Apache NetBeans (incubating) 9.0 RC1 is a full IDE for Java SE development.

Get it and read more on our download page:

https://netbeans.apache.org/download/nb90/nb90-rc1.html

Details on Apache NetBeans (incubating) 9.0 RC1, including a list of open issues to be resolved prior to the final release:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+RC1

What must be done for the final version of Apache NetBeans (incubating) 9.0 to be released?

1. The items in the link above need to be fixed, e.g, new splash screen needs to be integrated.
2. Cherry picking of pull requests merged into 'main' for 'release90' branch.
3. Put together rc2 release, sanity test it via NetCAT, and publish it.
4. Community Acceptance survey.
5. Start Apache voting for the final release, incorporating input from the Community Acceptance survey.
6. Release 9.0, which will be an IDE for Java SE development only, the other features have not been donated yet by Oracle and are being audited and processed and be part of subsequent releases of Apache NetBeans.

Take note of the Apache NetBeans release criteria:

https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+9.0+Release+Criteria

FYI, see the below for the donation status of features that have not been donated to Apache yet, e.g., features for working with Java EE, JavaScript, PHP, C/C++, and more:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition

Work is being done on bringing netbeans.org to Apache. We already have our Apache site set up, here:

https://netbeans.apache.org

On behalf of the Apache NetBeans PPMC

Geertjan

Apache Maven SCM Version 1.10.0 Released

khmarbaise — Mon, 28 May 2018 17:01:42 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven SCM, version 1.10.0.

Maven SCM supports Maven 2.x plugins (e.g. maven-release-plugin) and other tools (e.g. Continuum) by providing them with a common API for doing SCM operations. You can look at the list of SCMs for more information on using Maven SCM with your favorite SCM tool.

Release Notes – Maven SCM Version 1.10.0

Bugs:

SCM-763 – Password masking for svnexe does not handle all cases
SCM-797 – gitexe checkIn() fails due to Windows command line length limitation
SCM-814 – Dead links on Maven SCM plugin usage page and Maven SCM Providers Matrix page
SCM-818 – Updating doesn’t work when in detached HEAD
SCM-821 – fix incorrect resolving of branch name from HG outgoing changes && NPE in HgUtils.differentOutgoingBranchFound
SCM-829 – CommandParameter incorrectly removed from parameter list
SCM-836 – scm:bootstrap throws NPE
SCM-846 – userInfo in Git HTTP URLs not escaped according to RFC 3986
SCM-862 – apache-rat complains about Eclipse .checkstyle files
SCM-863 – NPE in GlobalOptions.setCVSRoot(null) with newer cvsclient
SCM-865 – cvsnt: rls: invalid option — d
SCM-866 – Cvs ScmProvider.list() does not return correct entries
SCM-867 – ScmWagon has no way to work with CVS and SVN in binary mode
SCM-868 – gitexe add() does not return added files when invoked in subdir
SCM-869 – gitexe list() implemented incorrectly
SCM-874 – ScmResult output password masking does not handle multiline text
SCM-875 – GitUpdateCommand assumes master branch by default
SCM-878 – AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
SCM-879 – JazzChangeLogCommandTest#testListChangesetConsumerWithTimeOnly() fails with NPE on Java 10
SCM-881 – ScmWagon has no way to work with SVN in binary mode
SCM-882 – ScmWagon has no way to work with GIT in binary mode
SCM-886 – Tests with checkin rely on global git config
SCM-887 – Plexus Utils 3.0.24 makes some tests fail
SCM-888 – Changelog generation fails on Windows with Mercurial SCM

Improvements:

SCM-739 – Release Plugin: Use “git —depth 1” When Checking Out
SCM-748 – Automatically create parent dirs with ‘svn —parents’
SCM-855 – Upgrade to Java 7
SCM-873 – Improve documentation on svn-settings.xml and git-settings.xml
SCM-884 – Upgrade jgit to last version of java 7 release (4.5.0.201609210915-r)
SCM-885 – Extend GitChangeLogCommand by using revision only

Task:

SCM-876 – switch from Git-WIP to Gitbox

Dependency upgrade:

SCM-824 – Upgrade Plexus Utils to 3.0.24

Enjoy,

-The Apache Maven team

Apache Maven Plugin Tools Version 3.5.2 Released

khmarbaise — Sat, 26 May 2018 16:45:19 +0000

The Apache Maven team is pleased to announce the release of the Apache Maven Plugin Tools, version 3.5.2.

The Maven Plugin Tools contains the necessary tools to generate
rebarbative content like descriptor, help and documentation. In addition,
it provides tools to write Maven Plugins in scripting languages like Ant
or Beanshell.

The Maven Plugin Plugin is used to create a Maven plugin descriptor for
any Mojo’s found in the source tree, to include in the JAR. It is also
used to generate report files for the Mojos as well as for updating the
plugin registry, the artifact metadata and generating a generic help goal.

You should specify the version in your project’s plugin configuration:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-plugin-plugin</artifactId>
  <version>3.5.2</version>
</plugin>

You can download the appropriate sources etc. from the download page.

Release Notes – Maven Plugin Tools – Version 3.5.2

Dependency upgrades:

MPLUGIN-333 – Upgrade parent to 31
MPLUGIN-334 – Upgrade mave-surefire/failsafe-plugin 2.21.0
MPLUGIN-335 – Support JDK 10 for plugin generation: upgrade asm
MPLUGIN-338 – Upgrade plexus-archiver to 3.6.0

Enjoy,

-The Apache Maven team

Announcing the release of Apache Samza 0.14.1

xinyu — Fri, 25 May 2018 23:03:44 +0000

We are very excited to announce the release of Apache Samza 0.14.1
Samza has been powering real-time applications in production across several large companies (including LinkedIn, Netflix, Uber, Slack, Redfin, TripAdvisor, etc) for years now. Samza provides leading support for large-scale stateful stream processing with:

First class support for local state (with RocksDB store). This allows a stateful application to scale up to 1.1 Million events/sec on a single machine with SSD.
Support for incremental checkpointing of state instead of full snapshots. This enables Samza to scale to applications with very large state.
A fully pluggable model for input sources (e.g. Kafka, Kinesis, DynamoDB streams etc.) and output systems (HDFS, Kafka, ElastiCache etc.).
A fully asynchronous programming model that makes parallelizing remote calls efficient and effortless.
High level API for expressing complex stream processing pipelines in a few lines of code.
Flexible deployment model for running the the applications in any hosting environment and with cluster managers other than YARN.
Features like canaries, upgrades and rollbacks that support extremely large deployments with minimal downtime.

Enhancements, Upgrades and Bug Fixes

This is a minor release which contains improvements over multiple areas. In particular:

SQL
SAMZA-1681 Add support for handling older record schema versions in AvroRelConverter
SAMZA-1671 Add insert into table support
SAMZA-1651 Implement GROUP BY SQL operator
Standalone
SAMZA-1689 Add validations before state transitions in ZkBarrierForVersionUpgrade
SAMZA-1686 Set finite operation timeout when creating zkClient
SAMZA-1667 Skip storing configuration as a part of JobModel in zookeeper data nodes
SAMZA-1647 Fix NPE in JobModelExpired event handler
Eventhub
SAMZA-1688 Use per partition eventhubs client
SAMZA-1676 Miscellaneous fix and improvement for eventhubs system
SAMZA-1656 EventHubSystemAdmin does not fetch metadata for valid streams
Host-affinity
SAMZA-1687 Prioritize preferred host requests over ANY-HOST requests
SAMZA-1649 Improve host-aware allocation to account for strict locality

In addition, Samza is also upgraded to support Kafka version 0.11 in this release.
Overall, 51 JIRAs were resolved in this release. A source download of the 0.14.1 release is available here. The release JARs are also available in Apache’s Maven repository. See Samza’s download page for details and Samza’s feature preview for new features. We requires JDK version newer than 1.8.0_111 when running 0.14.1 release for users who are using Scala 2.12.

Community Developments

In March 21th, we held the meetup for Stream Processing with Apache Kafka & Apache Samza, which has the following presentations for Samza:

In industry, Samza got new adopters, including Ntent and Movico.

Contribute

It’s a great time to get involved. You can start by reviewing the tutorials, signing up for the mailing list, and grabbing some newbie JIRAs.
I’d like to close by thanking everyone who’s been involved in the project. It’s been a great experience to be involved in this community, and I look forward to its continued growth.

Apache Software Foundation Blogs

NetBeans Status at FossBack '18

Apache Maven Release 3.5.4

Contributors

Release Notes – Maven – Version 3.5.4

The Apache News Round-up: week ending 22 June 2018

1.5M Lines of NetBeans Code from Oracle to Apache

Apache Maven Surefire Plugin 2.22.0 Released

Apache Maven Enforcer Plugin Version 3.0.0-M2

The Apache News Round-up: week ending 15 June 2018

Apache NetBeans at FOSS Backstage 2018

Notice: Java 6 and 7 users: SSL Protocol upgrades coming to Central

Announcing Phoenix 4.14 released

Apache Maven WAR Plugin, version 3.2.2

Apache Maven Help Plugin, version 3.1.0

Apache Maven Wagon 3.1.0 Released

The Apache News Round-up: week ending 8 June 2018

Apache Maven PMD Plugin Version 3.10.0 Released

Success at Apache: the Chance to Influence the World

The Apache Software Foundation Announces Apache® Traffic Control™ as a Top-Level Project

Apache Maven Invoker Plugin Version 3.1.0 Released

Apache Maven Shared Maven Invoker Version 3.1.0 Released

Apache Maven JavaDoc Plugin Version 3.0.1 Released

The Apache News Round-up: week ending 1 June 2018

Apache Ignite 2.5: Scaling to 1000s Nodes Clusters

Massive Scalability

Marrying Apache Ignite and ZooKeeper

Machine Learning: Partition-Based Datasets

Genetic Algorithms

Continuous Self-Healing and Consistency Checks

SQL: Security and Fast Data Loading

In-place Execution of Spark DataFrame Queries

DEB and RPM packages

The Apache® Software Foundation Announces Added Support by Oath to Help Apache Infrastructure

Announcing Apache JSPWiki 2.10.4

Improvements to the Haddock template

Fixes for ACLs

Other fixes

For more information

Groovy 2.5 CliBuilder Renewal

Apache Groovy 2.5 CliBuilder Renewal

The groovy.util.CliBuilder Class is Deprecated

Typed Options

Supported Types

Adding More Types

Annotations

Annotating Methods of an Interface

Annotating Properties or Setter Methods of a Class

Script Annotations

Typed Positional Parameters

Apache Commons CLI Features

Picocli CliBuilder Features

Strongly Typed Lists

Strongly Typed Maps

Usage Help with Detailed Synopsis

Use Any Option Names

Fine-grained Usage Help Message

Usage Help with ANSI Colors

New errorWriter Property

Gotchas/Incompatibilities

Properties options and formatter Unavailable in Picocli Version

Property parser Differs in Picocli and Commons CLI Versions

Different Parser Behavior for longOption

Conclusion

[ANNOUNCE] Apache Groovy 2.5.0 released

[ANNOUNCE] Apache Groovy 2.5.0 released

[ANNOUNCE] Apache NetBeans (incubating) 9.0 RC1 released

Apache Maven SCM Version 1.10.0 Released

Apache Maven Plugin Tools Version 3.5.2 Released

Announcing the release of Apache Samza 0.14.1

Enhancements, Upgrades and Bug Fixes

Community Developments

Contribute

The `groovy.util.CliBuilder` Class is Deprecated

New `errorWriter` Property

Properties `options` and `formatter` Unavailable in Picocli Version

Property `parser` Differs in Picocli and Commons CLI Versions

Different Parser Behavior for `longOption`