Hey all, we have artifacts we will need to distribute, but (potentially) can't hold in the repository. Apache has a statement on this:
https://www.apache.org/legal/resolved.html#no-modification I consider this bad practise, as it means the project will depend on potentially fragile third party hosting. Legal tickets for these files/licenses are opened, but I'd like to prepare for the worst-case. My suggestion is this: I'll package the files with correct license attribution as maven artifacts and get them published to maven central. The artifacts would be packed as jars/zips and this would happen under a personal group id. The artifacts would not be under the control of the netbeans project, but they are not expected to be changing (html DTDs, entity definitions, WSDL Definitions,...) and won't be removed from it. We are already using maven central to access common artifacts and I think this would be a good middle ground. Thoughts? Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
