[kepler-dev] SVNKit

[Matt Jones]

Hi Jing --

I think Ben's right -- should be a packaged install, preferably a WAR file
that contains everything someone would need.  So maybe you could add the
Kepler instance directly in the WAR file with the web service so that all an
admin would need to do is drop it in tomcat's webapp directory and the y
would be set to go.

Matt

On Wed, Jul 20, 2011 at 2:28 PM, ben leinfelder
<leinfelder at nceas.ucsb.edu>wrote:

> Hi Jing,
> I think it would be better to use a standard Kepler installer (soon to be
> 2.2?) on the server and package the other services (axis and scheduler war
> files) separately. Then we would have a standard installation of Kepler
> deployed on the remote execution server without worrying about maintaining
> releases for both a "client" and "server" version of Kepler. Can you just
> bundle the axis2/webservice war and the scheduler war into an archive that
> is easily deployed and configured on the server? I believe the target
> audience for the scheduling system is small and mostly comprised of system
> administrators who should be able to unpack the bundle.
> I don't think we should be performing SVN checkouts within code for this
> particular packaging task.
> Thanks,
> -ben
>
> 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 :
> >
> > http://svnkit.com/license.html
> >
> > Can we add the svnkit jar files into kepler/build-area/lib? If we can't,
> does anybody have any other recommendation?
> >
> > Thanks,
> >
> > Jing
> > _______________________________________________
> > Kepler-dev mailing list
> > Kepler-dev at kepler-project.org
> > http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20110720/4fb529c5/attachment.html>