[mojo-dev] [jira] (MLICENSE-102) Handling of dual licenses

[Stephan Schroevers (JIRA)]

Title: Message Title

Stephan Schroevers commented on an issue   Re: Handling of dual licenses +1 for this feature. Alternative implementation idea: only render/consider those licenses listed under <includedLicenses>. Warn (and optionally fail) if none (as opposed to "not all") of a module's licenses are listed. I realize that this change of semantics is not fully backwards compatible, but I'd argue it'd be more intuitive than the current behaviour. Add Comment   Mojo's License Maven Plugin / MLICENSE-102 Handling of dual licenses Licensing projects under dual licenses becomes a common option nowadays. A good example are EclipseLink projects, that are licensed under a choice of Eclipse Public License and Eclipse Distribution license. The plugin treats this as *both* license are applied: {code}      (Eclipse Distribution License v. 1.0) (Eclipse Public License v1.0) EclipseL... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email