[JIRA] (IDP-2019) Get LDAPTIVE 2 build to pass the enforcer checks

[Rod Widdowson (Jira)]

Rod Widdowson ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=59fb32bbc24efb3c4ed3c977 ) *commented* on IDP-2019 ( https://shibboleth.atlassian.net/browse/IDP-2019?atlOrigin=eyJpIjoiZjIxMDgyNWVkZDA2NDkyZmFiMzU5ODE4YjI1ZGIzZTciLCJwIjoiaiJ9 )

Re: Get LDAPTIVE 2 build to pass the enforcer checks ( https://shibboleth.atlassian.net/browse/IDP-2019?atlOrigin=eyJpIjoiZjIxMDgyNWVkZDA2NDkyZmFiMzU5ODE4YjI1ZGIzZTciLCJwIjoiaiJ9 )

Initial failures

Duplicates (different versions) found parsing the poms
org.ldaptive+ldaptive         :      1.3.1 (from parent pom.) and 2.1.1 (from provided pom)
File netty present with versions buffer-4.1.75.Final and codec-4.1.75.Final
File netty present with versions codec-4.1.75.Final and common-4.1.75.Final
File netty present with versions common-4.1.75.Final and handler-4.1.75.Final
File netty present with versions handler-4.1.75.Final and resolver-4.1.75.Final
File netty present with versions resolver-4.1.75.Final and transport-4.1.75.Final
File netty present with versions transport-4.1.75.Final and transport-classes-epoll-4.1.75.Final
File netty present with versions transport-classes-epoll-4.1.75.Final and transport-classes-kqueue-4.1.75.Final
File netty present with versions transport-classes-kqueue-4.1.75.Final and transport-native-epoll-4.1.75.Final-linux-x86_64
File netty present with versions transport-native-epoll-4.1.75.Final-linux-x86_64 and transport-native-kqueue-4.1.75.Final-osx-x86_64
File netty present with versions transport-native-kqueue-4.1.75.Final-osx-x86_64 and transport-native-unix-common-4.1.75.Final

The ldaptive one is because I short cuttted the build and hacked the idp-parent pom rather than the parent project. the rest falls into (I think) two categories

* The netty-* jars are not explicitly reference in any of our poms and so we need to set up the mappings in artifactMap.properties
* The netty project uses some very funky classifiers for their “transport” jars

I’ll fix the first one first because I want a record of what the next failure looks like

( https://shibboleth.atlassian.net/browse/IDP-2019#add-comment?atlOrigin=eyJpIjoiZjIxMDgyNWVkZDA2NDkyZmFiMzU5ODE4YjI1ZGIzZTciLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-2019#add-comment?atlOrigin=eyJpIjoiZjIxMDgyNWVkZDA2NDkyZmFiMzU5ODE4YjI1ZGIzZTciLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100207- sha1:591c2ef )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20221008/355b6c1d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-58991f33-6e3c-4fec-9209-55a0837b0de0
Type: image/png
Size: 452 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221008/355b6c1d/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-ad8453cf-b7ae-4581-86c5-a6c2da8a4507
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221008/355b6c1d/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-2e4e6b0b-6f2a-43a5-a262-81b2062f78f1
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20221008/355b6c1d/attachment-0005.png>