If you compile the SPDX Tools from source, please read the following and reply - preferably by Nov. 26.
I received a request and a contribution to move the SPDX source code to a Maven project build structure from Roger Meier. I also have a need increase the automation of the build process to reduce the effort of producing all the SPDX tools for every update. I personally would like to move to Maven myself for these tasks. I also believe it would improve the adoption of the SPDX tools source code. Since this may impact other users of the SPDX Tools source, please let me know if: A) This change will negatively impact your work and would like to keep things the way they are B) You really like this idea and would like to see SPDX tools move to Maven C) The change does not really impact how I use the source Also - let me know if you have any other questions, concerns, suggestions. Details on the change: - Addition of a Maven POM file - Remove the eclipse project metadata - Remove the lib and libsource directories and all dependent libraries (these would be pulled from an Maven repository) - Pull request for the change can be viewed at https://github.com/goneall/SPDX-Tools/pull/2 Licensing considerations: I would propose leaving the NOTICE file unchanged since the built binaries would still include these libraries even though they are pulled down at build time. The SPDX file for the SPDX Tools would no longer have the library files to specifically identify as an ArtifactOf that dependent project. In SPDX 2.0, we can include an SPDX relationship to the dependent libraries. Maven itself is licensed under Apache 2.0. Maven home page: http://maven.apache.org/ Gary ------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: <mailto:[email protected]> [email protected]
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
