You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Michael Taeschner (JIRA)" <ji...@apache.org> on 2012/08/15 15:56:37 UTC
[jira] [Created] (FELIX-3630) Packages exported by bundle are
(re)-imported with incorrect version
Michael Taeschner created FELIX-3630:
----------------------------------------
Summary: Packages exported by bundle are (re)-imported with incorrect version
Key: FELIX-3630
URL: https://issues.apache.org/jira/browse/FELIX-3630
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-2.3.7
Reporter: Michael Taeschner
Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
Resulting Manifest:
{noformat}
Manifest-Version: 1.0
Bnd-LastModified: 1345038828923
Build-Jdk: 1.6.0_31
Built-By: u056801
Bundle-Description: maven-bundle-plugin Import Package Test
Bundle-ManifestVersion: 2
Bundle-Name: Imports Test
Bundle-SymbolicName: com.mitaes.imports
Bundle-Version: 1.2.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: com.mitaes.service;version="1.0.0"
Import-Package: com.mitaes.service;version="[1.2,2)"
Tool: Bnd-1.50.0
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FELIX-3630) Packages exported by bundle
are (re)-imported with incorrect version
Posted by "Michael Taeschner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435121#comment-13435121 ]
Michael Taeschner edited comment on FELIX-3630 at 8/16/12 12:57 AM:
--------------------------------------------------------------------
Attached sample project "importTest.zip"
was (Author: mitaes):
Attached sample project [^importTest.zip]
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
> Attachments: importTest.zip
>
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3630) Packages exported by bundle are
(re)-imported with incorrect version
Posted by "Michael Taeschner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Taeschner updated FELIX-3630:
-------------------------------------
Description:
Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
Resulting Manifest:
Manifest-Version: 1.0
Bnd-LastModified: 1345038828923
Build-Jdk: 1.6.0_31
Built-By: u056801
Bundle-Description: maven-bundle-plugin Import Package Test
Bundle-ManifestVersion: 2
Bundle-Name: Imports Test
Bundle-SymbolicName: com.mitaes.imports
Bundle-Version: 1.2.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: com.mitaes.service;version="1.0.0"
Import-Package: com.mitaes.service;version="[1.2,2)"
Tool: Bnd-1.50.0
was:
Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
Resulting Manifest:
{noformat}
Manifest-Version: 1.0
Bnd-LastModified: 1345038828923
Build-Jdk: 1.6.0_31
Built-By: u056801
Bundle-Description: maven-bundle-plugin Import Package Test
Bundle-ManifestVersion: 2
Bundle-Name: Imports Test
Bundle-SymbolicName: com.mitaes.imports
Bundle-Version: 1.2.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: com.mitaes.service;version="1.0.0"
Import-Package: com.mitaes.service;version="[1.2,2)"
Tool: Bnd-1.50.0
{noformat}
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3630) Packages exported by bundle are
(re)-imported with incorrect version
Posted by "Michael Taeschner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435136#comment-13435136 ]
Michael Taeschner commented on FELIX-3630:
------------------------------------------
Current workaround is to configure the version range for the package to be imported inside plugin configuration or linked bnd file.
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
> Attachments: importTest.zip
>
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3630) Packages exported by bundle are
(re)-imported with incorrect version
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435161#comment-13435161 ]
Stuart McCulloch commented on FELIX-3630:
-----------------------------------------
The attached pom.xml has an additional execution of bundle:manifest which is tied to the 'process-classes' phase:
{code}
<executions>
<execution>
<id>bundle-manifest</id>
<phase>process-classes</phase>
<goals>
<goal>manifest</goal>
</goals>
</execution>
</executions>
{code}
This ends up creating a first-pass manifest under target/classes/META-INF/MANIFEST.MF which exports the package using the bundle version. The version appears to be added to the export by bnd, it isn't in the Export-Package instruction generated by the bundle plugin during this execution (see mvn clean process-classes -X). This is likely down to the slightly different approach taken by bundle:manifest (which analyzes an existing jar/directory using instructions as a guide) and bundle:bundle (which builds a fresh bundle based on the classpath and a set of instructions) - it looks like bnd's Builder takes package-level packageinfo versions into account, but bnd's Analyzer doesn't.
After this extra execution has completed the bundle packaging lifecycle kicks in and builds the bundle - once again mvn -X suggests that the bundle plugin doesn't add any specific versions to the default instructions, but the manifest we get back from bnd has the import range based on the interim manifest generated previously (with exports versioned using the bundle-version). However, the export now uses the packageinfo version.
I've tested this project with the latest maven-bundle-plugin 2.4.0-SNAPSHOT and the incorrect versions no longer appear, so it looks like this has been fixed in trunk.
As a workaround for 2.3.7 remove the above explicit execution of bundle:manifest (it is not required when you use bundle packaging) and you should get the expected results.
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
> Attachments: importTest.zip
>
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3630) Packages exported by bundle are
(re)-imported with incorrect version
Posted by "Michael Taeschner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Taeschner updated FELIX-3630:
-------------------------------------
Attachment: importTest.zip
Attached sample project [^importTest.zip]
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
> Attachments: importTest.zip
>
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FELIX-3630) Packages exported by bundle
are (re)-imported with incorrect version
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435161#comment-13435161 ]
Stuart McCulloch edited comment on FELIX-3630 at 8/16/12 1:34 AM:
------------------------------------------------------------------
The attached pom.xml has an additional execution of bundle:manifest which is tied to the 'process-classes' phase:
<executions>
<execution>
<id>bundle-manifest</id>
<phase>process-classes</phase>
<goals>
<goal>manifest</goal>
</goals>
</execution>
</executions>
This ends up creating a first-pass manifest under target/classes/META-INF/MANIFEST.MF which exports the package using the bundle version. The version appears to be added to the export by bnd, it isn't in the Export-Package instruction generated by the bundle plugin during this execution (see mvn clean process-classes -X). This is likely down to the slightly different approach taken by bundle:manifest (which analyzes an existing jar/directory using instructions as a guide) and bundle:bundle (which builds a fresh bundle based on the classpath and a set of instructions) - it looks like bnd's Builder takes package-level packageinfo versions into account, but bnd's Analyzer doesn't.
After this extra execution has completed the bundle packaging lifecycle kicks in and builds the bundle - once again mvn -X suggests that the bundle plugin doesn't add any specific versions to the default instructions, but the manifest we get back from bnd has the import range based on the interim manifest generated previously (with exports versioned using the bundle-version). However, the export now uses the packageinfo version.
I've tested this project with the latest maven-bundle-plugin 2.4.0-SNAPSHOT and the incorrect versions no longer appear, so it looks like this has been fixed in trunk.
As a workaround for 2.3.7 remove the above explicit execution of bundle:manifest (it is not required when you use bundle packaging) and you should get the expected results.
was (Author: mcculls):
The attached pom.xml has an additional execution of bundle:manifest which is tied to the 'process-classes' phase:
{code}
<executions>
<execution>
<id>bundle-manifest</id>
<phase>process-classes</phase>
<goals>
<goal>manifest</goal>
</goals>
</execution>
</executions>
{code}
This ends up creating a first-pass manifest under target/classes/META-INF/MANIFEST.MF which exports the package using the bundle version. The version appears to be added to the export by bnd, it isn't in the Export-Package instruction generated by the bundle plugin during this execution (see mvn clean process-classes -X). This is likely down to the slightly different approach taken by bundle:manifest (which analyzes an existing jar/directory using instructions as a guide) and bundle:bundle (which builds a fresh bundle based on the classpath and a set of instructions) - it looks like bnd's Builder takes package-level packageinfo versions into account, but bnd's Analyzer doesn't.
After this extra execution has completed the bundle packaging lifecycle kicks in and builds the bundle - once again mvn -X suggests that the bundle plugin doesn't add any specific versions to the default instructions, but the manifest we get back from bnd has the import range based on the interim manifest generated previously (with exports versioned using the bundle-version). However, the export now uses the packageinfo version.
I've tested this project with the latest maven-bundle-plugin 2.4.0-SNAPSHOT and the incorrect versions no longer appear, so it looks like this has been fixed in trunk.
As a workaround for 2.3.7 remove the above explicit execution of bundle:manifest (it is not required when you use bundle packaging) and you should get the expected results.
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
> Attachments: importTest.zip
>
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FELIX-3630) Packages exported by bundle
are (re)-imported with incorrect version
Posted by "Michael Taeschner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435169#comment-13435169 ]
Michael Taeschner edited comment on FELIX-3630 at 8/16/12 1:45 AM:
-------------------------------------------------------------------
Thanks Stuart, the tip of disabling the manifest execution did the trick.
I don't remember where I picked up the part with including the executions, it just has been this way in my projects until now. Will take more care about that in the future. If this does not qualify as major issue or issue at all you can adjust the severity.
Thanks and Kind Regards,
Michael
was (Author: mitaes):
Thanks Stuart, the tip of disabling the *manifest* execution did the trick.
I don't remember where I picked up the part with including the executions, it just has been this way in my projects until now. Will take more care about that in the future. If this does not qualify as major issue or issue at all you can adjust the severity.
Thanks and Kind Regards,
Michael
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
> Attachments: importTest.zip
>
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3630) Packages exported by bundle are
(re)-imported with incorrect version
Posted by "Michael Taeschner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435169#comment-13435169 ]
Michael Taeschner commented on FELIX-3630:
------------------------------------------
Thanks Stuart, the tip of disabling the *manifest* execution did the trick.
I don't remember where I picked up the part with including the executions, it just has been this way in my projects until now. Will take more care about that in the future. If this does not qualify as major issue or issue at all you can adjust the severity.
Thanks and Kind Regards,
Michael
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
> Attachments: importTest.zip
>
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3630) Packages exported by bundle are
(re)-imported with incorrect version
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch resolved FELIX-3630.
-------------------------------------
Resolution: Fixed
Fix Version/s: maven-bundle-plugin-2.4.0
As mentioned in previous comment, additional executions are now properly handled in trunk.
> Packages exported by bundle are (re)-imported with incorrect version
> --------------------------------------------------------------------
>
> Key: FELIX-3630
> URL: https://issues.apache.org/jira/browse/FELIX-3630
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Reporter: Michael Taeschner
> Fix For: maven-bundle-plugin-2.4.0
>
> Attachments: importTest.zip
>
>
> Packages exported by bundle are (re)-imported with incorrect version using the bundle version instead of the package version.
> I have created an example where the bundle is version 1.2.0-SNAPSHOT and the package-version of the exported package is 1.0.0 (via *packageinfo* file)
> Resulting Manifest:
> Manifest-Version: 1.0
> Bnd-LastModified: 1345038828923
> Build-Jdk: 1.6.0_31
> Built-By: u056801
> Bundle-Description: maven-bundle-plugin Import Package Test
> Bundle-ManifestVersion: 2
> Bundle-Name: Imports Test
> Bundle-SymbolicName: com.mitaes.imports
> Bundle-Version: 1.2.0.SNAPSHOT
> Created-By: Apache Maven Bundle Plugin
> Export-Package: com.mitaes.service;version="1.0.0"
> Import-Package: com.mitaes.service;version="[1.2,2)"
> Tool: Bnd-1.50.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira