Geoffrey,

I started to play with a maven and pax-exam based drools-osgi-test project were will be possible to run tests in different osgi environments (equinox-juno, equinox-kepler, felix, knoplerfish, jboss-osgi and karaf).

That project will let us to know the right manifest generation that will be needed for all env.

btw, where should I put this project ?

I added some comments below...

regards,

Cristiano

On 26/03/13 08:54, Geoffrey De Smet wrote:
Christiano, Charles,

Your pull requests conflicted massively with each other :(

I 've done my best to apply the best of both worlds.
Due to the conflict, changes might be lost. Sorry if that has happened.
Contradicting conflicts have been written below.

Some notes on this approach and the current state:
    bnd adds a :uses for each exported package. I use <_nouses> to help create the manifest, but I think it should be removed once we mature the manifest. This is a good article for the curious: http://blog.springsource.org/2008/10/20/understanding-the-osgi-uses-directive/

                            That is good when using Declarative Services and do not require you explicitly start and activate the bundle...

That was used to trick BND and should be maintained in projects that contains "impl" in the package name because that packages are not exported.

I've now spend a lot of time on drools OSGi, and I really need to focus on optaplanner issues.
Edson has agreed to look into future osgi related pull requests for drools.




_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev