You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2013/04/05 04:42:15 UTC
[jira] [Commented] (SOLR-4677) Improve Solr's use of spec version.
[ https://issues.apache.org/jira/browse/SOLR-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623272#comment-13623272 ]
Mark Miller commented on SOLR-4677:
-----------------------------------
I may have jumped the gun a bit here - I was remembering that I didn't pass the sys prop for spec version and then saw in the TODO that you needed to update it in common-build.xml (which I didn't do) and was looking at some build artifacts without the right spec but with the right impl - but looking at the official release manifest files, the versions look correct.
> Improve Solr's use of spec version.
> -----------------------------------
>
> Key: SOLR-4677
> URL: https://issues.apache.org/jira/browse/SOLR-4677
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Reporter: Mark Miller
> Fix For: 4.3, 5.0
>
>
> Solr 4.2.1 went out with an impl version of 4.2.1 and a spec version of 4.2.0.
> This is because you must update the spec version in common-build.xml while the impl is set by the version you pass as a sys prop when doing prepare-release.
> Do we need this spec version? Does it serve any purpose? I think we should either stop dealing with it or just set it the same way as the impl...or?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org