I think those bugs may be due to the plugin using the runtime scope
not the runtime classpath? The runtime classpath should include the
compile scope artifacts.
2009/7/31 Benjamin Bentmann :
> Hi,
>
> I would like to propose an extension of the mojo annotation
>
> �...@requiresdependencyresolution
moving to dev ml.
fully agree.
But my question here : is do we have to do this for multimodules as
the tarball in root contains all sources from modules ?
--
Olivier
2009/8/1 Jason van Zyl :
> Ok, we need to figure out how to do this generally. I really don't want to
> see this in every POM we h
The command-line setting should win, IMO...but I don't think this is
really tested ATM...
Brett Porter wrote:
Hi John,
On 14/07/2009, at 6:40 AM, jdca...@apache.org wrote:
+ As of Maven 2.2.1, there are two ways to specify which Wagon
provider should be used: via the command line,
+ or in
The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.6.
The Maven Javadoc Plugin is a plugin that uses the javadoc tool for
generating javadocs for the specified project.
http://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in y
Hi,
I would like to propose an extension of the mojo annotation
@requiresDependencyResolution
This currently allows to resolve only a single scope from the set
"compile", "runtime" and "test". A problem I have seen in some plugins
is about using "runtime" scope. This scope is not a superse
+1
Brett Porter wrote:
> Hi,
>
> Mark has been contributing regularly to Maven SCM for quite some time
> (in particular the git support recently, and I think has been wanting to
> help with improving the API and release mechanism for git), as well as
> being more broadly active.
>
> I think he'd
