Jason van Zyl said: > > On 24 Sep 07, at 9:23 AM 24 Sep 07, Mark Hobson wrote: > >> Okay, but I do think a feature branch is the best for prototyping new >> features - it stops blocking the developer and doesn't cause >> unnecessary problems for others. Do we really need to merge it into >> 2.0.x? 2.0.8 is due out soon which means users can start using this >> prototype which will lock us into supporting this functionality in >> future. >> > > I don't think Ralph was planning on trying to merge this as there are > changes in the separated maven-artifact. I don't think this can go in > 2.0.8. Ralph, just verifying but you're not intending to put this in > 2.0.8 are you? >
If there were no objections then ideally yes as the folks I did this for really only want to use a formal release of Maven. That is why I posed the question first last week. Since I only got feedback from Jason I (probably incorrectly) assumed no one else objected. To be honest, this is one aspect of the Maven community that I've been unclear on since participating here. I've seen folks do stuff in whiteboards and branches but it has never been clear to me when that is appropriate vs. discussing it on the list and committing. For example, I tried to go back in the dev list and search for where the decision to drop properties from individual dependencies was made in Maven 2 and I just couldn't find it. Maybe my search wasn't specific enough. If you would prefer this to be on a branch so others can try it I'd be happy to do that but I doubt we will be able to use it until it is in a release. If that is what you prefer then I can revert this tonight. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
