Skip to content

Latest commit

 

History

History
100 lines (68 loc) · 10.4 KB

artifacts-report.md

File metadata and controls

100 lines (68 loc) · 10.4 KB
Raw

Artifacts (Open Issues)

The dependecy artifacts used by EXMARaLDA are reported in four groups: (1) artifacts existing in public repositories, (2) artifacts equivalent to ones existing in public repositories, (3) artifacts included in other packages, and (4) artifacts of unknown origin.

The purpose of this report is to complete the documentation of the artifacts used by EXMARaLDA.

Artifacts existing in public repositories

Following artifacts are the same as existing files in public repositories (e.g. Maven). They do follow the naming conventions.

Artifacts equivalent to ones existing in public repositories

Following artifacts are the same as existing files in public repositories (e.g. Maven). Because they don't follow the naming conventions it is recommended to rename the artifact to follow the naming conventions.

  • mrj.jar -> MRJToolkitStubs-1.0.jar is the same as mrj:MRJToolkitStubs:1.0.

    The original jar MRJToolkitStubs-1.0.jar and the used jar by exmaralda mrj.jar differ as follows: In MRJToolkitStubs-1.0.jar the class com.apple.mrj.MRJFileUtils.java has two new signatures: public static File findFolder(short paramShort, MRJOSType paramMRJOSType) and public static File findFolder(short paramShort, MRJOSType paramMRJOSType, boolean paramBoolean), and the class com.apple.mrj.MRJPriv.java has two new signatures: static File findFolder(short paramShort, MRJOSType paramMRJOSType) and static File findFolder(short paramShort, MRJOSType paramMRJOSType, boolean paramBoolean). Furthermore it has following files META-INF\ABBOT.RSA, META-INF\ABBOT.SF, META-INF\MANIFEST.MF. Otherwise the jars are binary the same.

  • mysql-connector-java-5.1.6-bin.jar -> mysql-connector-java-5.1.6.jar is the same as mysql:mysql-connector-java:5.1.6.

  • stax-utils.jar -> stax-utils-20070216.jar is the same as net.java.dev.stax-utils:stax-utils:20070216.

  • saxon9he.jar -> Saxon-HE-9.6.0-7.jar is the same as net.sf.saxon:Saxon-HE:9.6.0-7.

  • jdom.jar -> jdom-1.1.3.jar is the same as org.jdom:jdom:1.1.3.

  • serializer.jar -> serializer-2.7.2.jar is the same as xalan:serializer:2.7.2.

  • xalan.jar -> xalan-2.7.2.jar is the same as xalan:xalan:2.7.2.

  • xercesImpl.jar -> xercesImpl-2.11.0.jar is the same as xerces:xercesImpl:2.11.0.

  • xml-apis.jar -> xml-apis-1.4.01.jar is the same as xml-apis:xml-apis:1.4.01.

  • swing-worker-1.2.jar -> swingworker-1.2.jar is the same as org.jdesktop.swingworker:swingworker:1.2.

    Version 1.2 is not existing (anymore). There are versions 1.2-1 or 1.2-2 that can be found in repository nigelsim.com. But, can this repository be trusted? Will it be available in the future? The jars are binary the same.

  • javax.mail.jar -> javax.mail-1.5.6.jar is the same as com.sun.mail:javax.mail:1.5.6.

    The original jar javax.mail-1.5.6.jar has a different META-INF\MANIFEST.MF as the jar used by exmaralda. Otherwise the jars are binary the same.

Artifacts included in other packages

Following artifacts are found to be part of other files/packages and they don't follow the naming conventions. Because they don't follow the naming conventions it is recommended to rename the artifact to follow the naming conventions. To avoid conflicts with existing groupIds we could make these artifacts belong to a new groupId=exmaralda, prefix the artifactId with exmaralda- and give the same version as the EXMARaLDA build (eg. exmaralda:exmaralda-artifact-1.0:1.6). This would help to discern it from real public artifacts.

  • BATIK.jar is part of batik-bin-1.8.zip from which it can be extracted under the path ``.

    This jar seems to have mixed contents of batik-1.8 and some other classes. What is the purpose of this mixing? (recommended name: exmaralda:exmaralda-:1.6)

  • elan.jar is part of ELAN_4-9-1_win.exe from which it can be extracted under the path InstallerData/Disk1/InstData/Resource1.zip/C_/MPI/ELAN_Releases/Install_Intermediates/lib/elan4.9.1/elan-4.9.1.jar.

    Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-elan-4.9.1:1.6)

  • quaqua.jar is part of quaqua-9.1.nested.zip from which it can be extracted under the path quaqua-9.1.zip/Quaqua/dist/quaqua.jar.

    Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-quaqua-9.1.jar:1.6)

  • fobs4jmf.jar is part of fobs4jmf_0.4.2_win32.tar.bz2 from which it can be extracted under the path fobs4jmf_0.4.2_win32.tar/fobs4jmf_0.4.2_win32/fobs4jmf.jar.

    Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-fobs4jmf-0.4.2.jar:1.6)

  • jmf.jar is part of fobs4jmf_0.4.2_win32.tar.bz2 from which it can be extracted under the path fobs4jmf_0.4.2_win32.tar/fobs4jmf_0.4.2_win32/jmf.jar.

    Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-jmf-0.4.2.jar:1.6)

  • bounce.jar is part of bounce-v011.zip from which it can be extracted under the path bounce.jar.

    It seems an old version of nz.ac.waikato.cms.weka.thirdparty > bounce. Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-:1.6)

  • cobra.jar is part of cobra-0.98.2.zip from which it can be extracted under the path cobra-0.98.2/lib/cobra.jar.

    Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-cobra-0.98.2.jar:1.6)

  • lobo.jar is part of lobo-distro-0.98.2.zip from which it can be extracted under the path lobo-distro-0.98.2/lobo.jar.

    Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-lobo-0.98.2.jar:1.6)

  • lobo-pub.jar is part of lobo-distro-0.98.2.zip from which it can be extracted under the path lobo-distro-0.98.2/lobo-pub.jar.

    Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-lobo-pub-0.98.2.jar:1.6)

Artifacts of unknown origin

The origin/source of following artifacts has not yet been identified

  • AppleJavaExtensions.jar is of unknown origin. (recommended name: exmaralda:exmaralda-AppleJavaExtensions.jar:1.6)

  • ipsk.jar is of unknown origin.

    is this jar from BAS in München? (recommended name: exmaralda:exmaralda-ipsk.jar:1.6)

  • JavaQTMovieView-1.4.5.jar is of unknown origin. (recommended name: exmaralda:exmaralda-JavaQTMovieView-1.4.5.jar:1.6)

  • jctable.jar is of unknown origin. (recommended name: exmaralda:exmaralda-jctable.jar:1.6)

  • jmf.jar is of unknown origin.

    Content of this jar do not correspond to any of the versions 2.1.1e, 2.2.1b, fs-3.0. The used jar by exmaralda is a subset of "FobsJMF/jmf.jar". Furthermore there are three modified/changed classes: com.sun.media.renderer.audio.AudioRenderer, com.sun.media.util.RegistryLib, com.sun.media.BasicRendererModule. Otherwise the jars are binary the same. (recommended name: exmaralda:exmaralda-jmf.jar:1.6)

Extra artifacts needed to compile EXMARaLDA

These artifacts are needed to compile EXMARaLDA. But they are not needed for runtime