IDE's are ok for building initial reports but since you
cannot use IDE's in a production environment you'll need
to automate this
because of that limitation
Export your build.xml and or pom and verify that works in
fully automated staged environment (i.e. ant or maven
script)
If you need any help feel free to contact me offline as Ive
done about 50 of these using junitreport..
Martin--
************************************************************
*********
This email message and any files transmitted with it contain
confidential
information intended only for the person(s) to whom this
email message is
addressed. If you have received this email message in
error, please notify
the sender immediately by telephone or email and destroy the
original
message without making a copy. Thank you.
----- Original Message -----
From: <chris.mccauley gsa.gov>
To: "Struts Users Mailing List" <user struts.apache.org>
Sent: Tuesday, September 12, 2006 8:24 AM
Subject: RE: Jasper Reports
> JasperAssistant's support is questionable at this
point, iReports has
> become part of the JAsperSoft bundle and in my humble
opinion is a better
> IDE. Additionally, there is a "How To"
booklet available for
> JasperReports on their website...its pretty
comprehensive, now, scoot....
>
> |