The current design focused on getting the information in place, but an oversight has left a ticking time bomb. Eventually we will have two artifacts that have a name collision at the artifact id level, notable candidates include artifacts called "core" or "compiler" with no project related component to the name.
If the versions don't overlap we will still be technically covered, but the result would be confusing. In the extremely unlikely case of versions also matching we would possibly have a problem, which could be either an inability for the verifyLicenseDirs task to complete without error if the licenses are not the same or possibly silently failing to document a dependency when the licenses are also the same.
So this ticket is for improving the name-spacing. First thought is to add another level of directories for the package portion of the coordinates. This is attractive in that the Apache 2.0 directory is already huge, and aggregating some of the entries can only improve usability.
The current design focused on getting the information in place, but an oversight has left a ticking time bomb. Eventually we will have two artifacts that have a name collision at the artifact id level, notable candidates include artifacts called "core" or "compiler" with no project related component to the name.
If the versions don't overlap we will still be technically covered, but the result would be confusing. In the extremely unlikely case of versions also matching we would possibly have a problem, which could be either an inability for the
verifyLicenseDirstask to complete without error if the licenses are not the same or possibly silently failing to document a dependency when the licenses are also the same.So this ticket is for improving the name-spacing. First thought is to add another level of directories for the package portion of the coordinates. This is attractive in that the Apache 2.0 directory is already huge, and aggregating some of the entries can only improve usability.