Yeah,

I must have been caught in between the commits or something. 30
minutes later, everything built.

But I think the question is still valid for the next time somebody
hits the problem, assuming it stays there after another hour or
whatever.

Regards,
   Alex.
----
Sign up for my Solr resources newsletter at http://www.solr-start.com/


On 4 January 2015 at 12:43, Erik Hatcher <[email protected]> wrote:
> I just ran (cd solr; ant clean package) on a clean 5x checkout:
>
>   BUILD SUCCESSFUL
>   Total time: 6 minutes 15 seconds
>
> Mac OS X 10.10.1
>
> $ ant -version
> Apache Ant(TM) version 1.9.4 compiled on April 29 2014
>
> $ java -version
> java version "1.8.0_25"
> Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
> Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
>
>
>> On Jan 4, 2015, at 11:35 AM, Alexandre Rafalovitch <[email protected]> 
>> wrote:
>>
>> Hi,
>>
>> I did a checkout of the latest 5.0 and the build fails (with ant clean
>> package). With errors from two different JIRAs ports it seems.
>>
>> Should I provide the feedback or do I assume that the Jenkins builds
>> catch this? I can see the build fails, but does not seem to be where
>> mine is? Does it exercise the same build path?
>>
>> If I do need to contact somebody, do I just ping this mailing list or
>> should I notify the JIRAs that I think caused this? Or both?
>>
>> What's the minimum noise + highest impact strategy here?
>>
>> Thanks,
>>   Alex.
>> ----
>> Sign up for my Solr resources newsletter at http://www.solr-start.com/
>>
>> ---------------------------------------------------------------------
>> 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]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to