You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Björn Heinrichs (Jira)" <ji...@apache.org> on 2022/10/25 10:32:00 UTC

[jira] [Created] (LOGGING-183) Running Tests under Windows seems not to work properly.

Björn Heinrichs created LOGGING-183:
---------------------------------------

             Summary: 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
         Attachments: fix.patch, log-build.txt, log-test.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)