[ http://issues.apache.org/struts/browse/SHALE-319?page=comments#action_38496 ] Wendy Smoak commented on SHALE-319: -----------------------------------
I added apache.snapshots back to shale-parent last night, after Torsten had trouble building the framework. I added it with releases/enabled/false, so it is the same definition that would be inherited from the top-level Apache pom. The issue is that with nothing in your local repo, Maven can't find the snapshot of shale-master in order to inherit the repository definitions. Typical bootstrap problem. :) Matthias, I'm curious whether this makes the problem you were having re-appear. I think it might have been the 'releases enabled' part that exposed whatever Maven bug you were running into. I hope so, anyway! > Shale-Parent--pom contains repositories > --------------------------------------- > > Key: SHALE-319 > URL: http://issues.apache.org/struts/browse/SHALE-319 > Project: Shale > Issue Type: Bug > Environment: behind a firewall / proxy > Reporter: Matthias Wessendorf > Assigned To: Matthias Wessendorf > Fix For: 1.0.4-SNAPSHOT > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
