felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3392) Generated Manifest ignores properties set by other plugins
Date Wed, 09 Apr 2014 11:28:15 GMT

    [ https://issues.apache.org/jira/browse/FELIX-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964039#comment-13964039

Joerg Schaible commented on FELIX-3392:

Here we go again. The interpolation does still not work for version 2.4.0 of the plugin. Goals
'bundle' and 'manifest' are both affected. The workaround mentioned above works only for the
'manifest' goal, there is no solution for the 'bundle' goal. 

Note, that the interpolation already works when building with Maven 2.2.1, it fails with Maven

@Andreas: It should not be a problem to update the Maven Core dependency, the plugin can still
run on Maven 2.2.1.

> 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
>             Fix For: maven-bundle-plugin-future
>         Attachments: patchPropertyResolution.patch, 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 was sent by Atlassian JIRA

View raw message