[
https://issues.apache.org/jira/browse/MNGSITE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620605#comment-14620605
]
Amedee Van Gasse commented on MNGSITE-250:
------------------------------------------
I uploaded a 4.2.2 POM to Maven Central yesterday, via Sonatype.
I am release engineer at iText Group NV, and I am authorized to update
artifacts with the com.lowagie and com.itextpdf groupId.
See https://issues.sonatype.org/browse/MVNCENTRAL-760
Versions 4.2.0 and 4.2.1 were uploaded to Maven Central by a company called
InProTopia, without the knowledge or approval of iText Group NV.
They built their jar not from the official iText repository, but off a patched
fork created by github user ymasory.
According to Apache's FAQ on uploading artifacts, InProTopia should have used a
different groupId:
bq. I have a patched version of the foo project developed at foo.com, what
groupId should I use?
bq. When you patch / modify a third party project, that patched version becomes
your project and therefore should be distributed under a groupId you control as
any project you would have developed, never under com.foo. See above
considerations about groupId.
https://maven.apache.org/guides/mini/guide-central-repository-upload.html
A solution to this problem has been given on StackOverflow:
http://stackoverflow.com/a/31319337/766786
> 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)
