You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by Tim Allison <ta...@apache.org> on 2021/08/17 12:55:53 UTC

[DISCUSS] release pipes artifacts?

All,
   The pipes artifacts are available via maven central, but they
aren't currently part of our release, which means that the built jars
aren't signed or hashed.  For non-java folks (see TIKA-3523), this can
be a pain.
    Should we release the jars for the pipes components with our
standard release or let maven central/build your own be the solution?
   I'm somewhat inclined toward the former -- release the pipes jars.  WDYT?

        Best,

                 Tim

Re: [DISCUSS] release pipes artifacts?

Posted by Tim Allison <ta...@apache.org>.

Wait, the keys and digests are published in maven central:
https://repo1.maven.org/maven2/org/apache/tika/tika-fetcher-http/2.0.0/

Question remains, though.  Do we want to release these artifacts via
Apache releases or is it good enough that users can pull them from
maven?

On Tue, Aug 17, 2021 at 8:55 AM Tim Allison <ta...@apache.org> wrote:
>
> All,
>    The pipes artifacts are available via maven central, but they
> aren't currently part of our release, which means that the built jars
> aren't signed or hashed.  For non-java folks (see TIKA-3523), this can
> be a pain.
>     Should we release the jars for the pipes components with our
> standard release or let maven central/build your own be the solution?
>    I'm somewhat inclined toward the former -- release the pipes jars.  WDYT?
>
>         Best,
>
>                  Tim