Rafael da Silva Chiarinelli wrote:
But, even whe defining the
jasperreports 2.0.5 as dependency of our project, the mojo plugin still
use the jasperreports 1.0.2 to compile all reports.
You have to distinguish the dependencies of the project and the
dependencies of a plugin, these are in general totally isolated (see [0]).
To add an artifact to a plugin's class path, use the <dependencies>
element owned by the <plugin> element (see [1]):
<project
...
<build>
<plugins>
<plugin>
<dependencies>
<dependency>
<groupId>jasperreports </groupId>
<artifactId>jasperreports </artifactId>
<version>2.0.5</version>
<dependency>
<dependencies>
...
</plugin>
...
</plugins>
...
</build>
...
</project>
Benjamin
[0] http://maven.apache.org/guides/mini/guide-maven-classloading.html
[1] http://maven.apache.org/ref/2.0.8/maven-model/maven.html#class_plugin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
