Bug 1988896 - weird build error with xmvn-mojo:4.0.0:javadoc (default-cli) @ log4j
Summary: weird build error with xmvn-mojo:4.0.0:javadoc (default-cli) @ log4j
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xmvn
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-02 03:24 UTC by Sergio Basto
Modified: 2023-05-25 17:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 17:59:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
https://kojipkgs.fedoraproject.org//work/tasks/9723/73109723/build.log (87.65 KB, text/plain)
2021-08-02 03:24 UTC, Sergio Basto
no flags Details
https://kojipkgs.fedoraproject.org//work/tasks/9947/73109947/build.log (97.56 KB, text/plain)
2021-08-02 03:25 UTC, Sergio Basto
no flags Details

Description Sergio Basto 2021-08-02 03:24:10 UTC
Created attachment 1809992 [details]
https://kojipkgs.fedoraproject.org//work/tasks/9723/73109723/build.log

Description of problem:
I can build log4j on F34 but not on Rawhide 


xmvn-mojo:3.1.0:javadoc (default-cli) @ log4j --- in build.log

and 

xmvn-mojo:4.0.0:javadoc (default-cli) @ log4j ---
/builddir/build/BUILD/apache-log4j-2.14.1-src/log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/package-info.java:22: warning: a package-info.java file has already been seen for package org.apache.logging.slf4j
package org.apache.logging.slf4j;
                          ^
/builddir/build/BUILD/apache-log4j-2.14.1-src/log4j-to-slf4j/src/main/java/org/apache/logging/slf4j/SLF4JLogger.java:25: error: cannot find symbol
import org.slf4j.MarkerFactory;


take a look in the build.log

Comment 2 Mikolaj Izdebski 2021-08-02 10:31:13 UTC
Please provide a minimal reproducer of the issue, which will be submitted upstream as a test case.

Comment 3 Sergio Basto 2021-08-09 14:26:35 UTC
I don't know how provide a "minimal reproducer of the issue" sorry , but seems that  xmvn-mojo:4.0.0:install  is missing some jar(s) in CLASSPATH [1] because the same source had been compile some lines before ... 



[1]
[INFO] --- xmvn-mojo:4.0.0:install (default-cli) @ log4j ---
(...)

/builddir/build/BUILD/apache-log4j-2.14.1-src/log4j-to-slf4j/src/main/java/org/apache/logging/slf4j/SLF4JLogger.java:25: error: cannot find symbol
import org.slf4j.MarkerFactory;

Comment 4 Ben Cotton 2021-08-10 13:33:36 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 5 Mikolaj Izdebski 2021-11-15 14:52:27 UTC
I can reproduce XMvn javadoc failure in mock.
This seems to be related to JPMS.
Dependencies were added to module path, but are not modular - they should be on class path.

Comment 6 Ben Cotton 2022-02-08 21:27:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 7 Ben Cotton 2023-04-25 16:43:20 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Ludek Smid 2023-05-25 17:59:42 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.