Hello, Thorsten
Thank you very much for the help! Yes, this is the reason of my problem.
I tested it on next releases of batik and found that the dependency
structure
changed in next versions and there's no batik-js in dependency tree.
Unfortunately, I couldn't upgrade version because in real
Hi Sergey,
> I updated to the latest maven version 3.5.3 and configured the project
> to use
> the latest maven-assembly-plugin version 3.1.0.
You seem to be hit by
https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-782.
In short: You have circular dependencies in Batik 1.7:
ba
Hi,
> The first thing I need to mention that I gave you a wrong version of
> maven-assembly-plugin.
> Maven-assembly-plugin version: 2.2-beta-5
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
> 2014-12-14T20:29:23+03:00)
> Maven home: C:\soft\apache-maven-3.2.5
> Java version: 1.
ran mvn package against pom.xml from supplied project.zip with no missing
dependencies:
[DEBUG] Goal:
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single (default)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${appendAssemblyId}
${attach}
${classifier}
