Jan,

there is a hard dependency on GigaSpaces' "com.j_spaces"...

1. Is it really necessary to have a hard coded dependency on the
GigaSpaces implementation, instead of coding against the JavaSpaces
Spec API? And wouldn't GigaSpaces simple be a drop-in replacement?

2. If that is not possible, are we allowed to upload the
"gigaspaces-JSpaces" jar to a maven repository without breaking any
licenses? I.e. we must have the right to redistribute without the user
agreeing to any click-thru license and essentially not risking to be
sued for using their stuff.


I think I will modify it for the JavaSpaces Spec API for now, since it
has already suffered from being outside the IDEA view and refactoring.



Cheers
Niclas

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to