Quantcast
Viewing all articles
Browse latest Browse all 12162

Re: Problems with manifest files in 4.0.0-rc2

I can only test your changes on Monday, because my local development environment here is not properly configured.

Sure, no hurry, we all need weekends Image may be NSFW.
Clik here to view.

 

Have a look to the class FileUtils, the classloader provided in the signature is never used.

Ahh, good catch. Will fix this.

 

The thing you are looking for has already been implemented and specified by the OSGi Alliance. It is called "Declarative Services",

Great! Will definelty look into it.

 

What's pretty cool, is that the file can be hardcoded or automatically generated. In Maven, there is the "Apache Felix Maven SCR Plugin". It uses annotations that only exist at compile time.

Those annotations are actually a problem: aSmack is build form sources, and the org.apache.felix.scr.annotations.Activate import will result in a compilation error if Smack is build against the android.jar. But nevertheless I think we are on a good track here. The XML file can simply be added as resource file. After all the felix annotations and the resulting automatic generation of the xml resource file provides very little benefit in Smack.

 

Will experiment a bit with it and let you know of the outcome.


Viewing all articles
Browse latest Browse all 12162

Trending Articles