Already added in jira:
http://jira.codehaus.org/browse/MNG-556
Cheers,
Vincent
2005/7/8, Kris Bravo <[EMAIL PROTECTED]>:
> Thanks Kenney, that fixed the problem. At the same time, it would be
> helpful if the error explained this nuance.
>
> Before I add to Jira, can we assume that MavenProject
Thanks Kenney, that fixed the problem. At the same time, it would be
helpful if the error explained this nuance.
Before I add to Jira, can we assume that MavenProject.getArtifacts()
should *never* return null for a valid project with resolved
dependencies? If so, the method could throw an
Dependen
On Fri, 8 Jul 2005, Kris Bravo wrote:
You should define
@requiresDependencyResolution compile
in the class-level javadoc.
> I have the following handle to the MavenProject defined in a plugin
> written for maven 2.
>
>/**
> * The project whose project files to create.
> *
> * @
I have the following handle to the MavenProject defined in a plugin
written for maven 2.
/**
* The project whose project files to create.
*
* @parameter expression="${project}"
* @required
*/
private MavenProject project;
When I attempt to get the list of classpath eleme
