On 31/03/2007, at 12:09 AM, Jason van Zyl wrote:
This would not be a concept change in Maven (at least, yet - it
could be something to consider in the versioning in future): it's
simply two types of release repositories. The stable one would be
included in Maven by default, the unstable/pre-release one would
not. You'd have to add the repository to your project.
-1
Ok - having reflected on this, I still believe in the concept but
agree that it won't be practical without first making it easier to
declare your repositories without all the extra work that is required
now.
It's already complicated enough and I think we should, in fact, go
the other way and put a default SNAPSHOT repository in the process
by default so that thousands of people don't have diddle POMs all
the time.
No real objections here.
So in summary, more default repositories definitions not more types
of repositories.
I'm not sure that's a fair summary. Specifying your repositories
globally needs to be simpler, trying to shove everything (especially
snapshots) through central is impractical.
Put a default snapshot repository on central, find some reasonable
eviction policy and make day-to-day use easier. Also make the
specification of the plugin version to bring that into common
pattern that is the same for dependencies.
+1 on both easier day to day use and locking down versions.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
