Skip to content

[Fatal Error] jcardsim-3.0.4.pom:7:3: The element type "hr" must be terminated by the matching end-tag "</hr>" #2

Open
@grenyaz

Description

I just tried to build one of the samples and I'm getting the following error

$ ./gradlew :jc101-1c:build
Starting a Gradle Daemon (subsequent builds will be faster)
:jc101-1c:compileJava
:jc101-1c:processResources UP-TO-DATE
:jc101-1c:classes
:jc101-1c:jar
:jc101-1c:assemble
:jc101-1c:compileTestJava
Download https://jcenter.bintray.com/com/github/martinpaljak/apdu4j/18.10.04/apdu4j-18.10.04.pom
Download https://jcenter.bintray.com/com/github/martinpaljak/javacard/18.10.04/javacard-18.10.04.pom
Download https://jcenter.bintray.com/org/bouncycastle/bcprov-jdk15on/1.60/bcprov-jdk15on-1.60.pom
Download https://jcenter.bintray.com/junit/junit/4.12/junit-4.12.pom
Download http://dl.bintray.com/bertrandmartel/maven/com/licel/jcardsim/3.0.4/jcardsim-3.0.4.pom
[Fatal Error] jcardsim-3.0.4.pom:7:3: The element type "hr" must be terminated by the matching end-tag "</hr>".
Download https://jcenter.bintray.com/com/github/martinpaljak/apdu4j/18.10.04/apdu4j-18.10.04.jar
Download https://jcenter.bintray.com/org/bouncycastle/bcprov-jdk15on/1.60/bcprov-jdk15on-1.60.jar
:jc101-1c:compileTestJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':jc101-1c:testCompileClasspath'.
> Could not resolve all dependencies for configuration ':jc101-1c:jcardsim'.
   > Could not resolve com.licel:jcardsim:3.0.4.
     Required by:
         project :jc101-1c
      > Could not resolve com.licel:jcardsim:3.0.4.
         > Could not parse POM http://dl.bintray.com/bertrandmartel/maven/com/licel/jcardsim/3.0.4/jcardsim-3.0.4.pom
            > The element type "hr" must be terminated by the matching end-tag "</hr>".

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 4.543 secs

Is the jcardsim-3.0.4 dependency broken? It seems so. Are there any alternatives to resolve that dependency?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions