Thanks for your advise, I temporarily found a solution by modifying the url in the jasperreports pom.xml file in my local repository (<repositories>/<repository> tag) but it is obviously a dubious solution and i'll try look at the repository manager option when i have time.
Clement, -- I temporarily found a solution by directly modifying jasperreports pom.xml (section 2010/11/2 Andrew Close <[email protected]> > On Tue, Nov 2, 2010 at 6:02 AM, Antonio Petrelli > <[email protected]> wrote: > > 2010/11/2 Clément TRUNG <[email protected]>: > >> the maven-metadata file contains html code that Maven sure is unable to > >> read. Obviously, I'm not Jasper forge administrator and can't change the > way > >> the site works, what are the solutions available to handle this kind of > >> situation ? > > > > Simple, call the Jasper forge administrator and ask him/her to fix it. > > Other options are: > > 1. install locally Jasper Reports artifacts and say goodbye to Jasper > > repositories > > +1 - Stick the artifacts you need for Jasper in your local repo > manager. Working with the Jasper folks is difficult unless you're > paying for support. ;) > > > 2. install a Maven repository manager (e.g. Nexus) that can act as a > > proxy to Jasper Forge (however I don't know if it will work). > > > > > -- > Andrew Close > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
