You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Matthias Wessendorf (JIRA)" <ji...@apache.org> on 2006/10/25 05:53:04 UTC

[jira] Commented: (SHALE-319) Shale-Parent--pom contains repositories

    [ http://issues.apache.org/struts/browse/SHALE-319?page=comments#action_38479 ] 
            
Matthias Wessendorf commented on SHALE-319:
-------------------------------------------

>I strongly disagree. That's what the <repository> element is there for. If we tell people they have to configure their user settings (to get the right repositories), we have just >destroyed the primary reason we switched away from Ant (where you had to customize build.properties files for stuff like this) in the first place. 

at least if ibiblio is down a user wants to add a mirrow or alternate repo

>Sounds like you should set proxy settings in your user settings file, something which *does* belong there. I can build from behind Sun's firewall with no problems, once I set my proxy servers correctly. 

I am not saying that I don't have that stuff setup in my settings, I am able to build, no worries.

>[snip]
> So it tries to download apache2-pom from these...
> it doesn't look in other repos.
>
>Sounds like a bug in Maven to me.

can be that, or we need to remove the <repo/>


[snip]
> Our work around, we changed the shale-parent-pom in our
> corp. m2 repo and commented those repositories out. That works.

>Try this experiment (on a machine outside the firewall):
>* Do the same thing
>* Erase your local repository
>* Do *not* add these repositories to your user settings
  (this reflects the state of the vast majority of the world)
>* Try a build
>* Watch it fail because it doesn't know where to get the
 > dependencies at all.

did everything with a *naked* m2 env. (means no settings at all)

I got this:

Downloading: http://repo1.maven.org/maven2/org/apache/shale/shale-parent/1.0.3/shale-parent-1.0.3.pom
16K downloaded
Downloading: http://people.apache.org/maven-snapshot-repository/org/apache/shale/shale-master/1/shale-master-1.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.shale:shale-parent:pom:1.0.3

Reason: Cannot find parent: org.apache.shale:shale-master for project: org.apache.shale:shale-parent:pom:1.0.3


ok, can be, b/c the people.apache.org is down. BUT! after commented out the repos in -parent, it went through, pretty smooth



So what I did than, *erase* my local_repo again, update shale source, remove the <repo/> from -parent (in source) and run the Shale build.
It went through (and the post shale trinidad build as well)

> 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