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.

Sign up for GitHub

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

Jump to bottom

fix issue #428: use relative path instead of ${project.build.outputDirectory}/META-INF #430

Merged

danfickle merged 1 commit into danfickle:open-dev-v1 from syjer:428-fix-source-jar

Jan 17, 2020

Contributor

syjer commented Jan 15, 2020 •

edited

Loading

This fix issue #428 . I've checked the resulting jars and they are now correctly built (the final jar, the source jar the javadoc jars).

ATM I can't find any downside/issues.


          fix issue #428: use relative path instead of ${project.build.outputDi…

20f653b

…rectory}/META-INF

Owner

danfickle commented Jan 17, 2020

Thanks mate. Merging now.

danfickle merged commit 98fca08 into danfickle:open-dev-v1

danfickle mentioned this pull request

Upload to maven central via bintray. #7

Open

vstoykov mentioned this pull request

Sources jar contains absolute local path #428

Closed

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

Labels

None yet