Missing dependencies - de.rub.nds.tlsattacker:Attacks:jar:3.7.2 & de.rub.nds.tlsattacker:TLS-Core:jar:3.7.2

Question

Missing dependencies - de.rub.nds.tlsattacker:Attacks:jar:3.7.2 & de.rub.nds.tlsattacker:TLS-Core:jar:3.7.2

acostad184 opened this issue 3 years ago · 9 comments

I'm by no means an expert on Java or Maven but I believe these dependencies are missing from Maven's repo

Here's the full error message:

[ERROR] Failed to execute goal on project TLS-Scanner: Could not resolve dependencies for project de.rub.nds.tlsscanner:TLS-Scanner:pom:4.1.2: The following artifacts could not be resolved: de.rub.nds.tlsattacker:TLS-Core:jar:3.7.2, de.rub.nds.tlsattacker:Attacks:jar:3.7.2: Could not find artifact de.rub.nds.tlsattacker:TLS-Core:jar:3.7.2 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Hope this helps !

Cheers

Answer 1 · 2021-12-21T08:03:07.000Z

Jeah, maven central servers were pretty busy these days due to log4j - I was not able to push them yet. I will try throughout the day. Maybe I am lucky. For now, you have to build these dependencies yourself from our repos.

Answer 2 · 2021-12-21T09:13:29.000Z

Ok i had better luck today. I also drafted a new release to update log4j 2.16.0 -> 2.17.0 . I don't think the issue affected any of our projects but jeah... The new versions are in maven central now and should build again

Answer 3 · 2022-06-09T07:14:36.000Z

Sorry to re-open the issue, I got a similar error while git cloning today:

[ERROR] Failed to execute goal on project TLS-Scanner: Could not resolve dependencies for project de.rub.nds.tlsscanner:TLS-Scanner:pom:4.2.0: Failure to find de.rub.nds.tlsattacker:TLS-Core:jar:3.8.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project TLS-Scanner: Could not resolve dependencies for project de.rub.nds.tlsscanner:TLS-Scanner:pom:4.2.0: Failure to find de.rub.nds.tlsattacker:TLS-Core:jar:3.8.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced

I am not used to java project in general nor Maven, so in case you could shortly document how to build these dependencies manually to solve the issue locally, that would be great.

Thanks, Benoit.

Answer 4 · 2022-06-09T08:44:45.000Z

Ah I see, the problem is that we made a release yesterday and the dependencies didn't make it into nexus yet. They will probably be there tomorrow such that it builds again automatically, for now you need to build all the dependencies manually:
https://github.com/tls-attacker/ModifiableVariable
https://github.com/tls-attacker/ASN.1-Tool
https://github.com/tls-attacker/X509-Attacker
https://github.com/tls-attacker/TLS-Attacker

Each time you have to clone them and run mvn clean install -DskipTests
Edit: In that order

Answer 5 · 2022-06-09T09:06:53.000Z

any chance to modify the dockerfile so that this is always done?

Answer 6 · 2022-06-09T09:13:42.000Z

yes we can do that

Answer 7 · 2022-06-09T09:35:52.000Z

I updated the docker file, so that should build now.

Answer 8 · 2022-06-09T10:41:28.000Z

Its now in maven central and should now also be buildable without explicitly building the dependencies - sorry for the inconvinience

Answer 9 · 2022-06-09T10:57:49.000Z

Thanks a lot! Works great.