Hi,
This is a Java 8 compatibility release. This release is needed to be
able to use Maven PMD Plugin on Java 8 sources. This involved
upgrading to PMD 5.1+ which in turn requires at least Java 6. So the
plugin now requires Java 6 to run and is able to work on Java 8
sources.
We solved 2 issues:
How did you end up handling the java 6 requirement?
manfred
Dennis Lundberg wrote on 28.07.2014 15:04:
Hi,
This is a Java 8 compatibility release. This release is needed to be
able to use Maven PMD Plugin on Java 8 sources. This involved
upgrading to PMD 5.1+ which in turn requires at
Hi,
About a year ago, the EOL banner was added for Maven 1.x. Today I saw there was
a still a maven-1.x link in the navigation from the parent POM, which I
removed, and added a single section to the bottom of the front page for
archived documentation.
Looking at
Leave SVN alone, it's only a matter of time before it's permanently retired
in it's entirety, right?
On Tue, Jul 29, 2014 at 12:58 PM, Brett Porter br...@apache.org wrote:
Hi,
About a year ago, the EOL banner was added for Maven 1.x. Today I saw
there was a still a maven-1.x link in the
Hey all,
Just been reading [1] after it was mentioned in both #scala and #clojure
on irc.freenode.org now, is there anything that can be done to alleviate
some of these issues?
oss.sonatype.org now requires everything to be GPG signed before being
uploaded to central, but I'm not sure about
We are already in the process of making this open for free to
everyone. Way back in 2012 the CDN situation was different but we just
renewed the contract and and ssl is part of it. Once this is setup, we
should consider changing the superpom to use ssl by default.
Obviously doing something to
On 29 Jul 2014, at 12:14 pm, Mark Derricutt m...@talios.com wrote:
Hey all,
Just been reading [1] after it was mentioned in both #scala and #clojure on
irc.freenode.org now, is there anything that can be done to alleviate some of
these issues?
oss.sonatype.org now requires everything
