-
Notifications
You must be signed in to change notification settings - Fork 3
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
Provide the lib in Maven central? #2
Comments
As in stapler/netbeans-stapler-plugin#6, yes. I need to go to some work to get Maven Central publishing set up. (https://github.com/sigstore/sigstore-maven promises to make that easier soon.) |
Alternatively you could also provide the nbm in the new plugin portal of NetBeans: https://plugins.netbeans.apache.org. Then NetBeans wouldn't complain that the module cannot be found, instead it should install it from the official plugin portal as a dependency for my plugin or other plugins. Maybe that's easier as the nbm is already published on Maven central. Thanks in advance. |
https://cwiki.apache.org/confluence/display/NETBEANS/How+to+get+plugin+on+Plugin+Portal+Update+Center claims that
I do have an OSSRH login already, just need to set aside a bit of time to file a request for a new component, make sure the POM here satisfies Central constraints, etc. |
I thought Yenta is already in Maven central, at least it says so here: |
Apparently added a decade ago, so quite possible! I guess I can try just deploying an update and see what happens… |
Any news on this? |
Hi @jglick,
if I reference the org.netbeans.contrib.yenta:api dependency in my NetBeans plugin it expects to have the org.netbeans.contrib.yenta:api nbm installed in the user's IDE where my plugin gets installed as the nbm-maven-plugin doesn't pack other nbms inside plugins, but if I reference the org.netbeans.contrib.yenta:lib (or any other jar file) it just packs it inside my plugin and it works like a charm. So the question is: Could you provide the org.netbeans.contrib.yenta:lib in Maven central?
Cheers,
Fabian
The text was updated successfully, but these errors were encountered: