[
https://issues.apache.org/jira/browse/FELIX-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738128#action_12738128
]
Tim Moore commented on FELIX-1439:
----------------------------------
There's a simple work around: in a project's properties section, explicitly
redefine these properties:
<properties>
<project.organization.name>${project.organization.name}</project.organization.name>
<project.organization.url>${project.organization.url}</project.organization.url>
</properties>
> maven-bundle-plugin resource filtering does not substitute
> project.organization.*
> ---------------------------------------------------------------------------------
>
> Key: FELIX-1439
> URL: https://issues.apache.org/jira/browse/FELIX-1439
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.0.0
> Reporter: Tim Moore
>
> We have an XML file in our project's resource directory that contains various
> Maven properties that are substituted by the maven-bundle-plugin at build
> time. Most of the properties work (for example, ${pom.name},
> ${pom.description}, ${pom.version}) but ${pom.organization.name} and
> ${pom.organization.url} do not. Changing them to ${project.organization.name}
> and ${project.organization.url} did not help.
> These properties are a little unusual in that they refer to properties of a
> nested object within the project model, kind of like how project.build works,
> so they probably have to be special-cased the same way.
> I notice that when I run mvn with -X, I see this in the BND Instructions:
> [DEBUG] pom.organization: null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
