GitLab

- FraSCAtiOSGiTracker and OSGiResourceProcessor are dependent of the core and used in frascati-in-osgi and osgi-in-frascati : those two classes are put in the core module
- fix AbstractResource getResource and getResources methods bugs
- configure binding-gcs-test
- bpel, gcs, velocity, widget are available in frascati-in-osgi

    - new way to test if test bundle is loaded
    - frascati-compiler-plugin : FraSCAti composite instead of FraSCAtiOSGi one
    - add log messages

        - improve starter capabilities :  * allow to add InitializableItf object to wait for before launching FraSCAtiOSGiService
        - update frascati-fscript-embedded to use new starter functionnalities
        - update frascati-core to use new starter functionnalities
cosmetic : ignore target and properties files 
                     

Updated examples-native/helloworld-binding-native test case as this example is not supported on Windows.

Move exception classes to the api package.

        * Concierge - XQuery test : move scripts in a new "scripts" directory
        * JBoss - Windows OS - ImplementationOSGi test : test bundle's URL created using the File's toURL method

webexplorer-launcher module

Refresh status of the sub-component when component status change

Move the data analysis from javascript client side to JAVA server-side to improve sustainability ans scalability.
(TODO: services architecture, tests and documentation)  

@produce(text/plain) to avoid "HTTP 204 no content" response that cause troubleshooting in AJAX request

This should free resources.

- Remove sysout 
- Add java generation for ProxyLogWS template

fix osgi binding with Concierge in Windows OS bug : change createJarFile method to be able to use Concierge's bundles storage in Windows OS