[
https://issues.apache.org/jira/browse/FELIX-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604031#comment-13604031
]
Joerg Schaible commented on FELIX-3392:
---------------------------------------
I normally overwrite Specification-Version in the jar configuration with values
from the build-helper plugin:
{noformat}
<configuration>
<archive>
<manifest>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
</manifest>
<manifestEntries>
<Specification-Version>${parsedVersion.majorVersion}.${parsedVersion.minorVersion}</Specification-Version>
</manifestEntries>
</archive>
</configuration>
{noformat}
However, adding this to the bundle-plugin's configuration does not work either,
the value is still not interpolated:
{noformat}
<configuration>
<instructions>
<Specification-Version>${parsedVersion.majorVersion}.${parsedVersion.minorVersion}</Specification-Version>
</instructions>
</configuration>
{noformat}
> Generated Manifest ignores properties set by other plugins
> ----------------------------------------------------------
>
> Key: FELIX-3392
> URL: https://issues.apache.org/jira/browse/FELIX-3392
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Paul Gier
> Attachments: test-bundle-properties.zip
>
>
> My usecase is that I want to generate a build timestamp for my build using
> the buildnumber-maven-plugin, then add this timestamp to my jar manifest.
> Using the maven jar plugin, this works as expected and the property is set.
> Using the bundle plugin, the property is not resolved and I get something
> like "${timestamp}" in my manifest. It appears that the bundle plugin does
> not resolve properties that were set earlier in the build.
--
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
