plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <>
Subject Re: Including AL 2.0 content?
Date Tue, 26 Dec 2017 14:32:17 GMT
And for one license I couldn’t see if this is compatable:
The FontAwesome fonts are licensed under “SIL OFL 1.1” (
Is this compatable with the AL 2.0?


Am 26.12.17, 12:44 schrieb "Christofer Dutz" <>:

    Hi Justin,
    thanks for the feedback … I did apply the configuration I did for the Edgent project
to here so now I could add the LICENSE and NOTICE attributions.
    The thing is, that the reflow skin does bundle the listed software. Some are graphic resources
and some are CSS frameworks or JavaScript libs. In the end, they are used and they are added
to our build-output so I listed all of them. I also added the stuff for FontAwesome as this
wasn’t listed yet. 
    However, the thing is that these resources are only used for generating the site. Not
a single line of them is output to the individual build artifact. I don’t quite know how
to deal with this. So, I added a headline for all of these attributions that these only apply
to the generated site.
    Would be cool, if there was a way to provide attributions for artifact and site separately,
but it seems this isn’t possible (Mabe I should ask the Maven guys on this matter)
    What would be the ideal way to handle this?
    Am 26.12.17, 11:12 schrieb "Justin Mclean" <>:
        > I was able to override this, by copying the original template from here:
        > To here:
        > So, is this ok to do so? Would I need some additional attribution?
        Look OK to me, Apache licensed software doesn't require attribution. It does however
have a NOTICE file [1] so I would add this to NOTICE:
        Reflow Maven skin and Velocity tools
        Copyright 2012 Andrius Velykis
        (as the rest of the NOTICE file doesn't seem to be bundled)
        You can also add it to LICENSE [2] but it’s not required.

View raw message