[ http://jira.codehaus.org/browse/MEV-445?page=all ]
Carlos Sanchez closed MEV-445.
------------------------------
Assignee: Carlos Sanchez
Resolution: Won't Fix
We don't change binaries, they are the official releases
> fop:fop 0.20.5 project on repo1.maven.org has inconsistenc Class-Path: and
> pom.xml dependencies
> -----------------------------------------------------------------------------------------------
>
> Key: MEV-445
> URL: http://jira.codehaus.org/browse/MEV-445
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Dependencies
> Reporter: Markus KARG
> Assigned To: Carlos Sanchez
>
> repo1.maven.org contains the project "fop" version "0.20.5".
> The pom.xml's dependencies and the main artifact's Class-Path MANIFEST.MF
> entries are not in sync.
> As a result, someone that has a pom.xml depending on the fop 0.20.5 project
> on repo1.maven.org will end up with a broken classpath (since the JARs told
> in the Class-Path: attribute are not there).
> I could not find the maintainer of that project's pom.xml, so since you are
> the maintainer of the complete repository, please either fix it or lookup and
> inform the maintainer of the pom.xml.
> I already contacted the maintainer of the "original FOP product" (Jeremias
> MÄRKI), but he said that he has not provided the repo1.maven.org download for
> fop and he doesn't know who provided it.
> Also I have asked the maven users list who could fix it, but no one answered.
> It seems that there is stuff on you repository that actually is without a
> maintainer.
> This situation is not acceptible, since there should be a maintainer for each
> project ever.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
