jfrank

Jul 07 2009

svnant 1.3

9 responses so far

9 Responses to “svnant 1.3”

1. # Horston 09 Jul 2009 at 12:05 am

   Hi Joshua,

   thank you very much! My first smoke test with a SVN-1.6-Repository worked fine.

   Regards,
   Horst

2. # Horston 09 Jul 2009 at 4:14 am

   Hi again,

   I turned around the brackets … Your blogging software was afraid of <property …

   Having the

   <property name=”commit-comment” value=”something\\” />

   then a

   <commit dir=”.” message=”${commit-comment}” />

   results in a log message

   something\” –non-interactive C:\my\path\projects

   I simply can get around it with a space:

   <commit dir=”.” message=”${commit-comment} ” />

   But maybe you are interested.

   Regards,
   Horst

3. # jfrankon 09 Jul 2009 at 11:26 am

   Horst,

   From what I can tell you are saying that the double backslash turns into a single slash in your comment, similar to an escape.

   I imagine this is only with the command line client? Is that true?

   This sounds like a good bug report, if you’d like to proceed at subclipse.tigris.org against subclipse, with the svnant component selected.

   Please specify which svn library was being used at the time.

   Joshua

4. # Horston 12 Jul 2009 at 11:34 pm

   Joshua,

   thank you for your reply. I already thought of an escaping problem. The commandline Ant’s problem is slightly different from svnant’s.

   I’m going to send you more details by e-mail because the blogging software would chagrin me …

   Regards,
   Horst

5. # hudsonon 21 Jul 2009 at 1:05 pm

   I was happy to see that there was an update to svnant. I have been using it in a build script to insert the svn version number into the source code for runtime identification, and loosing that automation when building files was a big blow to my workflow.

   However, I have a problem, the variable I was using for the revision number in ant is not getting replaced with the number. This line:

   revision=${svn.info.lastRev}
   used to produce:

   info:
   [echo] revision=198600

   but now it produces :

   info:
   [echo] revision=${svn.info.lastRev}

   I just have the “svnant.jar” and “svnClientAdapter.jar” files in my ant/lib folder, and to upgrade, I just replaced those two files. Is there something else I need to do to get this to work again?
   Regards,
   Hudson

6. # hudsonon 21 Jul 2009 at 1:09 pm

   that last post lost the tags from text I copied from my ant source xml. So, that line
   revision=${svn.info.lastRev}

   should have been in an “echo” tag…

7. # hudsonon 21 Jul 2009 at 2:03 pm

   sorry, ignore my last two posts… I had some code commented out by mistake.

   Now I am still getting the same error I was hoping would be fixed by this update:

   [svn] started …
   [svn] failed !
   [svn] svn: This client is too old to work with working copy ‘bin’. You need
   [svn] to get a newer Subversion client, or to downgrade this working copy.

   Was this the kind of error that was supposed to be fixed?

   Regards,
   Hudson

8. # jfrankon 27 Jul 2009 at 11:29 am

   Hudson,

   You’ll likely need to uninstall and reinstall a new version of subversion on your machine. Since svnant relies on javahl, it doesn’t contain all the bits for being a subversion client except for using svnkit. Your javahl is likely too old. Try setting svnkit=”true” to use it for your library as another alternative.

   Joshua

9. # Guy Davison 19 Aug 2009 at 1:21 pm

   Hi, I just tried to drop the new jars in place on our old ones (few years now). Our ‘ant update’ target gives an error:

   svn: OPTIONS of ‘http://intus002/repos/DVApp/branches/8.14′: authorization failed: Could not authenticate to server: rejected Basic challenge (http://intus002)

   Here’s the target from build.xml:

   I’m running this on a Ubuntu Linux 9.04 system with Sun’s JDK 1.6.0_14. Any ideas on what I’m doing wrong? Running ’svn update’ from that directory works just fine. Your help would be greatly appreciated.

Leave a Reply

Name (required)

Mail (hidden) (required)

Website