#1812

Regression ; missing osgi headers in META-INF/manifest.mf

    • Status: New
    • Priority: Normal (3)
    • Component: actor
    • Estimate: None/Small/Medium/Large None
    Hello,

    akka-actor jar don't include osgi headers (but in 1.3.1 it do).
    Can you include them in the future to allow usage of this great 2.0 version in an OSGI world ?

    Thank you
  • Followers
     
    Ico-users Jonas Bonér , Peter Vlugter , mathieu.barcikowski 
     
    Attachments
    No attachments
    Associations
     
    No associations
    Activity
     
    User picture

          on Feb 12, 2012 @ 06:26pm UTC * By viktorklang

    Don't think we'll have time to do this given the short notice.
    To ensure this makes it into 2.0, I'd love a Pull Request.
    I guess it could use this: https://github.com/typesafehub/sbtosgi
    User picture

          on Feb 12, 2012 @ 06:29pm UTC * By viktorklang

    Milestone changed from 2.0-RC1 to 2.0
    User picture

          on Feb 25, 2012 @ 05:16pm UTC * By viktorklang

    Milestone changed from 2.0 to Backlog
    User picture

          on May 02, 2012 @ 10:46pm UTC * By viktorklang

    Milestone changed from Backlog to Community Involvement Requested
    User picture

          on May 25, 2012 @ 04:09am UTC * By osxhacker

    Hi everyone,

    I, too, have a need for OSGi support and have created a sample project here:

    https://github.com/osxhacker/akka-v2-contrib-osgi

    Using Maven and Akka v2.0.1 to successfully deploy akka-actor and akka-remote into Karaf v2.2.6. The project is by no means production quality, but hopefully will help others in getting this fine product running in an OSGi container.

    One thing that would make wrapping the JAR's easier, IMHO, would be to have a bit more granular packaging with regard to the akka.serialization package. Since there are classes in akka-actor and akka-remote in this same package, it creates a "split package" situation in an OSGi deployment. This is by no means a criticism, just what I hope to be a helpful observation :-). It's not a deal-breaker, though, as what I did was to embed akka-actor and akka-remote together so that a deployment can choose whether or not to have remoting support.

    Thanks again for making Akka!
    Time Expenditure
    Loading