Community
Participate
Working Groups
It occasionally happens that the MANIFEST file gets corrupted when a new service component is added. The Service-Component header is added at the end of the previous line, the entries for that header are split and cut somehow. I don't have a clear way that reproduces this issue. It happens sometimes. The only thing I always have set is org.osgi.service.component.annotations;version="1.2.0";resolution:=optional in the Import-Package header. The Service-Component header follows. The first service added looks fine. If I add a second, the error comes up. But if I try to reproduce it the same way it happened before, it does not happen again.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
