doc directory and multi-module projects
Ian Young
ian at iay.org.uk
Sun Jun 30 10:12:09 EDT 2013
The scripts that we use to create new monolithic projects create a doc/ directory with a LICENSE.txt and an empty RELEASE-NOTES.txt file. Seems pretty obvious, really.
The corresponding scripts to create a multi-module project, and add modules to such a project do not do this.
Where, if anywhere, should the doc directory (or potentially directories) live in such a situation? We don't seem to have anything like this in the current V3 sources, either the OpenSAML part of the IdP part.
I think one axis we can consider this on is the question of how the end user might acquire things like release notes. Obviously there's not much point shipping per-module release notes inside a Maven .jar artifact, so perhaps they only need to appear in things with more complex distribution packages. Even then, it's not obvious to me how we'd avoid duplication where we have multiple packagings, potentially from different modules. Maybe we just have to avoid that.
Curious,
-- Ian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4813 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20130630/bb932102/attachment.bin
More information about the dev
mailing list