Java code coverage in TC 3.1

Hi there,

I'm having trouble getting the code coverage builds to work in TC 3.1 with
the ant runner. The same configuration, as far as I can tell, worked OK with
3.0.1. However, the moment I enable the code coverage in 3.1 the build fails
at the compilation step with a weird error:

java.lang.NoSuchMethodError: org.apache.tools.ant.RuntimeConfigurable.removeAttribute(Ljava/lang/String;)V

I tried using different jdks but with no luck. Running the same build config
without code coverage works fine. Does this require a newer version of ant
(I tried both with the bundled one and with a 1.6.5 I have on that machine)?

Any ideas?

Thx,
Andrei


3 comments

Hello,

There is a bug in TC 3.1 - Ant 1.6.5 in some cases will not work. However
Ant 1.7.0 bundled with TeamCity should work fine. The bug will be fixed in
3.1.1 release.

How did you configure TC to use bundled Ant? It seems that Ant 1.6.5 was
used instead.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Andrei Oprea" <andrei.oprea@rogers.com> wrote in message
news:de7391465e7f8ca57ce300f2c5a@news.intellij.net...

Hi there,

>

I'm having trouble getting the code coverage builds to work in TC 3.1 with
the ant runner. The same configuration, as far as I can tell, worked OK
with 3.0.1. However, the moment I enable the code coverage in 3.1 the
build fails at the compilation step with a weird error:

>

java.lang.NoSuchMethodError:
org.apache.tools.ant.RuntimeConfigurable.removeAttribute(Ljava/lang/String;)V

>

I tried using different jdks but with no luck. Running the same build
config without code coverage works fine. Does this require a newer version
of ant (I tried both with the bundled one and with a 1.6.5 I have on that
machine)?

>

Any ideas?

>

Thx,
Andrei

>



0

Hello Pavel,

PS> There is a bug in TC 3.1 - Ant 1.6.5 in some cases will not work.
PS> However Ant 1.7.0 bundled with TeamCity should work fine. The bug
PS> will be fixed in 3.1.1 release.

Aha, good to know.

PS> How did you configure TC to use bundled Ant? It seems that Ant 1.6.5
PS> was used instead.

I haven't configured anything, I just presumed it did if I did not specify
anything. But looking better I noticed that the machine defines an ANT_HOME
env variable (pointing to the 1.6.5 instalation), so it must be that the
agent used that all the time. I'll specify the one inside the teamcity agent
for that build config, to see if it helps.

Thx,
Andrei


0

Hello,

If anything is configured then TeamCity will try to detect which Ant to use.
It will take into account ANT_HOME environemnt variable or ant.home
property.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Andrei Oprea" <andrei.oprea@rogers.com> wrote in message
news:de7391465e918ca57daa1eb1080@news.intellij.net...

Hello Pavel,

>

PS> There is a bug in TC 3.1 - Ant 1.6.5 in some cases will not work.
PS> However Ant 1.7.0 bundled with TeamCity should work fine. The bug
PS> will be fixed in 3.1.1 release.

>

Aha, good to know.

>

PS> How did you configure TC to use bundled Ant? It seems that Ant 1.6.5
PS> was used instead.

>

I haven't configured anything, I just presumed it did if I did not specify
anything. But looking better I noticed that the machine defines an
ANT_HOME env variable (pointing to the 1.6.5 instalation), so it must be
that the agent used that all the time. I'll specify the one inside the
teamcity agent for that build config, to see if it helps.

>

Thx,
Andrei

>



0

Please sign in to leave a comment.