cn73 Posted November 11, 2009 Share Posted November 11, 2009 Good morning.I've opened, edited and saved, with iReport 3.6.0, a report, originally created with iReport 3.0.0. When I compile my report I get this strange WARNING:11-nov-2009 9.27.03 net.sf.jasperreports.engine.component.ComponentsEnvironment findComponentBundlesWARNING: Found two components for namespace http://jasperreports.sourceforge.net/jasperreports/componentswhat this means?Post Edited by cn73 at 12/11/2009 09:16 Link to comment Share on other sites More sharing options...
cn73 Posted November 16, 2009 Author Share Posted November 16, 2009 anybody? Link to comment Share on other sites More sharing options...
lucianc Posted November 16, 2009 Share Posted November 16, 2009 This means that JasperReports is present twice on the report classpath. I don't know how iReport manages classloaders, so I can't tell how could that happen. Do you have a classpath configured in iReport?Regards,Lucian Link to comment Share on other sites More sharing options...
cn73 Posted November 17, 2009 Author Share Posted November 17, 2009 the "problem" occurs when compiling the report in my project, through jasperreports-maven-plugin ... so in the pom I must use a double dependence, one for Plugin, the other for the project. Now it is clear the cause, thanks;)Code:<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jasperreports-maven-plugin</artifactId> <configuration> <sourceDirectory> src/main/jasperreports </sourceDirectory> <outputDirectory> src/main/resources/jasperbin </outputDirectory> <javaDirectory> target/jasperreports/java </javaDirectory> <!-- <keepJava>true</keepJava> --> </configuration> <executions> <execution> <phase>generate-resources</phase> <goals> <goal>compile-reports</goal> </goals> </execution> </executions> <dependencies> <dependency> <groupId>jasperreports</groupId> <artifactId>jasperreports</artifactId> <version>3.5.3</version> <scope>provided</scope> </dependency> </dependencies> </plugin> Link to comment Share on other sites More sharing options...
phuchoa0502 Posted August 17, 2011 Share Posted August 17, 2011 Hi cn73! Could you please to explain more detail how to solve this problem, because now i also get it. thanksHans Link to comment Share on other sites More sharing options...
dshurt Posted September 5, 2019 Share Posted September 5, 2019 Make sure both the plugin and the project dependencies match. That solved my issue that caused this message. Using: 6.9.0 jasper; 1.0-beta-2 plugin Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now