Re: 3.4.0 SNAPSHOT breaks Log4j build

Am 07/07/16 um 01:23 schrieb Christian Schulte: > And then there is this MNG-NOT-YET-FILED-BY-ME - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional command

Re: 3.4.0 SNAPSHOT breaks Log4j build

Am 07/06/16 um 23:49 schrieb Christian Schulte: > > I'll take a closer look at the project tomorrow. Could be it's the > Aether bug I mentioned in that other mail which got reverted and makes > the project build again. That would mean the project really should not > build and error out but does no

Re: 3.4.0 SNAPSHOT breaks Log4j build

Am 07/06/16 um 23:40 schrieb Stuart McCulloch: > On Wednesday, 6 July 2016 at 22:17, Christian Schulte wrote: >> Am 07/06/16 um 23:08 schrieb Stuart McCulloch: >>> On Wednesday, 6 July 2016 at 21:53, Christian Schulte wrote: Am 07/06/16 um 22:21 schrieb Ralph Goers: > This is an interestin

Re: 3.4.0 SNAPSHOT breaks Log4j build

On Wednesday, 6 July 2016 at 22:17, Christian Schulte wrote: > Am 07/06/16 um 23:08 schrieb Stuart McCulloch: > > On Wednesday, 6 July 2016 at 21:53, Christian Schulte wrote: > > > Am 07/06/16 um 22:21 schrieb Ralph Goers: > > > > This is an interesting situation. The classes that use Jackson are a

Re: 3.4.0 SNAPSHOT breaks Log4j build

Am 07/06/16 um 23:08 schrieb Stuart McCulloch: > On Wednesday, 6 July 2016 at 21:53, Christian Schulte wrote: >> Am 07/06/16 um 22:21 schrieb Ralph Goers: >>> This is an interesting situation. The classes that use Jackson are all >>> considered optional in Log4j, so having optional set to true is

Re: 3.4.0 SNAPSHOT breaks Log4j build

On Wednesday, 6 July 2016 at 21:53, Christian Schulte wrote: > Am 07/06/16 um 22:21 schrieb Ralph Goers: > > This is an interesting situation. The classes that use Jackson are all > > considered optional in Log4j, so having optional set to true is indeed what > > is desired. However, we require t

Re: 3.4.0 SNAPSHOT breaks Log4j build

On Wed, Jul 6, 2016 at 12:47 PM, Karl Heinz Marbaise wrote: > Hi Gary, > > done so. > > See announce on dev / user list... The new version fixes the Log4j build. Thank you, Gary > > > Kind regards > Karl Heinz Marbaise > On 7/6/16 9:18 PM, Gary Gregory wrote: > >> On Wed, Jul 6, 2016 at 11:5

Re: 3.4.0 SNAPSHOT breaks Log4j build

On Thu, Jul 7, 2016 at 8:21 AM, Ralph Goers wrote: > With scope set to test I would expect that the non-test classes that need > them would fail to compile. Sadly this falls into one of my biggest pet-peeves with maven. IMHO neither compile or test scope should ever be transitive. Sadly, such a

Re: 3.4.0 SNAPSHOT breaks Log4j build

Am 07/06/16 um 22:21 schrieb Ralph Goers: > This is an interesting situation. The classes that use Jackson are all > considered optional in Log4j, so having optional set to true is indeed what > is desired. However, we require those dependencies to compile and to run the > unit tests. With scop

Re: 3.4.0 SNAPSHOT breaks Log4j build

This is an interesting situation. The classes that use Jackson are all considered optional in Log4j, so having optional set to true is indeed what is desired. However, we require those dependencies to compile and to run the unit tests. With scope set to test I would expect that the non-test cla

Re: 3.4.0 SNAPSHOT breaks Log4j build

Hi Gary, done so. See announce on dev / user list... Kind regards Karl Heinz Marbaise On 7/6/16 9:18 PM, Gary Gregory wrote: On Wed, Jul 6, 2016 at 11:52 AM, Karl Heinz Marbaise wrote: Hi Gary, On 7/6/16 8:47 PM, Gary Gregory wrote: On Wed, Jul 6, 2016 at 11:45 AM, Stuart McCulloch wrot

Re: 3.4.0 SNAPSHOT breaks Log4j build

BTW, https://issues.apache.org/jira/browse/MNG-5227 was about making the optional flag of a dependency manageable. Previously any optional flags in dependencyManagement sections were ignored, and it looks like the Log4j build relies on that historical behaviour. For example the jackson dependen

Re: 3.4.0 SNAPSHOT breaks Log4j build

On Wed, Jul 6, 2016 at 11:52 AM, Karl Heinz Marbaise wrote: > Hi Gary, > > On 7/6/16 8:47 PM, Gary Gregory wrote: > >> On Wed, Jul 6, 2016 at 11:45 AM, Stuart McCulloch >> wrote: >> >> That looks like the build (644ac9c40ad41bf61e3b099918af33b8eb950621) >>> before MNG-5227 and other breaking cha

Re: 3.4.0 SNAPSHOT breaks Log4j build

Hi Gary, On 7/6/16 8:47 PM, Gary Gregory wrote: On Wed, Jul 6, 2016 at 11:45 AM, Stuart McCulloch wrote: That looks like the build (644ac9c40ad41bf61e3b099918af33b8eb950621) before MNG-5227 and other breaking changes were rolled back I just tried with a maven distribution built from latest m

Re: 3.4.0 SNAPSHOT breaks Log4j build

Hi, thanks Stuart...that's right. Kind regards Karl Heinz Marbaise On 7/6/16 8:45 PM, Stuart McCulloch wrote: That looks like the build (644ac9c40ad41bf61e3b099918af33b8eb950621) before MNG-5227 and other breaking changes were rolled back I just tried with a maven distribution built from late

Re: 3.4.0 SNAPSHOT breaks Log4j build

On Wed, Jul 6, 2016 at 11:45 AM, Stuart McCulloch wrote: > That looks like the build (644ac9c40ad41bf61e3b099918af33b8eb950621) > before MNG-5227 and other breaking changes were rolled back > > I just tried with a maven distribution built from latest master > (227085283b6379038ec16f4cf9ad2e8869ce

Re: 3.4.0 SNAPSHOT breaks Log4j build

That looks like the build (644ac9c40ad41bf61e3b099918af33b8eb950621) before MNG-5227 and other breaking changes were rolled back I just tried with a maven distribution built from latest master (227085283b6379038ec16f4cf9ad2e8869cef694) and the Log4J build is passing On Wednesday, 6 July 2016

3.4.0 SNAPSHOT breaks Log4j build

A while back, a post made available a 3.4.0 SNAPSHOT build for testing. So I'm using it here and there. To replicate the 3.4.0-S failure (works fine on 3.3.9): Download https://repository.apache.org/content/repositories/orgapachelogging-1020/org/apache/logging/log4j/log4j-distribution/2.6.2/log4j