Re: Platform modules from 3rd parties - how to expose them?

It would be somewhat doable to add a maven repo feature to Meta Update
Server - https://github.com/timboudreau/meta-update-center

The challenge would be deriving the dependencies section for the POM
correctly, since NetBeans code-name-base entries don't have to have any
connection to the groupId/artifactId - bit of an impedance mismatch there
that's impossible to solve 100% algorithmically.  So maybe this only works
for NBMs that include a POM file.

I don't think the licenses of 3rd party modules are especially problematic
in general - the way the IDE does it is to concatenate a bunch of licenses
and show it to the user on startup, and I think that works for platform
apps too - and the license agreement is shown when a user updates.  So
unless that feature's been disabled for your application, the user has to
agree to it.

-Tim



On Tue, Apr 26, 2016 at 1:02 AM, Peter Hansson <[email protected]>
wrote:

> > Bundling external plugins by default with your NB platform application
> may be difficult from a legal perspective. You still have to display
> license texts or what ever.
>
> Not sure I understand the problem. Don't we - as developers - face the
> same challenge with each and every dependency we pull into our project from
> Maven Central? In each case we need to check (manually) if the license is
> compatible with what we want. This is no different. When we include
> something at build time it's us as developers who accept licenses, not the
> end user. That is one big difference between a Maven Repo Server and an
> Update Center.
>
> Peter
>
>
>


-- 
http://timboudreau.com