TC 2.1.1(build 4261), Ipr Runner, Global Lib Problem

Hi,

It seems like global lib names with '-' breaks the ipr runner.

For example a global lib named 'Apache-Jakarta-Commons-Logging-1.1' is
defined with:


Path to Library:
%system.global.library.Apache-Jakarta-Commons-Logging-1.1.path%
Jar patterns: *.jar


system.global.library.Apache-Jakarta-Commons-Logging-1.1.path=...my
path...


]]>
...


<...other elements...> ]]>

The error message from build:
: justDoIt (<1s)
: innerCall (<1s)
: compile (<1s)
: innerCall (<1s)
: compile.DummyModule (<1s)
: javac2 (<1s)
: Reference
global.library.Apache.Jakarta.Commons.Logging.1.1.path not found.


I noticed that in the file 'integrationBuild.xml', all '-' chars are
converted to '.'. Is this '-' issue a problem with my config or a bug in TC?
If it is a config error, where should I correct this?

Thanks,
Melv



4 comments

Hi Melv,

This is a bug in TeamCity. As a workaround you may use ]]> or _ instead of - in global library name. Sorry for the inconvinience :(. Will be fixed in the Benares EAP.

Kind regards,
KIR

0

I have not been following the license policy of Benares, but do this mean we
have to upgrade to get this fixed? Will this also be fixed for TC 2?

Thanks,
Melv

"Kirill Maximov (JetBrains)" <no_reply@jetbrains.com> wrote in message
news:23519975.1185202850380.JavaMail.itn@is.intellij.net...

Hi Melv,

>

This is a bug in TeamCity. As a workaround you may use <space> or _
instead of - in global library name. Sorry for the inconvinience :(. Will
be fixed in the Benares EAP.

>

Kind regards,
KIR



0

Hi Melv,

We'll either release TeamCity 2.1.2 with the fix or you'll get a free upgrade to Benares.
In the meanwhile, you can use the workaround.

Regards,
KIR

0

Ok, the easiest solution for us is to stay with the previous version of TC.
We are looking forward to the next fix and the license policy og Benares.

Thanks,
Melv

"Kirill Maximov (JetBrains)" <no_reply@jetbrains.com> wrote in message
news:4481797.1185352161446.JavaMail.itn@is.intellij.net...

Hi Melv,

>

We'll either release TeamCity 2.1.2 with the fix or you'll get a free
upgrade to Benares.
In the meanwhile, you can use the workaround.

>

Regards,
KIR



0

Please sign in to leave a comment.