Lucene version ranges

[Mark Diggory <md...@MIT.EDU>]

I was playing with using version ranges to identify which revisions  
are compatible with our release and discovered that the metadata in  
the repository isn't accurate to the actual releases:

See

http://repo2.maven.org/maven2/org/apache/lucene/lucene-core/
http://repo2.maven.org/maven2/org/apache/lucene/lucene-core/maven- 
metadata.xml

Is this something that happens allot, shouldn't there be a more  
reliable way to determine ranges? I suspect it would be relatively  
simple to write something that iterates over the repository and  
corrects metadata file based on repository directory contents?

-Mark


~~~~~~~~~~~~~
Mark R. Diggory - DSpace Systems Manager
MIT Libraries, Systems and Technology Services
Massachusetts Institute of Technology

Re: Lucene version ranges

[Carlos Sanchez <ca...@apache.org>]

you are welcome to do that ;)

On 10/30/07, Mark Diggory <md...@mit.edu> wrote:
> I was playing with using version ranges to identify which revisions
> are compatible with our release and discovered that the metadata in
> the repository isn't accurate to the actual releases:
>
> See
>
> http://repo2.maven.org/maven2/org/apache/lucene/lucene-core/
> http://repo2.maven.org/maven2/org/apache/lucene/lucene-core/maven-
> metadata.xml
>
> Is this something that happens allot, shouldn't there be a more
> reliable way to determine ranges? I suspect it would be relatively
> simple to write something that iterates over the repository and
> corrects metadata file based on repository directory contents?
>
> -Mark
>
>
> ~~~~~~~~~~~~~
> Mark R. Diggory - DSpace Systems Manager
> MIT Libraries, Systems and Technology Services
> Massachusetts Institute of Technology
>
>
>
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride