Hi,
I was pretty sure I'd done that before but somehow can't find it in my
backups; I seem to remember it had to do with plugging the plugin to a
different lifecycle phase.
As for the depenency to jr, you should be able to redeclare it in your
pom's build/plugins/plugin section and it would override the one
declared by the plugin. Re-release the plugin for each jr release
would mean that we would force users in using a given cuting edge
version. However, 1) i guess the next release will have an updated
dependency, hoping people can downgrade and stay compatible with their
project 2) your suggestion is very good, thought about it myself but
never had the time/need combination to do it myself. I'll happily
apply a patch ;)
Cheers
greg
On 03/01/07, Srepfler Srgjan <[EMAIL PROTECTED]> wrote:
A report that I need to compile inside has a reference to a class in the
same project where the project is. The project is a war artifact. As the
project can't get installed before it and the report get compiled
there's is a mutual dependency and the compile won't go through. I have
tried this but it didn't work:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jasperreports-maven-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>compile-reports</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>it.group.org</groupId>
<artifactId>Project</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
Any advice? Also, will there be a new release of the plugin?
Jasperreports is up to 1.2.7 in the repository and there is even a 1.2.8
out there. Would a recompile of the plugin with an added dependency to
the new jasper use the new compiler? Couldn't the plugin scan the
project and see the jasperreports version used and use the compiler for
that version?
Srgjan
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email