Description
I was thinking for a while already to merge the DNSSEC resolver implemented in dnssecjava into dnsjava but wasn't sure this is the right thing to do.
Pros:
- dnssecjava is useless without dnsjava and closely depends on the API
- might proliferate DNSSEC a bit
- large test coverage
- parts of dnssecjava's tests depend on internal/private dnsjava API to achieve coverage
Cons:
- my personal interest
- different project licenses 1
- change of package for dnssecjava
- jar size increase 2
Thoughts?
-
The original license of dnssecjava was BSD-3-Clause (c) VeriSign. I applied LGPL and later EPL to my work, keeping the BSD-3-Clause notice to stay compliant with it. The test replay files from unbound are also BSD-3-Clause. The only external contributions were very small and by people privately asking for a more liberal license (when it was still LGPL), one from VeriSign. Relicensing it back to BSD-3-Clause is thus possible.
However, it would probably be best to keep a single license on dnsjava, meaning a switch from BSD-2-Clause to BSD-3-Clause (which is adding:3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.). I don't think this is an issue. -
Size comparison:
| Project | Compressed | Uncompressed |
|---|---|---|
| dnsjava | 395 KiB | 811 KiB |
| dnssecjava | 51 KiB | 113 KiB |
| merged (including metadata) | 491 KiB | 923 KiB |