We're experimenting in the OSGi with the compilers -jsr16 target. This
allows us to program in J5 but generate 1.4 output ... Really cool.
Kind regards,
Peter Kriens
On 8 okt 2009, at 13:44, Karl Pauls wrote:
On Thu, Oct 8, 2009 at 12:43 PM, Don Brown <[email protected]> wrote:
I do have several that would be applicable, but they require Java
1.5.
I couldn't find anything about Felix's stance on Java compatibility
other than it seems Maven is targeting 1.3. What would it take for
that to change? Would it be possible to have the build require 1.5
(for tests) yet build 1.3 core jars? Maven 2 already requires 1.5,
so
the 1.5 JVM will be there.
Yes, that is no problem. The default is 1.3 but you can request 1.5 on
a per project basis.
regards,
Karl
Don
On Thu, Oct 8, 2009 at 9:34 PM, Karl Pauls <[email protected]>
wrote:
The more tests we have the better! Are you interested in bringing
over
the tests as well? That would be cool :-)
regards,
Karl
On Thu, Oct 8, 2009 at 12:29 PM, Richard S. Hall <[email protected]
> wrote:
On 10/8/09 12:24, Don Brown wrote:
Since the TCK seems to be a deadend for automated testing, what
other
options do we have? Richard, you said you were working on a
testing
framework, but I don't see it svn. Are there a set of
integration/functional tests I'm missing? I have a little
framework
we use in Atlassian Plugins for integration testing that I could
bring
over.
I am using BND and my few tests are included in the my sandbox:
http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/
There is some [likely outdated] description of this here:
http://felix.apache.org/site/bnd-testing-harness.html
This isn't integrated in anyway, because there was no decision
within the
community to go with it, but it is still what I use when I create
a new test
cases. It is also what the OSGi TCK is based on.
-> richard
Any objections?
Don
--
Karl Pauls
[email protected]
--
Karl Pauls
[email protected]
