Thanks, Dan. I've filed a report and attached a cut-down version of the
project and files. I hope it's helpful.
Dave
Dan Tran wrote:
file a jira with a producable jrxml, i will give it a try
thanks
On Feb 7, 2008 2:37 PM, David C. Hicks <[EMAIL PROTECTED]> wrote:
Good thought, but I was
file a jira with a producable jrxml, i will give it a try
thanks
On Feb 7, 2008 2:37 PM, David C. Hicks <[EMAIL PROTECTED]> wrote:
> Good thought, but I was already using 2.0.3. I did change it to 1.2.5,
> which is what the original Ant build was using, but that didn't make any
> difference, eit
Good thought, but I was already using 2.0.3. I did change it to 1.2.5,
which is what the original Ant build was using, but that didn't make any
difference, either.
Dan Tran wrote:
this plugin uses 1.2.2 jasperreport, this may be the cause of your
issue. But you can overide it thou. see doc f
this plugin uses 1.2.2 jasperreport, this may be the cause of your
issue. But you can overide it thou. see doc for details
-D
On Feb 7, 2008 1:54 PM, David C. Hicks <[EMAIL PROTECTED]> wrote:
> I'm converting an existing Ant build to Maven, and I've encountered a
> sticking point with respect to
I'm converting an existing Ant build to Maven, and I've encountered a
sticking point with respect to my Jasper reports.
Though it's not the preferred method for doing headers and footers, our
reports use some "imported" xml to provide the report header and footer
definitions. The xml is impor
