Publish jazzer plugin #103
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds publishing of the Jazzer plugin. It will NOT be published on the Gradle plugin portal, but on Maven Central only. This shouldn't be an issue, except that users won't be able to find it when searching on the plugin portal (similarly to the native build tools). It may be worth checking before a 1.0.0 release with a beta version or something, since the setup is a bit special. Fixes #100
# Conflicts: # fuzzing-tests/src/main/java/io/micronaut/fuzzing/http/CustomResourceLeakDetector.java
|
Thanks! Re the weird project structure, I've also created #101 for you, which may help. But that's not urgent. |
|
Yes I'm on it right now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds publishing of the Jazzer plugin. It will NOT be published on the Gradle plugin portal, but on Maven Central only. This shouldn't be an issue, except that users won't be able to find it when searching on the plugin portal (similarly to the native build tools).
It may be worth checking before a 1.0.0 release with a beta version or something, since the setup is a bit special.
Fixes #100