You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Kaloyan Enimanev (JIRA)" <ji...@apache.org> on 2009/03/18 13:55:50 UTC
[jira] Created: (FELIX-989) Ignore emply "_exportcontents"
instructions
Ignore emply "_exportcontents" instructions
-------------------------------------------
Key: FELIX-989
URL: https://issues.apache.org/jira/browse/FELIX-989
Project: Felix
Issue Type: Improvement
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-2.0.0, maven-bundle-plugin-1.4.3
Reporter: Kaloyan Enimanev
There is a quite central parent POM in our build system, that incorporates all {{maven-bundle-plugin}} configuration . Basically, in this parent POM we specify all the possible configurations with some default values and leave the extender the possibility to override those via a set of POM properties.
e.g. parent POM snippet :
{code:xml}
...
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
...
<Import-Package>${osgi.import.package}</Import-Package>
..
{code}
can be used in the child POM as
{code:xml}
...
<properties>
<osgi.import.package>com.foo.bar;version="1.0.0", *</osgi.import.package>
</properties>
..
{code}
That all worked fine, until yesterday when one of our developers wanted to use the "_exportcontents" instruction, so we have put the following snippet in our parent pom :
{code:xml}
....
<_exportcontents>${osgi._exportcontents}</_exportcontents>
...
{code}
Since the property {{osgi._exportcontents}} is not set, the above line is equal to
{code:xml}
....
<_exportcontents</_exportcontents>
...
{code}
Sadly, that broke the generation of "Export-Package" clauses in all the modules declaring "Embed-Dependency" of some form. The reason, seems to be hiding somewhere behind the empty-valued "_exportcontents" instruction.
So, would it be possible for the {{maven-bundle-plugin}} (or the BND tool) to ignore empty "_exportcontents" instructions ?
Many thanks in advance,
Kaloyan
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-989) Please ignore this entry
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch closed FELIX-989.
----------------------------------
Resolution: Incomplete
Closing as requested.
> Please ignore this entry
> -------------------------
>
> Key: FELIX-989
> URL: https://issues.apache.org/jira/browse/FELIX-989
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.3, maven-bundle-plugin-2.0.0
> Reporter: Kaloyan Enimanev
>
> Please ignore this entry
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-989) Please ignore this entry
Posted by "Kaloyan Enimanev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kaloyan Enimanev updated FELIX-989:
-----------------------------------
Description: Please ignore this entry (was: There is a quite central parent POM in our build system, that incorporates all {{maven-bundle-plugin}} configuration . Basically, in this parent POM we specify all the possible configurations with some default values and leave the extender the possibility to override those via a set of POM properties.
e.g. parent POM snippet :
{code:xml}
...
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
...
<Import-Package>${osgi.import.package}</Import-Package>
..
{code}
can be used in the child POM as
{code:xml}
...
<properties>
<osgi.import.package>com.foo.bar;version="1.0.0", *</osgi.import.package>
</properties>
..
{code}
That all worked fine, until yesterday when one of our developers wanted to use the "_exportcontents" instruction, so we have put the following snippet in our parent pom :
{code:xml}
....
<_exportcontents>${osgi._exportcontents}</_exportcontents>
...
{code}
Since the property {{osgi._exportcontents}} is not set, the above line is equal to
{code:xml}
....
<_exportcontents</_exportcontents>
...
{code}
Sadly, that broke the generation of "Export-Package" clauses in all the modules declaring "Embed-Dependency" of some form. The reason, seems to be hiding somewhere behind the empty-valued "_exportcontents" instruction.
So, would it be possible for the {{maven-bundle-plugin}} (or the BND tool) to ignore empty "_exportcontents" instructions ?
Many thanks in advance,
Kaloyan)
Summary: Please ignore this entry (was: Ignore emply "_exportcontents" instructions)
> Please ignore this entry
> -------------------------
>
> Key: FELIX-989
> URL: https://issues.apache.org/jira/browse/FELIX-989
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.3, maven-bundle-plugin-2.0.0
> Reporter: Kaloyan Enimanev
>
> Please ignore this entry
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.