Hi nino,
the goal should be to more test per release and not to disable existing
ones.
It is a little hard to help without exact informations, what is exacly
the problem with the test:
- What tests(s) are affected
- What fails (e.g. what bundles do not resolve etc.)
- Whats your enviroument (java + maven version)
- Have you tried to clear your maven-repro + rund a clean install
regards
Christoph
Am 22.05.2017 06:55, schrieb nino martinez wael:
Hi
Over 2 months ago I made the last changes to the 4.x.y branch[1] to
support wicket 8. I cannot get the "bare" felix tests to work (I seem
to be missing some dependency, which I cannot figure out)..
The question is, should I just disable the the test, as there are no
horison on it getting to work and release what we have..? If not, how
should we get the broken felix tests to work, i'm pretty sure its some
dependency thing that's out of sync.
[1]https://github.com/ops4j/org.ops4j.pax.wicket/tree/v4.x.y
Regard Nino
--
--
------------------
OPS4J - http://www.ops4j.org - [email protected]
---
You received this message because you are subscribed to the Google
Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
--
------------------
OPS4J - http://www.ops4j.org - [email protected]
---
You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
