You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I forgot that I'd meant to file this separately from #21, etc.
One step is that to pick an artifact name. We are likely to actually be publishing two new artifacts, one for the forked Checker Framework and one for our plugin, in which case we need to pick two artifact names. For a naming discussion about this repo (which we could apply to at least one of our artifacts), see #25.
The text was updated successfully, but these errors were encountered:
We already have permissions for org.jspecify [in Maven Central]. That might be enough to upload artifacts under a new artifact ID? The other part of the process is to figure out how to actually upload the relevant jars, poms, manifests, or whatever that our own build process may or may not automatically spit out. Since we're distributing both a Checker Framework fork and a plugin, that might actually mean a couple new artifacts, or else we need to find a way to merge them.
For completeness: IIUC ownership of coordinates foo.bar on Maven Central also grants exclusive ownership of all group IDs below those coordindates, such as foo.bar.baz. So you could also upload under (say) group ID org.jspecify.checker.
(No idea whether that'd be desirable, though. Naming is hard 😅.)
I forgot that I'd meant to file this separately from #21, etc.
One step is that to pick an artifact name. We are likely to actually be publishing two new artifacts, one for the forked Checker Framework and one for our plugin, in which case we need to pick two artifact names. For a naming discussion about this repo (which we could apply to at least one of our artifacts), see #25.
The text was updated successfully, but these errors were encountered: