[
https://issues.apache.org/jira/browse/BATIK-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241968#comment-14241968
]
Patrick Mahoney commented on BATIK-1098:
----------------------------------------
We noticed this, within our sbt build.
A few example messages:
[warn] circular dependency found:
org.apache.xmlgraphics#batik-anim;1.7->org.apache.xmlgraphics#batik-svg-dom;1.7->...
[warn] circular dependency found:
org.apache.xmlgraphics#batik-bridge;1.7->org.apache.xmlgraphics#batik-gvt;1.7->...
[warn] circular dependency found: org.apache.xmlgraphics#batik-
script;1.7->org.apache.xmlgraphics#batik-bridge;1.7->...
...
I have found that it is possible to keep multiple modules/projects, but that
some work will be necessary to make this dependency graph acyclic - new
subprojects to hold common code.
> Circular dependencies between submodules
> ----------------------------------------
>
> Key: BATIK-1098
> URL: https://issues.apache.org/jira/browse/BATIK-1098
> Project: Batik
> Issue Type: Bug
> Components: Animation engine, Bridge, GVT, Scripting, SVG DOM
> Affects Versions: 1.7
> Reporter: Heikki Vesalainen
> Priority: Critical
> Labels: build, maven
>
> There are circular dependencies between batik submodules:
> batik-svg-dom <-> batik-anim
> batik-bridge <-> batik-gvt
> batik-bridge <-> batik-script
> Since proper maven packaging seems to be almost impossible for the average
> Java-project, I strongly encourage projects not to try to bee too fancy. Just
> publish a single module that contains everything, hiding all the hard to
> avoid circular references between the different packages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
