Hi,
I upgraded from 1.6.5 to 1.7.1 a few weeks ago. Everything is working fine.
I use antcontrib and ant4eclipse a lot. No problems so far.
I had to upgrade because zipfileset is supported for the junit-task in 1.7.1
but not in 1.6.5 and
I had to run tests out of a jar-file.
Hope this helps a
On 2008-11-20, Gilbert Rebhan <[EMAIL PROTECTED]> wrote:
> 1. Are there any gotchas i have to be aware of, means are their
>any standard tasks/types that behave different from 1.6.5, maybe
>only in special circumstances ?
Your best source may be bugzilla. Search for bugs of type Regressi
I am trying to display the SVN revision number using Ant build system. I have
tried to use svntask. However, it gives me the revision of the current
directory. I would like to default it to the base directory, I've attached
the code snippet:
target name="version">
Any help is
Hi
I can run the below command from a Windows cmd line just fine
cvs -f stat | grep "Repository revision" | gawk '{print $4 " " $3}'
but now I'd like to add it to my build.xml file in a target
I've changed the double quotes with " and single quotes with ' and
every other combi
Hi,
i want to upgrade from ant 1.6.5 to 1.7.1
Some questions, hope for some answers/tips due to your
practical experience.
Given is a workflow, with a bunch of selfwritten tasks,
macrodefs/scriptdefs (mostly ruby),running on windows 2000/
2003/XP and AIX, with sun jdk 1.5.0_11
1. Are there any
the build.xml contains this:
causing ./build.sh to fail bcause junit is not found. Inserting a
solves it. However I wonder wether there is a better way than patching
the build.xml file?
Why isn't a property or such used ?
Sincerly
Marc Weber
On Mon, Nov 17, 2008 at 08:46:01AM +0100, [EMAIL PROTECTED] wrote:
> Where is your ${J2SE-1.4} property set?
> If this property HAS to be set, you could ensure that with .
> If an empty song is valid, you could also add an condition.
>
>
>
>
>
>
>
>
>
>
> Jan
Hi Jan, thanks
On Thu 2008-11-20 at 11:10h, Jonathan Oulds wrote on ivy-user:
:
> As an example we have our project source under SVN. Our CI inspects the
> project then builds and publishes if it detects any changes. however if
> we hard coded the revision number into the ivy file then our CI machine
> would
Not a one liner but a two-liner.
This is the technique I use often for displaying paths with ...
${listing}
The main task just calculates the middle part (${p}) and I have to put
something before and after it.
In your case this is the same:
