I'm looking for a way to handle the use of LGPLv3 dependencies in a platform application with regard to the following:
- permit all users to exchange the library with other API-compatible library versions (e.g. those with security- & bug-fixes) As an end user, I replaced the dependency in question with a slightly older one in the depending module in modules/ext. It looks to be working fine, without updating the corresponding module xml's crc value. So my question is, is this an ok approach from a license and a module management point of view? /Patrik --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
