+1
>From the src zip: ASC, SHA1 OK.
Maven Apache RAT check ... OK.
mvn clean install ... OK
mvn clirr:check -pl log4j-api ... OK
mvn clirr:check -pl log4j-1.2-api ... OK
Using:
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T12:49:05-07:00)
Maven home: C:\Java\apache
While it now shows up under the 'logging' category, I still can't see
the project at all unless I'm logged in. I'm assuming that's not
intentional.
-Robert Middleton
On Sun, Mar 11, 2018 at 7:05 PM, Matt Sicker wrote:
> This was fixed yesterday by the way. I still need to gather a list of users
FYI
I am traveling with family. I’ll have sporadic access to web and email.
I’ll try to review the release though.
Remko
Matt is right on all counts. The tests can be removed since picocli is tested
in its own project, and when we split the modules it can be moved out of core
into the tools module.
> On Mar 12, 2018, at 8:03, Matt Sicker wrote:
>
> Is that test copied from picocli? If so, I’m not sure what th
Thanks!
On 11 March 2018 at 17:33, wrote:
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/release-2.x 1d70d3197 -> 046a5cfaf
>
>
> Remove dead link
>
>
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Commit: http://git-wip-us.apache.org/repos/asf/logging-l
This is a vote to release Log4j 2.11.0, the next version of the Log4j 2 project.
Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...
The vote will remain open for 72 hours (or more if required). All votes are
welco
This was fixed yesterday by the way. I still need to gather a list of users
to add as project admins, though.
On Sat, Mar 10, 2018 at 11:08, Matt Sicker wrote:
> I can’t seem to change any settings. I’ll file an issue with infra.
>
> On Sat, Mar 10, 2018 at 09:44, Robert Middleton
> wrote:
>
>>
Is that test copied from picocli? If so, I’m not sure what the value is
there anyways since it’s already tested in its own project. As for why it’s
included, it won’t need to be once all the command line tools are separated
(this includes custom loggers and levels besides just log receivers and
wha
It looks like there's a bad redirect when vising the website from the
main homepage of https://logging.apache.org/. When I click on it, I
go to https://logging.apache.org/log4cxx which then goes to
https://logging.apache.org/log4cxx/latest_stable/latest_stable/, which
gives me a 404.
I'm able to
I’m not sure what you are thinking.
Ralph
> On Mar 11, 2018, at 12:10 PM, Gary Gregory wrote:
>
> Could it be a Maven toolchain that is misconfigured?
>
> Gary
>
> On Sun, Mar 11, 2018, 13:01 Ralph Goers wrote:
>
>> I should also add that this test is not failing on the MacBook Pro that I
>
Could it be a Maven toolchain that is misconfigured?
Gary
On Sun, Mar 11, 2018, 13:01 Ralph Goers wrote:
> I should also add that this test is not failing on the MacBook Pro that I
> use to perform releases. It is failing on a MacBook Pro that is about 4
> years newer. But both are running the
I should also add that this test is not failing on the MacBook Pro that I use
to perform releases. It is failing on a MacBook Pro that is about 4 years
newer. But both are running the latest version of High Sierra and should be
configured similarly. The only major difference is that I use Java 8
I can’t answer that except to say that I don’t think that will change for
2.11.0. I have no idea why we have anything to do with the command line in
Log4j.
Ralph
> On Mar 11, 2018, at 11:42 AM, Gary Gregory wrote:
>
> Do we still even need Picocli in the core? (This whole time I thought it
>
Do we still even need Picocli in the core? (This whole time I thought it
was "picoli")
Gary
On Sun, Mar 11, 2018, 12:06 Ralph Goers wrote:
> I do not know why but now on one of my MacBooks the 2.x build is failing
> with
>
> [INFO] Running org.apache.logging.log4j.core.tools.picocli.CommandLin
I do not know why but now on one of my MacBooks the 2.x build is failing with
[INFO] Running org.apache.logging.log4j.core.tools.picocli.CommandLineTest
[ERROR] Tests run: 199, Failures: 1, Errors: 0, Skipped: 4, Time elapsed: 0.802
s <<< FAILURE! - in org.apache.logging.log4j.core.tools.picocli.
Thanks for reporting this. I’ll take a look.
Remko
> On Mar 11, 2018, at 17:32, Atle Tokle wrote:
>
> I tried to build from GIT bash on windows 10, and first test that failed
> was
>
> testSynopsisOrderCorrectWhenParametersDeclaredOutOfOrder in
>
> org.apache.logging.log4j.core.tools.picocl
I tried to build from GIT bash on windows 10, and first test that failed
was
testSynopsisOrderCorrectWhenParametersDeclaredOutOfOrder in
org.apache.logging.log4j.core.tools.picocli.
CommandLineHelpTest:2008
It seems like the expected result
format(" %n") on line 2014 always assumes
that no A
17 matches
Mail list logo
