--jason
On Thursday, August 14, 2003, at 09:12 PM, Cabrera, Alan wrote:
Mx4j has unit tests that kick in if the jars from Sun are in the lib directory.� They check all the interfaces/classes to make sure that they match.� It's quite handy.
-----Original Message-----
From: Jason Dillon [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2003 9:37 AM
To: [EMAIL PROTECTED]
Subject: Re: API Source code for JSR specs
Refresh my memory please... I do not know what you mean, nor do I know what mx4j is doing... but if I had to guess I would say yes ;-)
--jason
On Thursday, August 14, 2003, at 08:25 PM, Cabrera, Alan wrote:
Ok.�� If there are no objections, I will start on JSR115.� Have you given any consideration to my question about us having signature checking unit tests like mx4j has?
Regards,
Alan
-----Original Message-----
From: Jason Dillon [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2003 8:35 AM
To: [EMAIL PROTECTED]
Subject: Re: API Source code for JSR specs
I am working on finalizing where spec stuff will go. I made an assumption about how maven works which turns out to be in correct.
The purpose of these sources is to allow geronimo to build with out having to have users go to sun and download there specs... there is some license fluff with putting the sun impls into the default repository.
--jason
On Thursday, August 14, 2003, at 07:36 PM, Alan Cabrera wrote:
I noticed that the API source code for JSR88 is in \modules\spec\specs.� Do we need to include API source code for�all JSRs in there?� If so, what's the reason for this?� Also, should we have signature checking unit tests like mx4j has?
Regards,
Alan
