[jira] [Created] (DIRMINA-1049) Error in mina-statemachine manifest prevents using it in Apache Karaf

["Vesa Pekkarinen (JIRA)" <ji...@apache.org>]

Vesa Pekkarinen created DIRMINA-1049:
----------------------------------------

             Summary: Error in mina-statemachine manifest prevents using it in Apache Karaf
                 Key: DIRMINA-1049
                 URL: https://issues.apache.org/jira/browse/DIRMINA-1049
             Project: MINA
          Issue Type: Bug
          Components: Statemachine
    Affects Versions: 2.0.15, 2.0.14, 2.0.13, 2.0.12
         Environment: Apache Karaf 4.0.6
            Reporter: Vesa Pekkarinen


An error occurs when trying to install a karaf feature that has mina-statemachine bundle as dependency. This effectively prevents using mina in karaf.

{noformat}
2016-10-20 11:28:39,190 | ERROR | pool-8-thread-1                                                  | apache.karaf.features.internal.service.BootFeaturesInstaller | 8 - org.apache.karaf.features.core - 4.0.6 | Error installing boot features
org.osgi.framework.BundleException: Could not create bundle object.
	at org.apache.felix.framework.Felix.installBundle(Felix.java:3057)
	at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:167)
	at org.eclipse.equinox.internal.region.BundleIdBasedRegion.installBundle0(BundleIdBasedRegion.java:117)
	at org.eclipse.equinox.internal.region.BundleIdBasedRegion.installBundleAtLocation(BundleIdBasedRegion.java:97)
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.installBundle(FeaturesServiceImpl.java:1261)
	at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:725)
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: invalid version "${version.commons.lang}": non-numeric "${version"
	at org.osgi.framework.Version.parseInt(Version.java:170)
	at org.osgi.framework.Version.<init>(Version.java:126)
	at org.apache.felix.framework.util.VersionRange.parse(VersionRange.java:98)
	at org.apache.felix.framework.util.manifestparser.ManifestParser.normalizeImportClauses(ManifestParser.java:330)
	at org.apache.felix.framework.util.manifestparser.ManifestParser.<init>(ManifestParser.java:182)
	at org.apache.felix.framework.BundleRevisionImpl.<init>(BundleRevisionImpl.java:121)
	at org.apache.felix.framework.BundleImpl.createRevision(BundleImpl.java:1282)
	at org.apache.felix.framework.BundleImpl.<init>(BundleImpl.java:113)
	at org.apache.felix.framework.Felix.installBundle(Felix.java:3004)
	... 11 common frames omitted
Caused by: java.lang.NumberFormatException: For input string: "${version"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Integer.parseInt(Integer.java:569)
	at java.lang.Integer.parseInt(Integer.java:615)
	at org.osgi.framework.Version.parseInt(Version.java:168)
	... 19 common frames omitted
{noformat}

In manifest we have:
{noformat}
Import-Package: org.apache.mina.core.session;version="2.0.15";resolution
 :=optional,org.slf4j;version="1.7",org.apache.mina.core.filterchain;ver
 sion="2.0.15";resolution:=optional,org.apache.mina.core.service;version
 ="2.0.15";resolution:=optional,org.apache.commons.lang.builder;version=
 "${version.commons.lang}"
{noformat}

commons-lang dependency was removed in this commit: https://git1-us-west.apache.org/repos/asf?p=mina.git;a=commit;h=54f05992 
But maven-bundle-plugin in pom.xml still contains the Import-Package instruction:
{code}
<Import-Package>
        org.apache.commons.lang.builder;version=${version.commons.lang},
{code}

This was found when trying to update 2.0.13 but the problem exists also in 2.0.12, 2.0.14 and 2.0.15.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)