felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FELIX-1439) maven-bundle-plugin resource filtering does not substitute project.organization.*
Date Wed, 02 Sep 2009 22:50:32 GMT

     [ https://issues.apache.org/jira/browse/FELIX-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stuart McCulloch resolved FELIX-1439.
-------------------------------------

    Resolution: Fixed

Applied modified version of the patch in trunk (r810723)

> 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
>         Attachments: FELIX-1439.patch
>
>
> 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.


Mime
View raw message