david.v.welker at gmail.com
Wed Jul 20 19:07:48 PDT 2011
The build system already issues all sorts of commands to SVN without
using a library such as SVNKit. I have purposely avoided using that
library precisely because of licensing restrictions. However, I have
found that I am able to do all the svn commands I want, including SVN
checkouts, without it. Why not look at existing code (i.e. in
Get.java) as an example.
On Jul 20, 2011, at 3:00 PM, jing wrote:
> Hi, devs:
> I am working on creating a kepler server version installer. It will
> include kepler, workflow run engine and workflow scheduler.
> Building the installer will involve the svn command, e.g. checking
> out workflow scheduler and run engine components from svn
> repositories. To my understanding, the jobs of kepler build system
> are done by java classes, not in the build.xml. So we need a java
> library to handle the svn actions. The library will provide a SVN
> API for the java class which builds the installer.
> I looked a around and found a pure java toolkit - SVNKit. It has
> dual licensing - TMate Open Source License and Commercial License.
> The TMate Open Source License permits you to use SVNKit at no charge
> under the condition that if you use the software in an application
> you redistribute, the complete source code for your application must
> be available and freely redistributable under reasonable conditions.
> It is similar to GPL license. The details can be seen at :
> Can we add the svnkit jar files into kepler/build-area/lib? If we
> can't, does anybody have any other recommendation?
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Kepler-dev