I meant to rename this thread...
On 3/13/09 9:46 AM, Richard S. Hall wrote:
On 3/13/09 5:46 AM, Dennis Geurts wrote:
Hi all,
Some questions about testing within the Apache Felix project
in
general:
The pom/pom.xml defines dependencies to:
- easymock 1.2 (the jdk1.3 type) and
- junit 3.8.1
Is there a special rationale for using these versions ?
I can understand the need being able to support jdk 1.4 and
earlier for the actual delivered binaries, but does/ should this also
hold for the tests ?
Well, if you plan to run on devices only running 1.4, then it is nice
to be able to test on those devices, since there are issues that might
only show up on those devices.
I've seen enormous improvements in both junit 4 and easymock
2.4
and (like to) use it in my tests. These improvements, however require
me to run the
tests using java5 or higher.
I therefore (locally, for now) created a separate folder
(test/deviceaccess) with its own pom.xml (that does not link to the
Apache Felix parent pom) in which I have placed
all my tests.
Since it is not linked to the parent pom and the parent pom
does
not define it as a module, I think one would still be able to generate
all binaries using jdk1.4.
I don't think generating 1.4 binaries is the simple part, the difficult
part is not becoming dependent on API > 1.4.
Could this be considered an acceptable solution ?
We never really settled this. Clearly having tests is better than not
having them at all, but having tests that run everything is even better.
What do people think?
-> richard
Regards, Dennis
On 12 mrt 2009, at 17:48, Dennis Geurts wrote:
Hi all,
Nice to see that the device access spec implementation has
found its place within Felix.
I hope it's useful; if question arise I will answer them as
soon as possible.
I'll initially focus on getting some tests available.
regards,
dennis
On 11 mrt 2009, at 23:40, Marcel Offermans (JIRA) wrote:
[ https://issues.apache.org/jira/browse/FELIX-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans resolved FELIX-10.
-----------------------------------
Resolution: Fixed
With the paperwork in place, I imported the code into our repository.
That ends this task as far as I'm concerned. It might trigger a couple
of follow up tasks though (checking if the implementation passes the
TCK, maybe porting it to foundation profile, etc..).
Implement Device Access
-----------------------
Key: FELIX-10
URL: https://issues.apache.org/jira/browse/FELIX-10
Project: Felix
Issue Type: New Feature
Components: Device Access,
Specification compliance
Reporter: Richard S. Hall
Assignee: Marcel Offermans
Attachments: device-access.zip
See section 103 in the OSGi R4 Service
Compendium for a full description of the task. Since implementations of
this service exist, perhaps a donation would be possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
<luminis_logo.jpg>
No trees were killed in the sending of this
message.
However, a large number of electrons were terribly disturbed!
-------------------------------------------------
Dennis Geurts
luminis
iQ
Products
B.V.
K.v.k Centraal Gelderland: 09
16 28 93
-------------------------------------------------
+31 6 12078236
[email protected]
www.luminis.nl
-------------------------------------------------
No trees were killed in the sending of this message.
However, a large number of electrons were terribly disturbed!
-------------------------------------------------
Dennis Geurts
luminis
iQ
Products
B.V.
K.v.k Centraal Gelderland: 09
16 28 93
-------------------------------------------------
+31 6 12078236
[email protected]
www.luminis.nl
-------------------------------------------------
|
