[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] Svnant not finding javahl

From: Sherman, Dennis (END-CHI) <dennis.sherman_at_endinfosys.com>
Date: 2006-09-07 16:50:46 CEST

We're in the middle of developing a prototype and evaluating subversion in
the process. That means we're new to subversion, and there may be something
I'm just missing.

I'm trying to script project checkout and update in Eclipse using ant under
Windows XP. It works fine on my machine, where I've got the subversion
command line client installed. It doesn't work on any of the other
developer's machines, even though everyone has subclipse and svnant. The
subclipse plugin seems to be working well for everyone, its just the ant
task that isn't.

What I want to know is what needs to be done so that svnant will work in
Eclipse on machines that have installed subclipse, but have not installed
the svn command line client.

Installation details:
        Windows XP Pro
        Eclipse 3.2.0 (callisto)
        Subclipse 1.1.5
        Svnant 1.0.0
        Eclipse knows there's a JavaHL plugin installed, JavaHL Win 32
Binaries 1.1.0

Snippets from build.xml:
    ...
    <path id="SVNAntLib" description="SVN Ant Library">
        <fileset dir="${svn.ant.dir}">
            <include name="*.jar"/>
        </fileset>
    </path>
    ...
    <taskdef resource="svntask.properties" classpathref="SVNAntLib"/>
    ...
    <!-- =================================
          target: svn-update
         ================================= -->
    <target name="svn-update" depends="" description="--> update project
from repository">
        <svn javahl="true">
            <update dir="${basedir}" recurse="true"/>
        </svn>
    </target>
    ...

All the above is actually in a base-build.xml that is included in each
project's build.xml. That lets us have a global build file for the entire
product, and there's a "product-update" target there that does an antcall to
svn-update for each project.

Results I'm seeing:

Running ant in Eclipse for the svn-update target for a project's build.xml
results in this output:

Buildfile: D:\Workspace\Product\Adaptor\build.xml
svn-update:
      [svn] Using command line interface
Svn : Updating
up -r HEAD D:\Workspace\Product\Adaptor --non-interactive
At revision 130.
BUILD SUCCESSFUL

Note that it is using the command line interface, even though we have <svn
javahl="true"..

Having spent far too long poking around the web, I tried adding the plugin
directory containing the JavaHL Win32 binaries to my path, and restarting
eclipse.

When running a project's build.xml, I now get:

Buildfile: D:\Workspace\Product\Adaptor\build.xml
svn-update:
      [svn] Using javahl
Svn : Updating
update -r HEAD D:/Workspace/Product/Adaptor
notify.at
BUILD SUCCESSFUL

OK, great. It would be better if it reported the revision, but at least it's
using javahl, and other people won't need to install the command line
client.

But when I use the global build to update several projects at one time, only
the first one uses javahl, and the others use the command line:

Buildfile: D:\Workspace\Product\_Build\build.xml
update-projects:
do-AdaptorConfiguration:
svn-update:
      [svn] Using javahl
Svn : Updating
update -r HEAD D:/Workspace/Product/AdaptorConfiguration
notify.at
do-Adaptor:
svn-update:
      [svn] Using command line interface
Svn : Updating
up -r HEAD D:\Workspace\Product\Adaptor --non-interactive
At revision 86.
do-all-adaptor:
...
do-all:
BUILD SUCCESSFUL

Thanks for any help.

--
Dennis R. Sherman
Endeavor Information Systems
847-227-2976
Dennis.Sherman@endinfosys.com
http://www.endinfosys.com 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Sep 7 16:51:36 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.