>-----Original Message----- >From: Jason van Zyl [mailto:ja...@sonatype.com] > >The nut of the problem is that if we had to support every optional behavior >for a particular subset of the community the code base would likely be >unmaintainable. No one here is going to implement anything toward what >you're specifically asking for because Maven was specifically designed not >to work for what you want. It probably would not be hard to do what you ask >for, but just because something is possible doesn't mean it's a good idea >to do it.
I understand that including every potential optional feature is not reasonable, and I'm not expecting that someone immediately go implement this for me just because I'm asking. However, I was hoping that it wouldn't get immediately dismissed without apparently considering the usefulness of it (especially since it seems like sometime similar is already done for snapshots), and I was hoping to perhaps even get a pointer of the sort of "we don't have the time to do it, but if you really want to work on this look at X". But, oh well, I guess I'll try to figure it out on my own. >Now what you're asking for here sounds particularly disastrous. If across >your organization a release does not actually mean a release in the Maven Again, you're missing my point. I AM NOT ASKING TO ALLOW RELEASES TO CHANGE! I just want a way to detect that something has become inconsistent when someone makes a mistake, and fail the build. If you think detecting problems is disastrous, well I don't really know what to say to that. eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org