All maven RPM builds no longer possible

[Graham Leggett]

Hi all,

I just tried to start from "probably simplest spec file possible” as described below
in order to package a maven artefact properly as an RPM:

https://docs.fedoraproject.org/en-US/java-packaging-howto/packaging_maven...

The build failed because the maven-javadoc-plugin package no longer exists, which is core
to building the javadoc package required by the spec. I have since been down a dependency
hell rabbithole to try and get something to work, with no luck to date.

Googling has revealed that java code has been in various states of brokenness for a while,
but we’re at a point where it isn’t possible to build any package using the maven macros
in an RPM spec file at all. Are people aware things are this broken?

Regards,
Graham
—

[Marián Konček]

Hi, thanks for pointing this out,
we have already been planning to update the howto guide soon™.

On 27. 6. 2022 11:02, Graham Leggett via devel wrote:
>  Hi all,
>
>  I just tried to start from "probably simplest spec file possible” as described below
> in order to package a maven artefact properly as an RPM:
>
>  https://docs.fedoraproject.org/en-US/java-packaging-howto/packaging_maven...
>
>  The build failed because the maven-javadoc-plugin package no longer exists, which is core
> to building the javadoc package required by the spec. I have since been down a dependency
> hell rabbithole to try and get something to work, with no luck to date.
>
>  Googling has revealed that java code has been in various states of brokenness for a
> while, but we’re at a point where it isn’t possible to build any package using the maven
> macros in an RPM spec file at all. Are people aware things are this broken?
>
>  Regards,
>  Graham
>  —
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-- 
Marián Konček

[Jerry James]

On Mon, Jun 27, 2022 at 3:04 AM Graham Leggett via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  I just tried to start from "probably simplest spec file
> possible” as described below in order to package a maven artefact properly as an RPM:
>
>  https://docs.fedoraproject.org/en-US/java-packaging-howto/packaging_maven...
>
>  The build failed because the maven-javadoc-plugin package no longer exists, which is core
> to building the javadoc package required by the spec. I have since been down a dependency
> hell rabbithole to try and get something to work, with no luck to date.
>
>  Googling has revealed that java code has been in various states of brokenness for a
> while, but we’re at a point where it isn’t possible to build any package using the maven
> macros in an RPM spec file at all. Are people aware things are this broken? 

My understanding is that xmvn has its own javadoc support, so
maven-javadoc-plugin isn't used even if it is installed.  Try adding
this to %prep:

%pom_remove_plugin -r :maven-javadoc-plugin

-- 
Jerry James
http://www.jamezone.org/

[Marián Konček]

That is correct, we removed maven-javadoc-plugin from Fedora since we 
had found a way to build maven without it.
xmvn has its own javadoc generator.

On 27. 6. 2022 21:46, Jerry James wrote:
>  On Mon, Jun 27, 2022 at 3:04 AM Graham Leggett via devel
>  <devel(a)lists.fedoraproject.org&gt; wrote:
> > I just tried to start from "probably simplest spec file possible” as described
> below in order to package a maven artefact properly as an RPM:
> >
> > https://docs.fedoraproject.org/en-US/java-packaging-howto/packaging_maven...
> >
> > The build failed because the maven-javadoc-plugin package no longer exists, which is
> core to building the javadoc package required by the spec. I have since been down a
> dependency hell rabbithole to try and get something to work, with no luck to date.
> >
> > Googling has revealed that java code has been in various states of brokenness for a
> while, but we’re at a point where it isn’t possible to build any package using the maven
> macros in an RPM spec file at all. Are people aware things are this broken?
>
>  My understanding is that xmvn has its own javadoc support, so
>  maven-javadoc-plugin isn't used even if it is installed.  Try adding
>  this to %prep:
>
>  %pom_remove_plugin -r :maven-javadoc-plugin
>  
-- 
Marián Konček