I committed a fix, but there are more problems with the smoke-checking (problems with NOTICE.txt). Its just now the checker makes it further along.
I can look at it tomorrow maybe, its way past beer time. On Thu, Jul 4, 2013 at 11:46 AM, Robert Muir <[email protected]> wrote: > I will exclude this file from the smoke tester then. I just have to wait > until it succeeds locally because my python is not very good. > > > On Thu, Jul 4, 2013 at 11:14 AM, Uwe Schindler <[email protected]> wrote: > >> Hi, >> >> I have no problem with it i fit is *not* part oft he WAR or the example >> folder's lib! If it would be it would be a bug! >> >> In general we should split all JARs needed for "compilation" and those >> for "test runtime" and "production runtime" by 3 different configurations. >> The test runtime is only added to classpath when tests are ran. The >> production env is used for building the webapp/example app. The compile >> classpath only contains direct dependencies, no transient ones. >> >> See e.g. forbidden-apis as an example. It splits those classpaths >> completely (and uses ivy:cachepath for classpath / ivy:cachefileset for >> packaging zips). >> >> ----- >> Uwe Schindler >> H.-H.-Meier-Allee 63, D-28213 Bremen >> http://www.thetaphi.de >> eMail: [email protected] >> >> >> > -----Original Message----- >> > From: Mark Miller [mailto:[email protected]] >> > Sent: Thursday, July 04, 2013 5:09 PM >> > To: [email protected] >> > Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 96 - >> Still >> > Failing >> > >> > >> > On Jul 4, 2013, at 11:06 AM, Mark Miller <[email protected]> wrote: >> > >> > >> we could solve that with an ivy configuration for 'tests' instead >> > >> > Or perhaps solved by that? I don't really know what you are suggesting >> > though - ivy is half as mysterious as maven to me. >> > >> > - Mark >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] For >> additional >> > commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
