[jira] Commented: (SOLR-907) Include access to Lucene Source with 1.4 release

["Hoss Man (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656264#action_12656264 ] 

Hoss Man commented on SOLR-907:
-------------------------------

anytime lucene jars are upgraded, the CHANGES.txt file lists the version -- if it's not an already released version, then the CHANGES.txt includes the subversion revision, ala...

{noformat}
 9. SOLR-819: Upgraded to Lucene 2.9-dev (r724059) to get access to Arabic public constructors (gsingers)
{noformat}

This information is also accessible without access to CHANGES.txt by inspecting the lucene-*.jar manifest files, and is exposed in the Solr admin console on /admin/registry.jsp ...

{noformat}
Lucene Implementation Version: 2.9-dev 724059 - 2008-12-06 20:08:54
{noformat}

Once you have the subversion revision number, getting the source is trivial...

{noformat}
svn co https://svn.apache.org/repos/asf/lucene/java/trunk@724059 lucene-r724059
{noformat}


Is there really anything else we need to do?



> Include access to Lucene Source with 1.4 release
> ------------------------------------------------
>
>                 Key: SOLR-907
>                 URL: https://issues.apache.org/jira/browse/SOLR-907
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 1.4
>            Reporter: Todd Feak
>            Priority: Minor
>
> If Solr 1.4 release with a non-release version of Lucene, please include some way to access the exact source code for the Lucene libraries that are included with Solr. This could take the form of Maven2 Repo source files, a subversion location and revision number, including the source with the distribution, etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.