I also did this several times in surefire. I think this strategy is better because it can be used to avoid the accumulation of issues in the first place.
It also allows us to be a little stricter on demanding test projects or similar, which is a great thing. As for the maven 1.x issues that's a completely different story, bulk closing sounds good to me ! Kristian 2014-11-25 9:33 GMT+01:00 tibor17 <tibo...@lycos.com>: > Michaelo, > > Due to we have a lot of open issues in SUREFIRE I have decided to ask the > Reporter for closing in JIRA. > So I have created a list of closable JIRA bugs and opened a discussion in > Maven mailing list last week. > This way the list was visible to all developers and everybody could argue to > not close them. > After one week we got a consensus, there wasn't any objection from > committers and PMC to not close ALL of them, and thus I closed them. Except > for one bug where I made an exception which will be categorized as an > improvement possibly in a new JIRA ticket. > > > > ----- > BR, tibor17 > -- > View this message in context: > http://maven.40175.n5.nabble.com/DISCUSS-Idle-bug-handling-approach-tp5815394p5815645.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
