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

Please publish an artifact to Maven Central #39

Open
rgoldberg opened this issue Jul 5, 2018 · 2 comments
Open

Please publish an artifact to Maven Central #39

rgoldberg opened this issue Jul 5, 2018 · 2 comments

Comments

@rgoldberg
Copy link

rgoldberg commented Jul 5, 2018

Please publish a Chainsaw artifact to Maven Central.

I want to use a custom plugin to apply Chainsaw (along with other standard plugins & configs) to all my Java builds.

For that, I think I need a dependency in my dependencies block.

If you know some other way to make com.zyxist.chainsaw.ChainsawPlugin available to my source, please let me know.

@mdavis95
Copy link

You might try using jitpack.io:

https://jitpack.io/#zyxist/chainsaw/chainsaw-0.3.1

repositories {
    maven { url 'https://jitpack.io' }
}

dependencies {
    compile 'com.github.zyxist.chainsaw:chainsaw:chainsaw-0.3.1'
}

@rgoldberg
Copy link
Author

rgoldberg commented Aug 13, 2018

@mdavis95 Thanks for the suggestion.

I've actually stopped using Chainsaw, and made my own fork.

Look at issues in the original repo to see things I've fixed.

All of my changes are in branches, but I've postponed creating most intermediate branches because they get in the way of rebasing.

To see the current state of the code, either use the branch renamed-plugin if you want to use a different plugin name, or use the commit immediately before the tip of that branch if you want to use the original plugin name.

I haven't published the current version of it to the Gradle Plugin Portal, because I keep updating it, but I can publish it if will help you; I'm trying to get the Gradle team to incorporate my improvements into their repo, to obviate the need for a separate plugin name…

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

No branches or pull requests

2 participants