Commits are done via the Server, so the post-commit script gets called
no matter what client you're using. That is, if you're not using the
file:// URL for Subversion:
Incorrect:
svn cp file://project/trunk file://project/tags/REL-1.0
Correct:
svn cp http://server/repos/project/trunk
http://ser
I'm having some difficulties with Subversion's Ant tasks.
I am on SUSE 9.0 which has the latest Subversion release of 1.3.
However, I am building with Hudson that is using svnkit which is using
a release 1.4.6 revision. The problem is I build with Hudson, it
creates a 1.4.6 compatible workspace, t
Not what you were asking for - but:
Use cpptask from the ant-contrib project - this handles all the logic of
compiling C and CPP, and also has some plugins for fortran. If handles all
the dependancy analysis for the Code and if your using a standard compiler
gcc, msvc it's all done for you
What I'm doing is tagging a build in an ant script using a user 'build'. This
is an actual user, and not something like apache or someone without a shell
account.
I've got automated builds triggered using Atlassian Bamboo when done from
the command line or doing a commit in a third party app like
Already tested the task?
Shug Boabby schrieb:
Hi all,
I am utterly failing at attempting to implement some logic in an ant
script, I was hoping somebody here could help.
I have a target which calls an external (non-standard) compiler. The
compiler takes a directory as a parameter and recursiv
