[
https://issues.apache.org/jira/browse/LOGGING-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623768#comment-17623768
]
Gary D. Gregory commented on LOGGING-183:
-----------------------------------------
Hi [~manf]
Thank you for helping.
It looks like the build is not fully up to date unfortunately.
I made some small changes to replace Clirr with JApiCmp but there are other
issues like 'mvn test' not running tests, which is weird.
Feel free to submit PRs on GitHub, it's the only way to get your changes
automatically tested without dumping that burden on another person.
If you want to see how GitHub runs our build, see maven.yml in the
.github/workflows folder
> Running Tests under Windows seems not to work properly.
> -------------------------------------------------------
>
> Key: LOGGING-183
> URL: https://issues.apache.org/jira/browse/LOGGING-183
> Project: Commons Logging
> Issue Type: Bug
> Affects Versions: Nightly Builds
> Environment: Windows 10 Enterprise
>
> Tested under
> Java Version 1.8 and 11 (Both Corretto)
> Reporter: Björn Heinrichs
> Priority: Minor
> Attachments: fix.patch, log-build.txt, log-test.txt, mvn.txt
>
>
> I've been trying to fork and contribute to commons logging to make it
> compatible with the JPMS System. A related Issue is
> https://issues.apache.org/jira/browse/COMMONSSITE-103
>
> I've hit a couple of roadblocks though, as by default cloning the repository,
> running mvn and then ant does not work.
>
> In particular javadoc throws this (seemingly) unrelated error, even though
> i've used both java 8 and Java 11 as the JDK.
> expected heading used: <H2>, compared to implicit preceding heading: <H3>
>
> Removing it from the default goal helped though. As i did not plan to add any
> javadocs anyway, i moved on to the next road block:
> Running Tests does not seem to work properly. I've attached two attempts to
> run ant test. using both build.xml and build-test.xml in both configurations.
> Unfortunately i will not be able to test under Java 2 for the forseeable
> future.
>
> In Github this does not seem to be an issue though. Searching through Jira,
> Google and the logging site did not reveal any helpful information in regards
> to building.
>
> I also noticed that the getlibs is not working in build-testing.xml a
> corresponding patch is attached.
>
> As far as i can see it, i've done everything as intended. I appologize if
> this is something more suited for the Mailing List, but to me it seems likely
> to be a bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
