I fear there is not much to discuss. The standard handling of javadoc has not
changed.
It's just that the plugin now aborts with an error or reports tons of warnings
on really peanut situations like a missing @param.
There are 2 other points we need to take care:
1.) this must only be activa
The Apache Maven team is pleased to announce the release of the Apache Maven
Plugin Tools, version 3.3
The Maven Plugin Tools contains the necessary tools to be able to produce
Maven Plugins in scripting languages and to generate rebarbative content like
descriptor, help and documentation.
The
Since MavenProject#getProjectReferences is public why is
MavenProject#getProjectReferenceId (which is the only way of generating the
key for projectReferences without breaking encapsulation) private?
NB in maven-project-2.2 #getProjectReferenceId used to be public.
William
GitHub user ryanheinen opened a pull request:
https://github.com/apache/maven-plugins/pull/21
Return false from canGenerateReport if skip is true
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ryanheinen/maven-plugins MPMD-187
+1 with Robert's solution (though I don't remember it was the actual issue
for that ci build failure some weeks ago...).
That's something I've also been planning to do after working recently with
buildnumber. BTW, not sure yet why, but sometimes IT won't fail doing a svn
info under the hood althou
Issue is still open for the future:
https://jira.codehaus.org/browse/MNG-5102
Cheers,
Paul
On Tue, May 13, 2014 at 9:36 PM, Mark Derricutt wrote:
> On 14 May 2014, at 5:19, Cristiano Gavião wrote:
>
> couple years ago I read an interview from Jason where he talk about pom
>> mixins [1].
>>
>
Hi Hervé,
> I tested it on maven-scm-publish-plugin, since it is quite little and
I'll
intend to make a release in a week or so
you can see the result here [1]
of course, the download link doesn't work because it is a non-released
SNAPSHOT
Yeah but the result looks great...
As expected,
