Hi,
On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
--> I think you should declare another "proximity hosted" repository in
your POM.
Thank you. When I reinstalled maven I didn't add the <repository> that
denoted our inhouse repo.
So i believe it helped :)
--> but m2 does know about it nothing
That leads me to another question. Proximity fronts all of our
repositories, both inhouse and external proxy/caches. So wouldn't a
request for the artifact (gov.usitc:usitc:pom:1.0-SNAPSHOT) from the
central mirror that m2 knows about be functionally the same as a request
to the inhouse repo m2 also knows about? The urls are the same. Does m2
interogate the repo to determine its id, or somehow otherwise determine
the repository that is hosting the artifact?
Well, this depends how is your Proximity configured.
I will presume you use the latest RC7 of it and with default
("factory") configuration. It would suffice in situation like yours.
In default configuration the emergeGroups is TRUE, so all groups are
on separate URLs. You can check that with repo browsing page.
So, shortly, the answer is NO, the inhouse repo (which is group
private) does not reside on the same URL as repo central (which is
public group).
One is here:
http://host/proximity/repository/public
and one here
http://host/proximity/repository/private
No?
(this presumes a default config and that you deployed your company
parent POM into predefined inhouse repo!)
M2 does not interrogate reposes about their ID, the ID's are just "for
humans" to associate base URLs and (optionally) auth and other stuff
to repositories. It just uses their base URL and concatenates it with
the calculated path from artifact attributes...
(gov.usitc:usitc:pom:1.0-SNAPSHOT ->
/gov/usitc/usitc/pom/1.0-SNAPSHOT/pom.xml or something like that)
-- M2 people, correct me if i'm wrong!
I hope I did not misunderstand your question....
Hope helps,
~t~
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
