Looking for .NET Core version of Remote Tea Client

2018-01-11T16:56:17.751000Z

Hi Balakumar,

except for the C# - fork RemoteTea.Net of this project I do not know any C# implementation of the ONC/RPC protocol. And even with that implementation I have not made any experience yet.

Sorry that I cannot give you help with this topic!

Regards,
Harald

Looking for .NET Core version of Remote Tea Client

2018-01-11T05:46:49.087000Z

Hi,

Is there a .NET Core/Standard version available for Remote Tea? So that i can use it in my .NET COre project.

Or what is the way to use the existing .NET version of Remote Tea dll in .NET core application?

Thanks

Some issues

2016-02-24T13:09:12.909000Z

Hi,

thanks for giving a post on these issues in here. I have not seen the linked issues yet, and probably would not have seen them at all, as I am not following the duplicate of remotetea at github.

However, I am going to solve both issues and going to publish them with version 1.1.4.

Regards,
Harald

Some issues

2016-02-23T23:25:41.313000Z

Hi
there is any plan for solve these issues:
https://github.com/remotetea/remotetea/issues/1
https://github.com/remotetea/remotetea/issues/2
thanks in advance
regards

OSGi Integration

2016-02-22T15:53:53.705000Z

Hi Guiseppe,

thanks for drawing attention to this limitation. The org.acplt.oncrpc.server package shall be part of the export as well. Give me a day to fix this and publish the change.

Regards,
Harald

OSGi Integration

2016-02-22T14:57:01.873000Z

Hi all
I need to use oncrpc library in java under Karaf (OSGi container) and I have a problem due to Import packages.
In the pom I see that only org.acplt.oncrpc package is exported, but I need org.acplt.oncrpc.server package.
There is some reason to not export other packages? If not, is it possible to remove following rows from pom?

<Export-Package>org.acplt.oncrpc</Export-Package>
<Import-Package>
     *
</Import-Package>

Thanks
Giuseppe

License Compatibility

2015-08-27T10:09:49.130000Z

Hi Harald,

thank you for jumping in so quickly, giving a clear answer. Favouring LGPL myself, I have nothing to add.

Regards,
Jens

License Compatibility

2015-08-21T21:13:45.065000Z

As the original author of RemoteTea I won't re-license the work. LGPL was choosen on purpose. No discussion.

License Compatibility

2015-08-21T18:22:33.123000Z

RemoteTea is currently licensed under the LGPL version 2. Unfortunately large bodies of open source java code are under the Apache License v2 (such as all of the projects of the Apache Software Foundation) which is considered incompatible with the LGPL.

This java licensing landscape likely looked very different when RemoteTea was started (I think the Apache License v2 only came out in 2004, and the first RemoteTea commit in sf.net is from 2003). However, at this point in time it means there is a great deal of open source code that could potentially use RemoteTea but can not due to the licensing.

Would the project be willing to consider re-licensing under a more 'permissive' license (such as BSD or MIT) to allow both Apache and (L)GPL downstream use?

Recent posts to Discussion

Looking for .NET Core version of Remote Tea Client

Looking for .NET Core version of Remote Tea Client

Some issues

Some issues

OSGi Integration

OSGi Integration

License Compatibility

License Compatibility

License Compatibility