After some
investigation, it comes from the diagram definition editor
extra plugin. It embeds directly the jar in the git
repository, which is a bad practice.
Plugins should
depend only from orbit plugins when they depend on a
specific external library.
So for the
contributors of the diagram: could you please remove the jar
from the plugin in the git repo, and update the classpath of
the plugin to depend on batik from orbit?
Regards,
Rémi
-------------------------------------------------------
Rémi
SCHNEKENBURGER
+33
(0)1 69 08 48 48
CEA Saclay
Nano-INNOV
Institut
CARNOT CEA LIST
www.eclipse.org/papyrus
Hi All,
We are currently working on the IPlog for
the release review 2.0.0 of the Papyrus project. When
generating the IPlog, it seems that new dependencies to third
party plugins have been added to the plugins without
explicitly running a CQ for those libraries.
Here are the issues we currently have [1]:
It looks like some unapproved versions of some libraries have leaked into the
project downloads since the last IP Log check (it looks like they may have
appeared in some of you service releases).
org.apache.batik.dom.source_1.6.1.*.jar (No CQ found)
org.apache.batik.dom_1.6.1.*.jar (No CQ found)
org.apache.commons.io_2.2.0.*.jar (No CQ found)
org.apache.commons.lang3_3.1.0.*.jar (No CQ found)
xalan-2.6.0.*.jar (No CQ found)
xerces_2_5_0.jar (No CQ found)
Do you know when/where these dependencies
were introduced, and what they are used for? Shall we remove
them from the dependencies or create a new CQ for these ones?
Regards,
Rémi
[1]
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11480
-------------------------------------------------------
Rémi
SCHNEKENBURGER
+33
(0)1 69 08 48 48
CEA Saclay
Nano-INNOV
Institut
CARNOT CEA LIST
www.eclipse.org/papyrus