Yes, to clarify, our project has something like this:
<plugin>
<groupId>com.acme.plugin</groupId>
<artifactId>plugin</artifactId><!-- <- this is already on maven central -->
<version>4.2.42</version>
<dependencies>
<dependency>
<groupId>com.acme.plugin</groupId>
<artifactId>plugin-dep</artifactId><!-- <- this is NOT OSS -->
<version>42.4.2</version>
</dependency>
</dependencies>
</plugin>
On Thu, Feb 29, 2024 at 1:33 PM Tamás Cservenák <ta...@cservenak.net> wrote:
> Howdy,
>
> You would need to ask Sonatype about that, and check here:
> https://central.sonatype.org/publish/requirements/
>
> IMHO best to ask them about it: IIUC you want to deploy artifacts to
> central that has dependencies not available from Central
> (nor any other public repository?)
>
> Thanks
> T
>
>
>
> On Thu, Feb 29, 2024 at 1:31 PM Florent Biville <florent.bivi...@gmail.com
> >
> wrote:
>
> > Hello,
> >
> > I'm working on an open-source project that we want to release to Maven
> > Central in the coming weeks.
> >
> > The project currently includes a plugin dependency that is NOT
> open-source
> > (nor in a public GitHub repository). Is that a blocker for releases to
> > Maven Central? I know it would be for regular dependencies and plugins,
> but
> > I'm not 100% sure about plugin dependencies in particular (although I
> would
> > guess it's the same).
> >
> > Any input would be appreciated,
> >
> > Best regards,
> > Florent
> >
>
