-
Notifications
You must be signed in to change notification settings - Fork 15
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
Implement pom.xml definitions for compliance with OSSRH #2 #3
Conversation
Thanks for the contribution. Can you correct the license you specify in the pom.xml? You made it Apache, but in reality the original jj2000 developers used their own license, which is specified in the COPYRIGHT file in the base of the repo. |
Hi Ryan... Doh, yes will do so. Sending PR ASAP thanks for review. On Wednesday, April 22, 2015, Ryan May notifications@github.com wrote:
Lewis |
hi @dopplershift I've removed the license but retainer the license markup. The reasoning is that there is a COPYRIGHT, but no License I can see. If you see differently then please inform and I will update again. |
When I read the COPYRIGHT file, it sounds like a license:
|
Hi Ryan, if you have a suggestion about which license then I would be only On Thursday, April 23, 2015, Ryan May notifications@github.com wrote:
Lewis |
Personally, I'd just call it the jj2000 license. If it needs to be a known license, then I'd leave it blank. I can take care of that later if you don't want to bother. |
@dopplershift done :) |
Implement pom.xml definitions for compliance with OSSRH Fixes #2.
Thanks for working this out! |
no problems |
Hi Folks (specifically @JohnLCaron ),
This is a pull request which will allow us to distribute this artifact via Maven Central as per the workflows which we have been working to. The proposed changes fit in with the existing workflow but you will now see that javadoc.jar and sources.jar artifacts accompany the usual .jar
Thanks
Lewis