Maven repository 1.4 missing parent

[Michele Sonnessa <so...@gmail.com>]

Dear all,

I’m trying to build and extension using brand new 1.4 api.
Unfortunately maven compilation fails because recent library versions depend on a parent pom
which is not generally available on maven central repository.

Did you miss to publish it or I’m missing something?

Thanks in advance,
Michele

Re: Maven repository 1.4 missing parent

[Nick Couchman <vn...@apache.org>]

On Wed, Jan 5, 2022 at 1:25 PM Mike Jumper <mj...@apache.org> wrote:

> On Wed, Jan 5, 2022 at 8:32 AM Nick Couchman <vn...@apache.org> wrote:
> >
> > On Wed, Jan 5, 2022 at 10:06 AM Michele Sonnessa <so...@gmail.com>
> wrote:
> >
> > > Dear all,
> > >
> > > I’m trying to build and extension using brand new 1.4 api.
> > > Unfortunately maven compilation fails because recent library versions
> > > depend on a parent pom
> > > which is not generally available on maven central repository.
> > >
> > >
> > I see the artifacts present on the central repository:
> >
> >
> https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-common/1.4.0
> >
> https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-common-js/1.4.0
> >
> https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-ext/1.4.0
> >
> > Not sure what is missing in your environment, but the officially
> published
> > ones for the new version of Guacamole appear to all be present. It's
> > possible that certain mirrors or repositories may take longer to update,
> so
> > you might just check back, or make sure you're using the official
> versions
> > noted above.
> >
>
> I'm seeing this issue as well. With the guacamole-client source having
> been restructured to leverage a parent artifact to control
> dependencies, things like guacamole-common depend on that parent, and
> anything that depends on those subprojects will fail to build unless
> the parent is available within the local repository.
>
> We should adjust our testing procedures, CI builds, etc. such that
> this fails going forward, but for now the 1.4.0 artifacts in Maven
> Central will not be usable except if the main guacamole-client 1.4.0
> source happens to already have been built locally.
>
> Possible solutions would be:
>
> * Verify there is no issue with publishing the guacamole-client build
> artifact in general, and call another vote for including the
> erroneously-omitted guacamole-client build artifact within 1.4.0. If
> that vote passes, we push the artifact. This feels to me like it would
> be within policy, but I'm not 100% positive.
>
>
Fine with me.


> * Get started on a 1.4.1 release to patch the issue.
>
> If at all possible, my personal preference would be to avoid doing an
> entire release for a binary-only issue relevant only to the Maven
> upload. That said, if there _is_ an issue with uploading the
> guacamole-client artifact, then a 1.4.1 is unavoidable.
>
>
I'm okay with this, as well - depending on how critical it is to resolve
this, we could possibly squeeze a few bug fixes into a 1.4.1 release, too.

Either way is good with me.

-Nick

Re: Maven repository 1.4 missing parent

[Mike Jumper <mj...@apache.org>]

On Wed, Jan 5, 2022 at 8:32 AM Nick Couchman <vn...@apache.org> wrote:
>
> On Wed, Jan 5, 2022 at 10:06 AM Michele Sonnessa <so...@gmail.com> wrote:
>
> > Dear all,
> >
> > I’m trying to build and extension using brand new 1.4 api.
> > Unfortunately maven compilation fails because recent library versions
> > depend on a parent pom
> > which is not generally available on maven central repository.
> >
> >
> I see the artifacts present on the central repository:
>
> https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-common/1.4.0
> https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-common-js/1.4.0
> https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-ext/1.4.0
>
> Not sure what is missing in your environment, but the officially published
> ones for the new version of Guacamole appear to all be present. It's
> possible that certain mirrors or repositories may take longer to update, so
> you might just check back, or make sure you're using the official versions
> noted above.
>

I'm seeing this issue as well. With the guacamole-client source having
been restructured to leverage a parent artifact to control
dependencies, things like guacamole-common depend on that parent, and
anything that depends on those subprojects will fail to build unless
the parent is available within the local repository.

We should adjust our testing procedures, CI builds, etc. such that
this fails going forward, but for now the 1.4.0 artifacts in Maven
Central will not be usable except if the main guacamole-client 1.4.0
source happens to already have been built locally.

Possible solutions would be:

* Verify there is no issue with publishing the guacamole-client build
artifact in general, and call another vote for including the
erroneously-omitted guacamole-client build artifact within 1.4.0. If
that vote passes, we push the artifact. This feels to me like it would
be within policy, but I'm not 100% positive.

* Get started on a 1.4.1 release to patch the issue.

If at all possible, my personal preference would be to avoid doing an
entire release for a binary-only issue relevant only to the Maven
upload. That said, if there _is_ an issue with uploading the
guacamole-client artifact, then a 1.4.1 is unavoidable.

- Mike

Re: Maven repository 1.4 missing parent

[Nick Couchman <vn...@apache.org>]

On Wed, Jan 5, 2022 at 10:06 AM Michele Sonnessa <so...@gmail.com> wrote:

> Dear all,
>
> I’m trying to build and extension using brand new 1.4 api.
> Unfortunately maven compilation fails because recent library versions
> depend on a parent pom
> which is not generally available on maven central repository.
>
>
I see the artifacts present on the central repository:

https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-common/1.4.0
https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-common-js/1.4.0
https://mvnrepository.com/artifact/org.apache.guacamole/guacamole-ext/1.4.0

Not sure what is missing in your environment, but the officially published
ones for the new version of Guacamole appear to all be present. It's
possible that certain mirrors or repositories may take longer to update, so
you might just check back, or make sure you're using the official versions
noted above.

-Nick