Hello, i have the same problem here since yesterday too. Thx for the tips on the settings.xml. Since i don't remember whether these dependencies were on the JasperForge repo or not my guess is that since the site has gone under some maintenance the 30th of October could it be that what was a 404 HTTP error code before is now a 202 HTTP code with an error page rendering ? In this case, it can be that maven generates a basic maven-metadata-jaspersoft.xml instead... I myself opened a thread this morning at maven mailing. For those interested, see http://www.mail-archive.com/users@maven.apache.org/msg113796.html Post Edited by ctrung at 11/02/2010 17:06
