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

Publish artifacts #100

Closed
yawkat opened this issue Jan 3, 2025 · 0 comments · Fixed by #103
Closed

Publish artifacts #100

yawkat opened this issue Jan 3, 2025 · 0 comments · Fixed by #103
Assignees
Labels
type: enhancement New feature or request

Comments

@yawkat
Copy link
Member

yawkat commented Jan 3, 2025

Issue description

I would like to start publishing artifacts from this repository to maven central. In particular:

  • fuzzing-api, a standard library artifact
  • fuzzing-annotation-processor, an annotation processor (based on the micronaut-core processor)
  • jazzer-plugin, a gradle plugin that consumes metadata generated by the annotation processor to either run jazzer directly, or to generate oss-fuzz test cases.

Additionally, if it's no issue there should be a bom with the managed jazzer dependency from the libs toml.

The reason for publishing these artifacts is that I would like to migrate the netty oss-fuzz tests to this infrastructure.

@yawkat yawkat added the type: enhancement New feature or request label Jan 3, 2025
melix added a commit that referenced this issue Jan 6, 2025
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants