[jira] Updated: (FELIX-846) Enhance the iPojo maven plugin to take metadata from pom.

["Todor Boev (JIRA)" <ji...@apache.org>]

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

Todor Boev updated FELIX-846:
-----------------------------

    Attachment: pom.xml

This is how I imagine it working.  I hope the maven pom schema allows me to pass arbitrary XML to the plugins. in the <configuration> tag. Than I can use namsepaces to instruct the XML parser to validate the part of the pom that the plugin consumes by the iPojo schema. Also I'm not sure if I have to pass more than one xml when I use composites and if this can also be accommodated by the maven pom schema.

> Enhance the iPojo maven plugin to take metadata from pom.
> ---------------------------------------------------------
>
>                 Key: FELIX-846
>                 URL: https://issues.apache.org/jira/browse/FELIX-846
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-1.0.0
>         Environment: Runtime: OSGi 4.1 + iPojo
> Build: Maven
>            Reporter: Todor Boev
>            Priority: Minor
>             Fix For: iPOJO-1.2.0
>
>         Attachments: pom.xml
>
>
> It would be nice if the iPojo Maven plugin could consume xml metadata directly from my pom.xml rather than look for a separate metadata file. This makes sense because the metadata.xml is used only at build time and does not progress to become a resource bundle. So it's not realy a resource - it is more part of the build scripts. And as such it's best if it can be integrated into the ultimate build script - the pom.
> Also this will match the way metadata is specified to the BND maven plugin. So we would have all data related to the construction of an iPojo bundle laid out in the pom.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.