• Type: Bug Report
• Resolution: Fixed
• Priority: L3 - Default
• Fix Version/s: 7.1.0, 7.1.0-alpha1
• Affects Version/s: None
• Component/s: engine
• Labels:

  None

This is the controller panel for Smart Panels app

[CAM-1538] OSGi Manifest headers still mention "Activiti"

Collapse comment: Ronny Bräunlich added a comment - 19/Nov/13 7:30 PM

Ronny Bräunlich added a comment - 19/Nov/13 7:30 PM

Removed all occurences of "activiti" from camunda-engine-osgi module and generated MANIFEST.MF s for camunda-engine and camunda-engine-osgi now have correct "org.camunda.*" imports

https://github.com/camunda/camunda-bpm-platform/pull/47

Expand comment: Ronny Bräunlich added a comment - 19/Nov/13 7:30 PM

Ronny Bräunlich added a comment - 19/Nov/13 7:30 PM Removed all occurences of "activiti" from camunda-engine-osgi module and generated MANIFEST.MF s for camunda-engine and camunda-engine-osgi now have correct "org.camunda.*" imports https://github.com/camunda/camunda-bpm-platform/pull/47

Collapse comment: Roman Smirnov added a comment - 21/Nov/13 2:50 PM

Roman Smirnov added a comment - 21/Nov/13 2:50 PM

Hi Ronny,

I merged your pull request!

Furthermore, the "engine/pom.xml" contains some additional osgi imports, which are declared as "optional". But this imported packages are not marked as optional in the generated MANIFEST.MF file. Would you like to have a look into it, why is that so?

Cheers,
Roman

Expand comment: Roman Smirnov added a comment - 21/Nov/13 2:50 PM

Roman Smirnov added a comment - 21/Nov/13 2:50 PM Hi Ronny, I merged your pull request! Furthermore, the "engine/pom.xml" contains some additional osgi imports, which are declared as "optional". But this imported packages are not marked as optional in the generated MANIFEST.MF file. Would you like to have a look into it, why is that so? Cheers, Roman

Collapse comment: Ronny Bräunlich added a comment - 21/Nov/13 3:23 PM

Ronny Bräunlich added a comment - 21/Nov/13 3:23 PM

Hi Roman,

thank you!

Yes, I already investigated the problem and I think that should be another JIRA issue because it would require changes on several modules (from my point of view).
When you look at the pom.xml in the engine-osgi module you'll find the configuration for the maven-bundle-plugin, which includes all the variables e.g. ${camunda.osgi.export}
The engine module declares its variables but lacks this configuration.
I guess the best thing to do would be to move the configuration from the engine-osgi module to the root pom. But right now I am not sure what the consequences would be for the other modules. Seems like I gotta do some research

Expand comment: Ronny Bräunlich added a comment - 21/Nov/13 3:23 PM

Ronny Bräunlich added a comment - 21/Nov/13 3:23 PM Hi Roman, thank you! Yes, I already investigated the problem and I think that should be another JIRA issue because it would require changes on several modules (from my point of view). When you look at the pom.xml in the engine-osgi module you'll find the configuration for the maven-bundle-plugin, which includes all the variables e.g. ${camunda.osgi.export} The engine module declares its variables but lacks this configuration. I guess the best thing to do would be to move the configuration from the engine-osgi module to the root pom. But right now I am not sure what the consequences would be for the other modules. Seems like I gotta do some research

Collapse comment: Roman Smirnov added a comment - 25/Nov/13 8:53 AM

Roman Smirnov added a comment - 25/Nov/13 8:53 AM

Hi Ronny,

you are right that should be another JIRA Issue. Therefore I created a new Bug CAM-1551, maybe you can assign it to you (I was not able to do it ).

Cheers,
Roman

Expand comment: Roman Smirnov added a comment - 25/Nov/13 8:53 AM

Roman Smirnov added a comment - 25/Nov/13 8:53 AM Hi Ronny, you are right that should be another JIRA Issue. Therefore I created a new Bug CAM-1551 , maybe you can assign it to you (I was not able to do it ). Cheers, Roman