On Mon, May 15, 2017 at 1:26 PM, onders <[email protected]> wrote: > yes i guess so. > there was no such a issue and it's been recently introduced due to our > company security policies. and after doing what Claus suggested, i am > totally screwed up, because all jar's are generated as corrupted. I can not > build anything. >
Ah yeah I have heard of others with that problem. Its a bit sad that Apache Maven dont have any CRC check OOTB of some kind to check that the downloaded JARs are as expected or at least not a HTML page, which you often would see in case of HTTP proxy errors. I heard stories about people about to give talks and on hotel wifi, they had it download over Maven and cause these kind of problems, and they were in trouble before their talks. > I'll try and see what i can do. > Any suggestions are welcome. > > Thanks. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/checkstyle-plugin-problem-tp5799504p5799532.html > Sent from the Camel Development mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
