On 5/4/15 10:54 , Christian Schneider wrote:
I just went through the process of getting access to the OSGi tcks at
apache. In the end after signing an agreement and explaining what I
need to
test I got access to the tck jars.
Getting them to work against in my case aries blueprint required some
more manual work again. Still not sure if I am doing it right as there
is not much documentation in the tck jars.
All this effort makes it quite difficult to run the tests. Which
probably results in very few people doing such test runs.
After running the blueprint tests I got 28 test failures. I am not
sure how well I will be able to work with these as I do not have the
test sources. So it is difficult to tell what the tests actually do.
Isn't the source inside of the JAR files?
-> richard
So this leads me to the question: Why is access to the tck restricted
at all? Wouldn't it make sense to publish the sources on e.g. github
so people can directly work with them?
Without the restrictions we could also nicely automate running the
tests against aries and have public jenkins builds that show the
current tck compliance.
Christian
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
