Hmm, sad to report that this didn't go well. Not sure yet where the problem lies, but it might be something to do with running gradle 1.0-m6 within Teamcity (tried running the build on the checkout that teamcity created on command prompt and that was successful while teamcity gradle plugin build was failing). Had to rollback to 0.9.2 (which is working fine by the way) to not stifle development. Hopefully I will get a second stab at this soon. regards gretar
On Sat, Dec 3, 2011 at 3:41 PM, Gretar Arnason <gretarr...@gmail.com> wrote: > I'll give it a try and report. > Thanks > > > On Fri, Dec 2, 2011 at 7:52 PM, Adam Murdoch > <adam.murd...@gradleware.com>wrote: > >> >> This is fixed in 1.0-milestone-6. Can you use that instead? >> >> On 03/12/2011, at 4:56 AM, Gretar Arnason wrote: >> >> We are using gradle on teamcity and have been using 0.9.2 for some time >> with good result. Now we are trying 1.0-m5 and are frequently getting some >> errors from the build. >> for example like: >> [12:02:06]: [:ci-assembler:resolveIvy] Download >> http://10.101.10.101:8001/nexus/content/repositories/pisces/calidris/wars/ci-rules-editor-ws/5.4.0.45007/ci-rules-editor-ws-5.4.0.45007.pom >> [12:02:06]: [:ci-assembler:resolveIvy] [Fatal Error] >> ci-rules-editor-ws-5.4.0.45007.pom:1:44: Content is not allowed in prolog. >> [12:02:06]: [:ci-assembler:resolveIvy] org.xml.sax.SAXParseException: >> Content is not allowed in prolog. >> >> When I examine the cache I see that the pom files in question have a size >> zero (and there .part counterpart as well). >> This seems to be only happening on the teamcity buildagent and not in the >> dev environments (running from console). >> The buildagents are running on win7. >> Any help appreciated. >> >> PS. I've also posted this on the forums. >> >> regards >> gretar >> >> >> >> -- >> Adam Murdoch >> Gradle Co-founder >> http://www.gradle.org >> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting >> http://www.gradleware.com >> >> >
