Hey devs, I think we already discussed it, but now I like to bring it again up to the table.
The "parent pom" in Shale has an "abuse" of <repositories/>. It specifies two repositories inside the <repositories/> xml element. IMO this should be handled by the user's settings.xml file and not by a lib. So, if you are behind a proxy, a corp.-m2-mirrow and a corp-own-m2-repo, you can't build stuff which uses Shale. (This envoironment is sorta production like.) Why can't you build the stuff? Because maven sees only (to fetch Shale dependencies) these two repos: -Apache M2 Snapshot -Java.net So it tries to download apache2-pom from these... it doesn't look in other repos. (currently the apache m2 snapshot repo is down... so it doesn't get Shale-master too, which is! available within a regular m2 repo) Our work around, we changed the shale-parent-pom in our corp. m2 repo and commented those repositories out. That works. 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
