Mon, 8 Apr 2013 20:15:15 +1000, /Olivier Lamy/:
Release Notes - Apache Maven 2.x Compiler Plugin - Version 3.1
** Bug
* [MCOMPILER-187] - incremental stuff detect changes even if
nothing has changed means too much compilation
I'm not sure it is the same, but it seems I'm still observing
This mojo is maintained here http://code.google.com/p/maven-license-plugin/
So use this place for any questions.
Maybe you can try this one too http://mojo.codehaus.org/license-maven-plugin/
2013/4/11 David Hoffer dhoff...@gmail.com:
I have a multi-module build I'm running the license:format
On 11 April 2013 11:36, Olivier Lamy ol...@apache.org wrote:
This mojo is maintained here
http://code.google.com/p/maven-license-plugin/
So use this place for any questions.
While you are over there can you also point out that they are not supposed
to call themselves maven-___-plugin as that
The Maven team is pleased to announce the release of
maven-shared-utils, version 0.4
This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.
It is not a 100% API compatible replacement though but a replacement
with improvements:
The Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.14.1
This version contains mostly minor bugfixes.
This is the last version that will include any java 1.3 1.4 support.
Future versions will be 1.5+ only.
You should specify the version in your project's
Jason
I am trying to pitch maven to the folks who are still using Ant + Ivy and
have created a dependency mess. One of the points I want to mention is
polyglot because of fewer number of lines of code. Is your update from Aug
2012 still valid ? as in, polyglot not abandoned ?
Thanks
Venkat
I'm not sure it could be a clue but it happens for some (I haven't
verified all) WAR modules.
What code are you compiling in a WAR module? Best practice says to move the
Java code to a Jar module. Are you precompiling jsps with jspc or ...?
Is this a project you can share via Github? Or can
Hi,
I've got a project structure where I have an aggregator project and all of
it's modules are also aggregator projects (i.e. projects that exist just to
specify sub-modules). Picture something like what's shown in the POM best
practices section of the Maven reference:
