Hello All, The tika-2.x-windows is back up and running - whoop whoop!
Turns out the Maven build configuration wasn't pointing to a settings.xml that had the relevant apache-release profile settings available, thus failing on any step that needed access to the repository. Not sure if there is anything more to be done on INFRA-13647 (I would have thought this profile should be there by default) but for now we should be good. I was thinking we should: - Add a Windows build for trunk - Drop the deploy step from the Windows builds (i.e. move to install command) as we are just wasting cycles and network deploying 2x (one from standard Linux build, one from Windows). Any thoughts? Cheers, Dave
