[jira] [Closed] (MNGSITE-250) Failed reference in *.jar of com.lowagie

["Karl Heinz Marbaise (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNGSITE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise closed MNGSITE-250.
---------------------------------------
    Resolution: Not A Problem

This Problem is related to:
{code}
Access denied to http://www.jasperforge.org/maven2/com/itextpdf/itextpdf/4.2.2/itextpdf-4.2.2.pom. Error code 403, Forbidden -> [Help 1]
{code}
and has nothing to do with the Maven site. 

> Failed reference in *.jar of com.lowagie
> ----------------------------------------
>
>                 Key: MNGSITE-250
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-250
>             Project: Maven Project Web Site
>          Issue Type: Bug
>         Environment: Repository
>            Reporter: Laura Abad
>            Priority: Blocker
>              Labels: maven
>         Attachments: maven-metadata-central.xml
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> Compiling with maven causes dependency error for jar that has dependecies for  com.lowagie because it directory is move to com.itextpdf but number of revisions don't match.
> Error log:
> Failed to collect dependencies for [jasperreports:jasperreports:jar:2.0.1 (compile)]: Failed to read artifact descriptor for com.lowagie:itext:jar:4.2.2: Could not transfer artifact com.itextpdf:itextpdf:pom:4.2.2 from/to jaspersoft (http://www.jasperforge.org/maven2): Access denied to http://www.jasperforge.org/maven2/com/itextpdf/itextpdf/4.2.2/itextpdf-4.2.2.pom. Error code 403, Forbidden -> [Help 1] 
> The problem is caused by an opoened range version y jasperreports pom that tells maven install to compile with latest version of Itext. The metadata from Itext was updated yesterday with a latest version that has no .jar and perevents the compilation.
> Here is the problematic metadata: 
> https://slmaven.indra.es/nexus/content/groups/public/com/lowagie/itext/maven-metadata.xml
> Going to previus version of the metadata will resolve the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)