Blocked mirror for ipdNexus

[sloboegen]

Hi!

Due to the specifics of my task, I have to work only with the second version of JPlag (JPlag v.2.12.1).

I have the following error while running the command mvn clean generate-sources assembly:assembly inside jplag-folder:

[INFO] >>> maven-assembly-plugin:2.4:assembly (default-cli) > package @ jplag >>>
Downloading from maven-default-http-blocker: http://0.0.0.0/edu/kit/ipd/jplag/text/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata edu.kit.ipd.jplag:text:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/edu/kit/ipd/jplag/text/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] edu.kit.ipd.jplag:text:0.0.1-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata edu.kit.ipd.jplag:text:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/edu/kit/ipd/jplag/text/0.0.1-SNAPSHOT/maven-metadata.xml
Downloading from maven-default-http-blocker: http://0.0.0.0/edu/kit/ipd/jplag/java-1.7/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata edu.kit.ipd.jplag:java-1.7:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/edu/kit/ipd/jplag/java-1.7/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] edu.kit.ipd.jplag:java-1.7:0.0.1-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata edu.kit.ipd.jplag:java-1.7:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/edu/kit/ipd/jplag/java-1.7/0.0.1-SNAPSHOT/maven-metadata.xml
Downloading from maven-default-http-blocker: http://0.0.0.0/edu/kit/ipd/jplag/python-3/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata edu.kit.ipd.jplag:python-3:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/edu/kit/ipd/jplag/python-3/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] edu.kit.ipd.jplag:python-3:0.0.1-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata edu.kit.ipd.jplag:python-3:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/edu/kit/ipd/jplag/python-3/0.0.1-SNAPSHOT/maven-metadata.xml
Downloading from maven-default-http-blocker: http://0.0.0.0/edu/kit/ipd/jplag/csharp-1.2/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata edu.kit.ipd.jplag:csharp-1.2:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/edu/kit/ipd/jplag/csharp-1.2/0.0.1-SNAPSHOT/maven-metadata.xml
[WARNING] edu.kit.ipd.jplag:csharp-1.2:0.0.1-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata edu.kit.ipd.jplag:csharp-1.2:0.0.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/edu/kit/ipd/jplag/csharp-1.2/0.0.1-SNAPSHOT/maven-metadata.xml
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.750 s
[INFO] Finished at: 2022-04-15T16:16:27+03:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project jplag: Could not resolve dependencies for project edu.kit.ipd.jplag:jplag:jar:2.12.1-SNAPSHOT: Failed to collect dependencies at edu.kit.ipd.jplag:text:jar:0.0.1-SNAPSHOT: Failed to read artifact descriptor for edu.kit.ipd.jplag:text:jar:0.0.1-SNAPSHOT: Could not transfer artifact edu.kit.ipd.jplag:text:pom:0.0.1-SNAPSHOT from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [ipdNexus (http://bob.ipd.kit.edu/nexus/repository/maven-public-all, default, releases+snapshots)] -> [Help 1]

Could you tell, please, is this a temporary problem with ipdNexus or http://bob.ipd.kit.edu/nexus/repository/maven-public-all is completely unavailable? If it's not temporary, what should I do to successfully build JPlag v.2.12?

[tsaglam]

v2.12.1 is the legacy version of JPlag. While its sources a still available on the legacy branch, they are outdated. The servers you mentioned are either offline or no longer used by JPlag. Some of the legacy component, for example the web service, are no longer in use. To build the legacy version, you should remove the references to this server.
What are the specific of your task that makes you choose the legacy version?

[sloboegen]

The specificity is that there are matches that JPlag2 finds but JPlag3 does not. And I don't want these matches to be lost. For example:

JPlag3 breaks the match at lines with is Empty() / size() == 0, (int) a.get(i +1) / l.get(i + 1) and seems to skip matches due to presence/absence of braces. In my experiment, because of such behavior JPlag3 returned 10% similarity for a pair of plagiarized programs, while JPlag2 returned 70%.

Maybe the third version can be made a little less sensitive so that such matches can be found? In that case, I would happily use JPlag3.

[tsaglam]

Ah, that seems to be a separate issue. I will investigate this and see what I can do. Which java frontend do you use in the legacy version? This might be a possible source of this difference.
As a hotfix, you might play with the min token match argument, which is available in both versions (but the CLI syntax may vary). A lower min token match increases sensitivity but might also increase the chance for false positives.

[sloboegen]

I use frontend for Java17. Ok, I'll try to play with the min token argument.

So I'll close this discussion and duplicate everything as an issue!