Hello team, for easier understanding how the Aries components are connected with each other I want to use a maven plugin to generate some graphs. The work I have done so far is in https://github.com/apache/aries/pull/437 with generated images in description.
To have common configuration I want to set current aries parent pom as parent of submodules. When running the CI builds some files do not have licence header. I easily fixed it in transaction https://github.com/apache/aries/pull/438 but for subsystem module the number of missing files is much bigger and not so straightforward. Firstly, there are some java files without license, unused files in tests and files cfg and sausages that seem to not support comments. I am fixing those files in PR https://github.com/apache/aries/pull/440 Secondly, there are some submodules in subsystem that have version 0.1-SNAPSHOT so it looks like those modules have been never released and are not even part of subsystem reactor. In those directories there are many files without licenses. I propose moving these maven modules to sandbox directory in https://github.com/apache/aries/pull/439 Are you ok with the changes above? In the long term, I think we can remove directories that are not part of the reactor: - sandbox (last significant change 12 years ago) - tutorials (last significant change 13 years ago) We can mark with tag the the last commit sha containing this modules to easily be able to bring back any parts, just in case. There is also samples directory excluded from reactor and it's a different story - the samples are even part of the public website https://aries.apache.org/documentation/modules/samples.html This subproject is not buildable right now but I believe that it may be possible when all the other submodules are updated to support modern java versions and completely drop java 6. Let me know what's your opinion about such long term cleanup. -- Regards, Dominik Przybysz
