I'm not much of a stakeholder in this but after following the discussion I'm getting curious if there's any hints to why this was introduced? Is there a VCS "blame" to do that links to a JIRA issue of some kind? This could uncover at least a few (reasonable or not) use cases for this (admitted, seemingly strange) micro-behavior.
Sander Verhagen [ [email protected] ] NOTICE: my e-mail address has changed. Please remove [email protected] now and start using [email protected] from now on. Please update your address book. Thank you! > -----Original Message----- > From: Benson Margulies [mailto:[email protected]] > Sent: Tuesday, July 14, 2015 10:05 > To: Maven Developers List > Subject: Re: Intend to release maven-assembly-plugin 3.0.0 > > > If it’s easy to make compatible why would you not do it? > > Really, this is the only interesting point of disagreement here. It's easy for > _me_ to make it compatible. It's hard for readers of the assembly descriptor > documentation to digest and understand yet another option that tweaks yet > another micro-behavior. One user out of 10,000 might be disturbed by the > arrival of a foo.filtered file. 9,999 users out of 10,000 will have to wade > through the extra doc. And some unknown number of people will run into > the (to me) bizarre current behavior. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected]
