Hi, we like to open-source approach and we don't want to put pressure on the maven2 developers to fix all the issues in a short time. Open source is something you get from free when some voluteers have free time to develop planned functionalities.
What we expect is some management work done by Apache maven2 committee in release/tasks planning. So that the users of maven2 can rely (and believe) the project is under control, consistent and well coordinated. I'm not saying this is not happening in the maven2 project... but we would expect some more feedbacks about how is the project moving, especially because of how is maven2 done with a lot of different projects (plugins) depending on it and waiting for some bugs to be fixed. (an example can be also the m2plugin for eclipse). Another smart approach could be to do more versions also if only few JIRA tasks have been closed. Is it very difficult to do a maven2 version on a monthly base (for example)? I know we all should work a little bit for maven2 in order to see it grow faster and better, I will try to do it during my private time for the future... for now I'm "just" trying to let the company I work for and the development team believe m2 is a good tool for handling our release management process... and I think this is also useful for the m2 project itself. keep on doing the great job you started.. thanks, Federico Brett Porter wrote: > > On 18/09/06, jerome lacoste <[EMAIL PROTECTED]> wrote: >> I completely agree. In fact building plugins now requires maven 2.0.5 >> and this made me put a pause on working on mojo plugins: I want to use >> a stable build with known shortcomings, and not depend on a moving >> development platform. > > This isn't true. > > If you build all the plugins from trunk, then yes, 2.0.5 is required, > as the plugin plugin has adopted some new features. It's likely to be > reverted to avoid the headaches, but it is a separate issue. It was > exacerbated by that version being set to the default for all maven > plugins. That is being rolled back in many places already and is a > simple parent version change. > > However, you can keep using the released version of the plugin plugin > to build your plugins by sticking to non snapshot repositories. > > - Brett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/2.0.5-release--tf2271527.html#a6362059 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
