I can run with newer versions of Java than we require as a baseline. Thanks
for the info about what’s wrong!
On Sun, Jun 6, 2021 at 22:16 Ralph Goers wrote:
> In the log4j-core directory run
>
> mvn clean test -Dtest=RequiredValidatorTest
>
> Once the module has compiled you can do
>
> mvn sure
In the log4j-core directory run
mvn clean test -Dtest=RequiredValidatorTest
Once the module has compiled you can do
mvn surefire:test -Dtest-RequiredValidatorTest
The error happens because the initial compile cannot have a module-info and it
is finding the one from the previous build. See
h
I don't see any Mac build agents for anything at ASF besides GitHub
Actions. We do have Windows build agents, so I wonder if getting Mac
agents is something possible.
On Sun, 6 Jun 2021 at 18:43, Robert Middleton wrote:
>
> Thanks; I've been ignoring that while the release happens(there's
> proba
Thanks; I've been ignoring that while the release happens(there's
probably an easier way to do it on my side).
Somewhat related question: does the ASF Jenkins have any Mac builders?
It would be nice to make sure that the DMG gets generated on builds(I
suppose I could use github actions instead).
I can't even figure out how to execute individual tests from the
command line. Trying to run tests in log4j-core like so give an error:
$ mvn -pl :log4j-core test -Dtest=RequiredValidatorTest
...
[ERROR] COMPILATION ERROR :
[INFO] -
[ERRO
I've fixed this issue. The problem was that while the version in master
doesn't have a -SNAPSHOT, it can't be deployed to the snapshots repository
(duh). I've updated the pipeline to check the maven project version for
this before attempting to run a deploy step to publish snapshot builds. As
a bon
Nits (not blockers, but useful to fix for next release):
* Source archive should be created by adding the option
--prefix=apache-chainsaw-2.1.0/ so that the archives are inside a
directory. As is, they don't have a containing directory which can be
unexpected.
+1
Signatures good, built and tested
