title: package/class imports in jasperreport fails after upgrade 6.3.0 -> 6.3.1
body: <p>I have an application that compiles a lot of reports at build time and fills them at user requests during run time.
  I use the library version of jasperreports as dependency through Maven. I just increased the version number to 6.3.1. I was prepared for API changes and different behavior with the new version. However there is one thing I just can't seem to work out...</p>
  
  <p>I use a utility package in some "text field"-elements in report designs that use (static) methods for stuff like formatting or validation. The package is in the same project and after compiling in the same .jar-file as the reports. Example:</p>
  
  <pre><code>&lt;textFieldExpression&gt;&lt;![CDATA[TemplateUtils.formatIban($P{iban})]]&gt;&lt;/textFieldExpression&gt;
  </code></pre>
  
  <p>The package is also imported in the report:</p>
  
  <pre><code>&lt;import value="de.company.app.utils.*"/&gt;
  </code></pre>
  
  <p>The problem is that this package and other classes in my own packages are no longer recognized when trying to compile reports:</p>
  
  <blockquote>
    <p>de.company.app.utils cannot be resolved</p>
  </blockquote>
  
  <p>These packages are definitely on classpath of the project. Also, external libraries referenced as Maven dependencies (like Apache commons) are recognized without trouble and reports using them compile as usual. Only my own packages in the project are affected.</p>
  
  <p>Even when trying to compile directly through the Eclipse plugin or a fresh installation of Jaspersoft Studio 6.4.3, compiling fails with the same error.
  I've gone through the changelog and didn't find anything relating to this.</p>