[
https://issues.apache.org/jira/browse/SOLR-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741176#comment-13741176
]
Steve Rowe commented on SOLR-5159:
----------------------------------
Hi Artem, I've run and compared with and without your patch on trunk with
Maven3, looks good so far: ${svn.revision} and ${now.timestamp} and one other
timestazmp that weren't being interpolated now are. I want to verify Maven2
locally, and I also want to compare all manifest entries with the Ant-produced
ones - the solr entries were changed recently, and I want to keep them in sync.
Once these issues are settled, I'll commit.
> Manifest includes non-parsed maven variables
> --------------------------------------------
>
> Key: SOLR-5159
> URL: https://issues.apache.org/jira/browse/SOLR-5159
> Project: Solr
> Issue Type: Bug
> Components: Build
> Affects Versions: 4.4, 4.5, 5.0
> Environment: Apache Maven 3.0.5
> Reporter: Artem Karpenko
> Assignee: Steve Rowe
> Priority: Minor
> Labels: maven-bundle-plugin, maven3,
> Attachments: SOLR-5159.patch
>
>
> When building Lucene/Solr with Apache Maven 3, all MANIFEST.MF files included
> into JAR artifacts contain non-parsed POM variables: namely, there are
> entries like
> Specification-Version: 5.0.0.$\{now.version}
> In the end, Solr displays these values on admin page in "Versions" section.
> This is caused by unresolved bug in maven-bundle-plugin (FELIX-3392).
--
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: [email protected]
For additional commands, e-mail: [email protected]
