Our work around, we changed the shale-parent-pom in our corp. m2 repo and commented those repositories out. That works.
One of my friends from Irian.at (thanks Gerald) also tried this. He works in a bank and they also have hight security settings... the comment out fun in shale-parent-pom fixed his problem as well. -Matthias
I like to remove them from the shale-parent.pom in SVN as well, so that Shale 1.0.4 won't have this bug. Should I nail it to Jira, or just go ahead and commit it. -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
-- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
