Swagger Request Validator Core relies on POM with commercial license (v2.8.4)

[Samer Jalaleddine]

This is related to Issue #338.

In our case, we can’t use the newer version (major dependency conflicts). We are using version 2.8.4.

Would it be possible to have the same fix (shown above) on version 2.8.4? If modification to version 2.8.4 are not possible, could it be possible to have version 2.8.4 with the fix under a new version name (like 2.8.4-fix).

‌

Thanks in Advance

[James Navin]

Hi Samer,

As a general rule I try to avoid back-porting fixes unless they are critical, and I cannot modify an existing version (released versions are immutable in Maven).

It might help me to understand what is preventing you from rolling forward to the version with the updated POM - there might be a path forward there (we have discussed culling some dependencies that are only lightly used - we might be able to prioritize that if it’s one of them that is blocking you).

Otherwise - if you are pinned to this version is there anything stopping you using a forked version of the lib with the POM update applied? If you can’t roll forward to pick up changes and bug fixes then you won’t be losing much by maintaining your own fork.

Let me know if either of those options work for you.

Cheers,

James

[Samer Jalaleddine]

Hello James,

First of all thanks for the well put reply.

Regarding using the newer version, we end up with dependency conflicts. For instance, within the codeline the version of “com.fasterxml.jackson.core” can’t be changed without causing errors elsewhere (lots of code that relies on that set version). Our version of Jackson sadly doesn’t work with the new Swagger Request Validator.

Regarding forking our own version, it would require added effort to maintain the fork which was deemed not worth it.

I’ll see with the team if they have any ideas as well.

‌

Thanks,

Samer