[
https://issues.apache.org/jira/browse/BATIK-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868180#comment-16868180
]
Roman Valls Guimera commented on BATIK-1194:
--------------------------------------------
Could it be possible that this breakage is the underlying reason for BATIK-1260
too?
> batik-all maven artifact broken since 1.9
> -----------------------------------------
>
> Key: BATIK-1194
> URL: https://issues.apache.org/jira/browse/BATIK-1194
> Project: Batik
> Issue Type: Bug
> Affects Versions: 1.9
> Reporter: Mark A. Greenwood
> Assignee: simon steiner
> Priority: Blocker
> Labels: easyfix, maven
>
> All the maven artifacts associated with the 1.9 release are broken as they
> all refer to a parent pom org.apache.xmlgraphics:batik:1.9 which does not
> exist in any maven repository and so dependency resolution fails when any
> batik artifact is listed as a dependency in any project.
> This issue seems to have already been reported (see
> https://issues.apache.org/jira/browse/BATIK-1192) but for some reason was
> marked as closed even though the issue still exists. If the issue had been
> fixed then the following URL would not return a 404 response
> https://repository.apache.org/content/repositories/releases/org/apache/xmlgraphics/batik/
> The parent pom file does exist in the source distribution
> (http://apache.mirrors.nublue.co.uk/xmlgraphics/batik/source/) so it should
> be trivial to push this into the apache maven repo (which would then also fix
> maven central as I believe this is synced automatically).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
