You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2018/07/03 17:36:01 UTC

JENA-1572 - Tidy up LICENSE and NOTICE

The LICENSE and NOTICE files can be tided up. They were setup so 
individual modules can be released by themselves but Jena now releases 
all modules at once.

So the L&N can be reduced to:

* One (of each) in the root of the source repo.

* One per distribution binary where the binary includes things not in 
the repo (but linked to by maven).

* One in each jar. The automatically generated one probably isn't good 
enough. What I don't know is whether it can be the top-level one or per 
module (which does rather infer with the tidying up exercise).

Dist areas:
+ apache-jena/dist
+ apache-jena-osgi/dist
+ jena-fuseki2/apache-jena-fuseki/dist/
+ jena-fuseki1/dist/

We could drop the Fuseki1 distribution and just make the server jar.  It 
needs L&N to reflect the included dependencies.

Consequences:

* Javascript means source in the repo so all the MIT license refs need 
mentioning in the top level.

     Andy

JENA-1572 has my assessment of all the current L&N files.
JENA-1571 removes the dist/ and assembly for jena-sdb.

Re: JENA-1572 - Tidy up LICENSE and NOTICE

Posted by Andy Seaborne <an...@apache.org>.
Fuseki1 and SDB distribution building removed.

https://issues.apache.org/jira/browse/JENA-1571 -- SDB

https://issues.apache.org/jira/browse/JENA-1573 -- Fuseki1.

Anyone can get the necessary jars files from maven central tif they want 
to keep their installations up-to-date and they don't use a dependency 
manager.

     Andy

Names on my commits may be wrong but it only impacts the JIRA comment, 
the git commit itself is correct.

Logged with INFRA:
https://issues.apache.org/jira/browse/INFRA-15850


On 03/07/18 18:36, Andy Seaborne wrote:
> The LICENSE and NOTICE files can be tided up. They were setup so 
> individual modules can be released by themselves but Jena now releases 
> all modules at once.
> 
> So the L&N can be reduced to:
> 
> * One (of each) in the root of the source repo.
> 
> * One per distribution binary where the binary includes things not in 
> the repo (but linked to by maven).
> 
> * One in each jar. The automatically generated one probably isn't good 
> enough. What I don't know is whether it can be the top-level one or per 
> module (which does rather infer with the tidying up exercise).
> 
> Dist areas:
> + apache-jena/dist
> + apache-jena-osgi/dist
> + jena-fuseki2/apache-jena-fuseki/dist/
> + jena-fuseki1/dist/
> 
> We could drop the Fuseki1 distribution and just make the server jar.  It 
> needs L&N to reflect the included dependencies.
> 
> Consequences:
> 
> * Javascript means source in the repo so all the MIT license refs need 
> mentioning in the top level.
> 
>      Andy
> 
> JENA-1572 has my assessment of all the current L&N files.
> JENA-1571 removes the dist/ and assembly for jena-sdb.