ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACE-364) Launcher in the server store folder causes NoSuchMethodError when deploying something
Date Mon, 10 Jun 2013 13:44:20 GMT

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

Marcel Offermans resolved ACE-364.
----------------------------------

    Resolution: Fixed

Problem was caused by duplicate classes on the build path: both osgi.core and o.a.felix.dependencymanager
were not necessary. Also added a line to the bnd.bnd file to never generate an Import-Package
statement (this jar is not really a bundle). Bumped the version to 1.0.1.
                
> Launcher in the server store folder causes NoSuchMethodError when deploying something
> -------------------------------------------------------------------------------------
>
>                 Key: ACE-364
>                 URL: https://issues.apache.org/jira/browse/ACE-364
>             Project: ACE
>          Issue Type: Bug
>          Components: Launcher
>    Affects Versions: 1.0.0
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> When using the launcher that is packaged in the store folder of the server, you get a
NoSuchMethodError when you try to deploy something to this target:
> {code}
> $ java -jar ace-launcher.jar
> Adding additional bundle activator: org.apache.ace.managementagent.Activator
> Started management agent.
>   Target ID    : defaultTargetID
>   Server       : http://localhost:8080
>   Sync interval: 2000 ms
>   Unaffected bundles will not be stopped during deployment.
> Exception in thread "Timer-0" java.lang.NoSuchMethodError: org.osgi.framework.BundleEvent.<init>(ILorg/osgi/framework/Bundle;Lorg/osgi/framework/Bundle;)V
> 	at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4249)
> 	at org.apache.felix.framework.Felix.installBundle(Felix.java:2881)
> 	at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)
> 	at org.apache.felix.deploymentadmin.spi.UpdateCommand.execute(UpdateCommand.java:76)
> 	at org.apache.felix.deploymentadmin.spi.DeploymentSessionImpl.call(DeploymentSessionImpl.java:73)
> 	at org.apache.felix.deploymentadmin.DeploymentAdminImpl.installDeploymentPackage(DeploymentAdminImpl.java:214)
> 	at org.apache.ace.deployment.deploymentadmin.DeploymentAdminDeployer.install(DeploymentAdminDeployer.java:51)
> 	at org.apache.ace.deployment.service.impl.DeploymentServiceImpl.installVersion(DeploymentServiceImpl.java:120)
> 	at org.apache.ace.deployment.task.DeploymentUpdateTask.run(DeploymentUpdateTask.java:57)
> 	at org.apache.ace.scheduler.Executer.run(Executer.java:92)
> 	at java.util.TimerThread.mainLoop(Timer.java:555)
> 	at java.util.TimerThread.run(Timer.java:505)
> {code}
> It seems like some kind of packaging error. The normal "target" distribution works just
fine.

--
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

Mime
View raw message