users will not be able to rebuild from sources.
is it a requirement? No real idea as already said in this thread, you
need to ask Sonatype.
But it breaks the concept of opensource as you cannot build from the sources :)

On Fri, 1 Mar 2024 at 02:25, Florent Biville <florent.bivi...@gmail.com> wrote:
>
> The real plugin is com.mycila:license-maven-plugin
> <https://github.com/mathieucarbou/license-maven-plugin> and the non-OSS
> dependency brings a bunch of extra resources (authorized licenses,
> headers...).
>
> On Thu, Feb 29, 2024 at 2:14 PM Slawomir Jaranowski <s.jaranow...@gmail.com>
> wrote:
>
> > I can not fine mentioned plugin at all ...
> > https://repo.maven.apache.org/maven2/com/acme/
> >
> > What does it do ...?
> > Is it needed for the build project?
> > Can it be executed in profile?
> > Can it be replaced by something else ...?
> >
> > I will think about publishing projects which can not be build by outer
> > users, can not be a reproducible build check and so on ...
> >
> > So I would like to not publish something like this...
> >
> >
> >
> > czw., 29 lut 2024 o 13:41 Florent Biville <florent.bivi...@gmail.com>
> > napisał(a):
> >
> > > 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
> > > > >
> > > >
> > >
> >
> >
> > --
> > Sławomir Jaranowski
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to