On 06/21/2012 03:54 PM, Rajith Attapattu wrote:
On Thu, Jun 21, 2012 at 10:32 AM, Gordon Sim <[email protected]> wrote:
On 06/21/2012 03:25 PM, Rajith Attapattu wrote:
Does the above answer your questions sufficiently ?
Yes, but I still don't understand why you need to check the built jar into
svn.
How else would I make it available on the Java side?
The API impl on the java side needs this jar file to compile successfully.
Whats the rationale for the current split?
Why don't you include that impl in the bindings code and jar itself?
If/when there are other implementations of the API, then the API itself
would want to live in the Java tree. You could have your JNI based impl
depend on that jar of course (i.e. the API possibly including some
plugin framework for impls).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
