Jump to content
Changes to the Jaspersoft community edition download ×

Compile error in ReportQueryDialog

2004 IR Help

Recommended Posts

By: Neil Lamka - neil_lamka

Compile error in ReportQueryDialog

2005-07-14 11:02

I updated my JDK to 1.5 (from 1.4) although I don't think that is related to the issue. I checked out the current iReports code from CVS and tried to compile and get the following compile error.


D:iReportiReport2>ant clean compile

Buildfile: build.xml



[delete] Deleting directory D:iReportiReport2classes

[delete] Deleting directory D:iReportiReport2targetdist



[mkdir] Created dir: D:iReportiReport2classes

[mkdir] Created dir: D:iReportiReport2targetdist

[copy] Copying 260 files to D:iReportiReport2classes



[javac] Compiling 305 source files to D:iReportiReport2classes

[javac] D:iReportiReport2srcitbusinesslogicireportguiReportQueryDialog.java:1397: cannot find symbol

[javac] symbol : method setName(java.lang.String)

[javac] location: class net.sf.jasperreports.engine.design.JRDesignExpression

[javac] exp.setName("parameterDefaultValue_" + parameter.getName() );

[javac] ^

[javac] Note: * uses or overrides a deprecated API.

[javac] Note: Recompile with -Xlint:deprecation for details.

[javac] Note: Some input files use unchecked or unsafe operations.

[javac] Note: Recompile with -Xlint:unchecked for details.

[javac] 1 error



D:iReportiReport2build.xml:71: Compile failed; see the compiler error output for details.


I searched the forum and did not find anything that looked related so I assume I'm missing something simple here. I have been able to do an ant build on previous releases that I've checked out.


Thanks in advance for the help








By: C-Box - c-box

RE: Compile error in ReportQueryDialog

2005-07-14 12:42

I also got this error and commented the line out...


Teodor meant:

We removed the "name" property of expressions because it was
not very useful and was not used in all cases. For instance,
if you
build the template using the API the expressions have a null


so I guess Guilio has to remove that line in next version... he will get to know at least, when he upgrade to current 0.6.8. :-)



Link to comment
Share on other sites

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...