[JENKINS-72981] Inline EZMorph repository

[BobDu]

json-lib has a exclusive dependency libary ezmorph

Currently, we not have a fork for ezmorph. However, the refactoring work will inevitably involve modifications to the content of ezmorph. Considering the singularity of dependencies. It is also unnecessary to separately split ezmorph into an independent repository and jar package.

So, attempting merge ezmorph into this repository.

I make a ezmorph readonly git mirror from origin cvs for reference, and copy all java code into this repo.

https://github.com/BobDu/ezmorph

@basil

Testing done

Submitter checklist

Preview Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[KalleOlaviNiemitalo]

Does the ezmorph source tree contain a NOTICE file as referenced by clause 4.d. of the Apache-2.0 license? Or any other legal notices that would have to be copied with the Java files.

[BobDu]

Does the ezmorph source tree contain a NOTICE file as referenced by clause 4.d. of the Apache-2.0 license? Or any other legal notices that would have to be copied with the Java files.

I make a readonly git repository replica covert from origin cvs repo.

https://github.com/BobDu/ezmorph

In the original repository, there are no additional notice files.

[basil]

Very nice! Can you also copy over the package.html files from the original repository? We have the package.html files for JSON-lib in this repository, so we should keep the package.html files from EZMorph to be consistent.

What's the reason for removing the unused files in commit 1cf9067, and how do you know they are unused? In theory the only way to prove that a plugin isn't consuming them would be using https://github.com/jenkins-infra/usage-in-plugins. And this also dilutes the semantics of this PR, since it's now doing two things, a code import and a code cleanup. I think I would rather let this PR be a simple import and defer the code cleanup to another PR, unless there was a particular reason to do so here.

[BobDu]

so we should keep the package.html files from EZMorph to be consistent.

Origin package.html file has some html tag syntax error cause CI failed, and there doesn't seem to be any meaningful information. So, I rough delete it.
But I agree with your point of view, keep copying the original code as much as possible in this PR except for fixing CI errors.

I think I would rather let this PR be a simple import and defer the code cleanup to another PR

+1, I will revert this commit in this PR

[BobDu]

Origin package.html file has some html tag syntax error cause CI failed

Sorry, I made a mistake. Looks like a hint but does not cause failure.
So let’s not modify it yet, in this PR.

[basil]

Thanks for the PR!

I have confirmed that these sources exactly match the contents of the 1.0.6 sources JAR on Maven Central and the CVS repository checked out via:

cvs -z3 -d:pserver:anonymous@ezmorph.cvs.sourceforge.net:/cvsroot/ezmorph co -r REL_1_0_6 -P ezmorph

There was a minor textual merge conflict in the log4j properties file, which I resolved in favor of EZMorph to ensure that tests have proper debug logs.