Hi, I notice some great work going into m1 plugins. Thanks to everyone for the work going on there and for keeping them going. In addition, there are new jira issues coming in, sometimes with patches.
As we progress towards a final release of Maven 2.0 and look to maintaining both in parallel in the future, I'm looking for thoughts from people on how we can ensure features and bugfixes in the m1 plugins don't get overlooked for m2. The ideal solution is for the m1 plugin to be rewritten as a wrapper on the m2 version, but this might be too much work in some cases, especially if there is heavy project interaction. It's also an issue if we've deliberately decided to remove a feature from the m2 version. That said, are there any plugins where people think this would make sense to try? What fallbacks do we have otherwise? Some options: - Cease new features on the m1 plugins to reduce the amount of work. This is probably too harsh, esp. if m1 users contribute patches - open an issue on the m2 plugin when the m1 version is closed, linking to the original - others? Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
