Heya Ryan... For me the big problem with adding http://people.apache.org/~mikemccand/staging-area/rc3_lucene2.9.1/maven/<http://people.apache.org/%7Emikemccand/staging-area/rc3_lucene2.9.1/maven/>to my build config is that the artifact names of the interim release are the same as the final objects will be.. thus once they are copied to a local repo maven won't bother to go looking for more recent versions, even if you blow away that temporary repo. Would it be possible to publish tagged rc-N releases to a public and more permanent repository where people can reference them and upgrade to the final release when it's available.
Just a thought, cheers for all your hard work. Ian. 2009/11/2 Ryan McKinley <ryan...@gmail.com> > > On Nov 2, 2009, at 8:29 AM, Grant Ingersoll wrote: > > >> On Nov 2, 2009, at 12:12 AM, Licinio Fernández Maurelo wrote: >> >> Hi folks, >>> >>> as we are using an snapshot dependecy to solr1.4, today we are getting >>> problems when maven try to download lucene 2.9.1 (there isn't a any 2.9.1 >>> there). >>> >>> Which repository can i use to download it? >>> >> >> They won't be there until 2.9.1 is officially released. We are trying to >> speed up the Solr release by piggybacking on the Lucene release, but this >> little bit is the one downside. >> > > Until then, you can add a repo to: > > http://people.apache.org/~mikemccand/staging-area/rc3_lucene2.9.1/maven/<http://people.apache.org/%7Emikemccand/staging-area/rc3_lucene2.9.1/maven/> > > >
