[ http://issues.apache.org/struts/browse/SHALE-319?page=comments#action_38483 ] Wendy Smoak commented on SHALE-319: -----------------------------------
I'm also not in favor of a solution that requires developers to edit settings.xml in order to build Shale, but I don't think that is the case here. We have releases enabled on apache.snapshots because that is where we have been staging releases. A better idea would be to stage them elsewhere, such as http://people.apache.org/builds/shale/m2-staging-repository, and remove this repository definition from shale-parent. For the java.net repo, I thought I heard that it would be synced with the central repository. If that is true, then we don't need that one, either. The build failures seem to be a bug in Maven's dependency resolution mechanism. It should check all of the repositories, and from the log output, it never checks its own central repo. We had a similar report at Struts this morning. > 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 > > 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
