Re: [jira] [Reopened] (MNG-5227) The 'optional' flag of a dependency should be manageable.

2016-01-29 Thread Christian Schulte
MNG-5959 - Different wording, same use case. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [jira] [Reopened] (MNG-5227) The 'optional' flag of a dependency should be manageable.

2016-01-29 Thread Christian Schulte
Am 01/29/16 um 11:50 schrieb Robert Scholte: Hi, What interested me is that is seems to be the intention to NOT manage the optional flag.[1] It's one of those issues flagged a regression in Maven 3 which hasn't been. Maven 2 just did not have support for it. It got removed for Maven 3.0 in 20

Re: [jira] [Reopened] (MNG-5227) The 'optional' flag of a dependency should be manageable.

2016-01-29 Thread Jason van Zyl
I believe what Christian is asserting is that if you so choose to manage the optional flag because that’s how you use a particular dependency within your multi-module application build that it should be retained. It may very well be that a set of modules need an optional dependency to compile bu

Re: [jira] [Reopened] (MNG-5227) The 'optional' flag of a dependency should be manageable.

2016-01-29 Thread Robert Scholte
Hi, What interested me is that is seems to be the intention to NOT manage the optional flag.[1] Why would you set the optional flag when using dependency management? this just means, that if you want to use this dependency, you explicitly need to set the optional to false? That doesn't feel