This repository has been archived by the owner on May 11, 2021. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix #89: Keep compile dependencies scope also in pom.xml
Due to a maven-publish plugin limitations all dependencies are set to runtime.
- Loading branch information
ee21c8f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very ugly hack... Why not maven-plugin? It works as expected.
ee21c8f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to integrate bintray plugin with maven-plugin?
ee21c8f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In short not, but you can upload artifacts with gradle task.
ee21c8f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about fixing that in maven-publish on the upcoming hackathon, but looking in the code at that stage they seem to keep all dependencies as runtimeDependencies with no information about actual classifier. It would be probably (I hope I am wrong) a bigger change in the whole new publishing mechanism :(.