Found the solution, but this should definetly be in the documentation.
I thought that I'd seen this sort of configuration before.. and yes the
Maven Dependency Plugin uses it for artifact item (see
http://mojo.codehaus.org/dependency-maven-plugin/howto.html):
<configuration>
<artifactItems>
<artifactItem>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<type>jar</type>
<outputDirectory>${project.build.directory}/alternateLocation</location>
<destFileName>optional-new-name.jar</destFileName>
</artifactItem>
</artifactItems>
<outputDirectory>${project.build.directory}/wars</outputDirectory>
</configuration>
I suspected that I needed to add javadoc annotations to my bean - which I
got confirmed by the Dependency plugin:
public class ArtifactItem
{
/**
* Group Id of Artifact
* @parameter
* @required
*/
private String groupId;
[...]
/**
* @return Returns the artifactId.
*/
public String getArtifactId()
{
return artifactId;
}
/**
* @param artifactId The artifactId to set.
*/
public void setArtifactId( String artifact )
{
this.artifactId = artifact;
}
[...]
}
One of the mojos looks has this section:
/**
* Collection of ArtifactItems to work on. (ArtifactItem contains
groupId, artifactId, version, type, location, destFile, markerFile and
overwrite.)
* See "How To Use" and "Javadoc" for details.
* @parameter
* @required
*/
private ArrayList artifactItems;
(The Dependency Maven Plugin source code is Copyright 2005-2006 Brian Fox
and licensed under the Apache License, Version 2.0).
Regards,
Jimisola
--
View this message in context:
http://www.nabble.com/Passing-plugin-build-configuration-from-pom-to-a-custom-bean-tf1930560.html#a5288122
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
