If you're solving this, it might be nice to also integrate this into the
building of maven artifacts so POMs have a <license> section - lots of
people use these for product license audits.

-Tim

On Wed, Jun 19, 2019 at 4:30 PM Matthias Bläsing <[email protected]>
wrote:

> Hi Jaroslav,
>
> Am Mittwoch, den 19.06.2019, 15:34 +0200 schrieb Jaroslav Tulach:
> > Hello guys, especially Matthias.
> >
> > We are about to import Apache NetBeans 11.x to OracleLabs projects like
> > VisualVM and IGV. To do so we need a legal approval. Ideally we would get
> > list of files
> > for the clusters that we need with their appropriate license:
> >
> > ```
> > platform cluster
> > ├── core
> > │   ├── asm-all-5.0.1.jar - BSD
> > │   ├── core-base.jar - APL2
> > │   ├── core.jar - APL2
> > │   ├── org-netbeans-libs-asm.jar - APL2
> > │   └── org-openide-filesystems.jar - APL2
> > ├── lib
> > │   ├── boot.jar - APL2
> > │   ├── nbexec - APL2
> > │   ├── nbexec64.dll - APL2
> > ```
> >
> > possibly with a hyperlink to the actual text of the license. What
> > would be the best way to generate such document? I know we can
> > generate the
> > LICENSE and DEPENDENCIES files with
> >
> > ```
> > nbbuild$ ant build-source-config -Dcluster.config=igv
> > nbbuild$ git diff .
> > diff --git a/nbbuild/cluster.properties b/nbbuild/cluster.properties
> > index 3523ff048..272f81016 100644
> > --- a/nbbuild/cluster.properties
> > +++ b/nbbuild/cluster.properties
> > @@ -40,6 +40,14 @@ clusters.config.basic.list=\
> >          nb.cluster.ergonomics
> >  # ergonomics must be last
> >
> > +clusters.config.igv.list=\
> > +        ${clusters.config.platform.list},\
> > +        nb.cluster.ide,\
> > +        nb.cluster.extide,\
> > +        nb.cluster.java,\
> > +        nb.cluster.nb,\
> > +        nb.cluster.webcommon
> > +
> >  clusters.config.standard.list=\
> >          ${clusters.config.java.list},\
> >          nb.cluster.apisupport,\
> > ```
> >
> > so we seem to have enough information. It is just about the "right
> > presentation".
> >
>
> I think you are already looking at the right place. The work of creating
> the LICENSE file,
> which holds the summary of the licenses, and copies the individual license
> files with the
> full text to the licenses subdir in the build tree is done in the
> `createlicensesummary`
> task. That task is implemented by
> org.netbeans.nbbuild.extlibs.CreateLicenseSummary
> class in the nbbuild project.
>
> This task scans two sources for information:
> - the external files definitions
> - the licenseinfo.xml files
>
> In both files the license names are required to be names of files in the
> nbbuild/licenses
> directory. This should make it possible to create links to the files.
>
> Gettings this per cluster might be more work, as the system tries to
> minimise the information
> and summarise it if possible. This is required, so that the NOTICE file
> follows the
> requirement to be minimal.
>
> I think that the above mentioned class should be a good start for an
> individual task
> tailored to your needs. While that task is focused on text files, creating
> HTML should be
> doable.
>
> HTH
>
> 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
>
>
>
>

-- 
http://timboudreau.com

Reply via email to