> > > > > > Many maven plugins get fixes and features but stay in SNAPSHOT for months > > before some of us propose a new release. I think the main reason is the > why? i mean why change it if you are not going to release it... i would > figure > that the trunk would nearly always never have changes...
Before I was accepted as a maven committer I never used SNAPSHOTs plugin to build my project. Now, most of my projects use SNAPSHOTS (timestamps) because some desired feature has been fixed either by applying a patch or by making myself the required change. Calling for a vote on a plugin I'm not familiar with and with no idea of the roadmap is not easy. IHMO this is a side effect of SNAPSHOTs : if you're confident with the codebase and how to change it, you don't really require a release... some more "automatic" release process would encourage them. > > > -- > Michael McCallum > Enterprise Engineer > mailto:[EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
