Hej Ceki,
Nils is right, all the elements of BOM are ignored but the depMgt.
So what you "pollute" are those extra handfuls of bytes that consumers
download, only to toss them away.
So this is not a problem IMHO.
Thanks
T
On Tue, Jan 9, 2024 at 12:34 AM Nils Breunese wrote:
> or elements ar
or elements are not imported when a project imports a BOM with
import, only is imported.
Other elements only get inherited when a project uses another project as a
parent.
> Op 8 jan 2024, om 20:57 heeft Ceki Gulcu het volgende
> geschreven:
>
> Hi Tamás,
>
> Thank you for your comments.
Hi Tamás,
Thank you for your comments.
My question is more regarding the need to place a javadoc
element in the BOM file, i.e top level pom.xml, instead of parent/pom.xml.
Once the javadoc related element is in the BOM file, it works fine.
However, given the BOM file is intended to be importe
Hej Ceki,
I also experience javadoc misbehaviour when JPMS/jigsaw is involved, and _I
think_ it boils down when it tries to be "smart" when it comes to JPMS...
See master of maven-resolver, as it was suffering with similar issues, and
this change:
https://github.com/apache/maven-resolver/commit/ba
Hello all,
Given the javadoc generation is an important part of software projects,
maybe someone would care to comment whether the behavior described below
is expected or not?
In the meantime, happy new year to all,
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponso
