[jira] [Comment Edited] (BATIK-1186) batik-rasterizer 1.9 jar file is empty on Maven central

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Comment Edited] (BATIK-1186) batik-rasterizer 1.9 jar file is empty on Maven central

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/BATIK-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983844#comment-15983844 ]

Glenn Adams edited comment on BATIK-1186 at 4/25/17 11:48 PM:
--------------------------------------------------------------

[~ssteiner1] As part of the transition to maven, the target artifacts were reorganized in order to (1) remove circular dependencies between artifacts; (2) clearly separate library and application jar artifacts, i.e., those without a main class reference in the manifest and those with a main class reference. In order to accomplish these goals, prior application only artifacts were separated into a library jar and an application jar flavor, where the library jar is referenced as a dependency by other library jars as well as application jars.

In the prior, ant based builds, the batik-rasterizer artifact was an application jar and contained a copy of its class files. In the new maven build, all of the former rasterizer classes were moved into the batik-svgrasterizer library jar artifact, and the batik-rasterizer was left in place, but without a copy of the class files. However, it is not empty, but contains a pom and a manifest with a class path both of which reference batik-svgrasterizer as a dependency.

So, if you use maven, then the dependencies will automatically be satisfied. And if you use batik-rasterizer as an application (its new sole use), then again its dependencies are addressed by its pom and classpath.

However, if you are using batik-rasterizer as a means to reference the class files now moved to batik-svgrasterizer, you will need to update your application accordingly.


was (Author: gadams):
[~ssteiner1] As part of the transition to maven, the target artifacts were reorganized in order to (1) remove circular dependencies between artifacts; (2) clearly separate library and application jar artifacts, i.e., those without a main class reference in the manifest and those with a main class reference. In order to accomplish these goals, prior application only artifacts were separated into a library jar and an application jar flavor, where the library jar is referenced as a dependency by other library jars as well as application jars.

In the prior, ant based builds, the batik-rasterizer artifact was an application jar and contained a copy. In the new maven build, all of the former rasterizer classes were moved into the batik-svgrasterizer library jar artifact, and the batik-rasterizer was left in place, but without a copy of the class files. However, it is not empty, but contains a pom and a manifest with a class path both of which reference batik-svgrasterizer as a dependency.

So, if you use maven, then the dependencies will automatically be satisfied. And if you use batik-rasterizer as an application (its new sole use), then again its dependencies are addressed by its pom and classpath.

However, if you are using batik-rasterizer as a means to reference the class files now moved to batik-svgrasterizer, you will need to update your application accordingly.

> batik-rasterizer 1.9 jar file is empty on Maven central
> -------------------------------------------------------
>
>                 Key: BATIK-1186
>                 URL: https://issues.apache.org/jira/browse/BATIK-1186
>             Project: Batik
>          Issue Type: Bug
>          Components: SVG Rasterizer
>    Affects Versions: 1.9
>            Reporter: Thomas Mortagne
>            Priority: Blocker
>
> When I download http://search.maven.org/remotecontent?filepath=org/apache/xmlgraphics/batik-rasterizer/1.9/batik-rasterizer-1.9.jar I end up with an empty JAR (except for the META-INF).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...