Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License URL in third-party file #75

Open
simonklb opened this issue Feb 9, 2017 · 4 comments
Open

License URL in third-party file #75

simonklb opened this issue Feb 9, 2017 · 4 comments

Comments

@simonklb
Copy link

simonklb commented Feb 9, 2017

It would be nice to have the possibility to include more than just the license name in the third party file. Any chance that the license URL could be made available to the template file as well?

@jahlborn
Copy link

jahlborn commented May 9, 2017

Yes, this would be very useful especially for "custom" licenses. Today, we are just including the url as part of the name, e.g. "project--1.0=Custom License - http://project/path". Maybe the license plugin could parse that and split it into name and url info?

@tchemit tchemit modified the milestone: Backlog Jun 11, 2017
@tchemit
Copy link
Contributor

tchemit commented Jun 30, 2017

@simonklb @jahlborn which file are you talking about ?

the missing license file ? (THIRD-PARTY.properties).

Yes it would be a great idea. The best to thing to do would to use here one of the predefined license name (named a gplv3, agpl, ...) this name is related to a full definition of a license .

Do you get me ?

@tchemit tchemit modified the milestones: 1.14, Backlog Jun 30, 2017
@tchemit tchemit self-assigned this Jun 30, 2017
@simonklb
Copy link
Author

@tchemit Sorry, I'm not really following you here. What we want is to be able to link to the license via an URL. This is mostly needed for custom licenses, like @jahlborn mentioned. For well-known licenses there is no problem for people to find them online.

@jahlborn
Copy link

To confirm, yes we are referring to the THIRD-PARTY.properties file. And to reiterate what @simonklb said, this is desirable for custom licenses, e.g. jdom http://www.jdom.org/docs/faq.html#a0030 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants