cannot build trunk on os/x or from within eclipse

[GoogleCodeExporter]

I'm trying to build a jar based on what's in trunk and I'm getting the
following error when using ant on the commandline or from within Eclipse.

There are a few releases of svn out there still in the wild and I'd
encourage you to make this as easy as possible for Eclipse Callisto users,
which would mean removing the svn dependencies from the build.xml file.

Buildfile: build.xml

create_paths:

prepare:
      [svn] Using javahl
Svn : Status
Unsupported working copy format
svn: This client is too old to work with working copy
'/Users/phil/Documents/workspace/sxip-openid-trunk'; please get a newer
Subversion client

BUILD FAILED
/Users/phil/Documents/workspace/sxip-openid-trunk/build.xml:28: Can't get
status of /Users/phil/Documents/workspace/sxip-openid-trunk

Original issue reported on code.google.com by pelja...@gmail.com on 5 Jan 2007 at 4:30

[GoogleCodeExporter]

We used the svnjavahl.jar library to link the package version with the svn 
revision number. 

If you cannot upgrade your svn package, you can try disabling this piece 
from the build file, i.e. remove lines 27-38 from the "prepare" target in 
build.xml.

As a side note, the library was developed on OSX using svn 1.3.x at some 
point (now we're using 1.4.0).

Johnny

Original comment by johnny%s...@gtempaccount.com on 22 Jan 2007 at 2:52

[GoogleCodeExporter]

Original comment by Johnny.B...@gmail.com on 22 Jan 2007 at 4:55

• Changed state: Started

[GoogleCodeExporter]

Not sure if this should be a different thread or not, but I'm using the trunk as
well, and my build fails too, for similar, yet slightly different reasons:

BUILD FAILED
C:\MyStuff\Professional\Sappenin\DifferenceMail\JBossIDE_Eclipse\Openid4java\bui
ld.xml:28:
Cannot use javahl nor command line svn client

I can see the javahl/svn jars in the libext directory, but it appears that ant 
is
unable to find my svn.properties file?  There is a .svn directory in the root
openid4java directory (I'm guessing that was added by eclipse though).

Any ideas? 

Original comment by sappenin on 6 Feb 2007 at 3:51

[GoogleCodeExporter]

Original comment by Johnny.B...@gmail.com on 9 Feb 2007 at 8:16

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Does SVN work for you from the command line?

In order for ant to use javahl lib, I believe it should be copied into the 
$ANT_HOME/
lib directory (or add openid4java/libext to ant's classpath).

Johnny

Original comment by Johnny.B...@gmail.com on 12 Feb 2007 at 8:35

[GoogleCodeExporter]

No, SVN doesn't work from the command line.  I use it via an eclipse plugin.  

How big of a deal would it be to change the build file so that it doesn't by 
default
rely on grabbing the latest/greatest from SVN?  It should still be an option, 
but
maybe something that the user has to do by adjusting the ant command on the 
command
line (like 'ant -buildfromhead or 'ant -buildfromsvn')

In my case, I either download a given version of a libraby like this, and don't 
want
to build something more recent (via SVN), or else I  download via eclipse to 
get the
latest greatest (if I'm contributing or something like that).  In that latter 
case, I
wouldn't use SVN in my ant file anyway.

My $.02.

David

Original comment by sappenin on 13 Feb 2007 at 4:35

[GoogleCodeExporter]

We've put the SVN revision in the build so that wherever the java-openid.jar 
file 
ends up, one can tell exactly what it was built from (and ease troubleshooting. 
etc).

If you're running ant also from within eclipse, you may be able to check / add 
the 
jahahl library in there. Or, you can still comment out the SVN part from 
build.xml 
(see my first reply here).

Hope this helps.
Johnny

Original comment by Johnny.B...@gmail.com on 13 Feb 2007 at 5:33

[GoogleCodeExporter]

The SVN version is part only of the 'dist' target since rev169, so building 
should 
no longer be affected by this.

Original comment by Johnny.B...@gmail.com on 25 Apr 2007 at 5:24

• Changed state: Fixed