Looks like the test was depending on the JARs included in the source code, which were removed in the release process. I can try to spend some time on it.
John On Sat, Apr 16, 2016 at 10:48 AM Anatole Tresch <[email protected]> wrote: > Hi > > It should only be a test dependency, not for production or distribution ;) > > The test once worked, but stopped working again (dont ask me why). It would > be good if someone with more arquillian know how can get it up again. > For me all the OSGI support is quite costly in terms of time, so I stopped > to invest more into it. > > > > > 2016-04-16 16:42 GMT+02:00 John D. Ament <[email protected]>: > > > All, > > > > Going through the notices issue still. I wonder, why do we declare a > > dependency on arquillian/shrinkwrap? We have a single test which is > > ignored that uses it, and I'm not sure what the aim is TBH. > > > > > > > https://github.com/apache/incubator-tamaya/blob/master/modules/integration/osgi/src/test/java/org/apache/tamaya/integration/osgi/TestConfigIntegration.java > > > > So can we kill this test and the dependency? Probably not, since its the > > only test in that module. So how do we test OSGi? > > > > John > > > > > > -- > *Anatole Tresch* > Java Engineer & Architect, JCP Star Spec Lead > *Switzerland, Europe Zurich, GMT+1* > > *Blogs: **http://maketechsimple.wordpress.com > <http://maketechsimple.wordpress.com/> * > *Twitter: @atsticks* >
