Regression ; missing osgi headers in META-INF/manifest.mf
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
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
Leave a comment
on 2012-02-13 01:26 *
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
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
on 2012-05-03 05:46 *
By viktorklang
Milestone changed from Backlog to Community Involvement Requested
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!
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!
OSGi support is added to Akka master, for 2.1
on 2012-06-08 00:20 *
By viktorklang
Milestone changed from Community Involvement Requested to Mingus
Updating tickets (#520, #852, #857, #874, #935, #950, #1364, #1508, #1542, #1559, #1734, #1744, #1755, #1782, #1812, #1824, #1831, #1858, #1871, #1880, #1886, #1892, #1896, #1899, #1929, #1930, #1950, #1952, #1953, #1962, #1966, #1969, #1972, #1973, #1977, #1978, #1986, #1988, #1993, #1999, #2000, #2003, #2005, #2006, #2015, #2016, #2019, #2021, #2022, #2023, #2024, #2025, #2029, #2031, #2032, #2036, #2046, #2048, #2051, #2055, #2059, #2061, #2062, #2064, #2065, #2068, #2072, #2074, #2076, #2078, #2079, #2085, #2087, #2088, #2089, #2090, #2091, #2092, #2093, #2095, #2098, #2099, #2100, #2101, #2102, #2119, #2129, #2134, #2135, #2136, #2144, #2147, #2148, #2156, #2166, #2168, #2172, #2174, #2178, #2183)