For deploying, yes. you need only the dsitributionManagement and the
settings.xml configuration.
But when other projects wants to use your artifacts ( which is of course
not in ibiblio ), they need to know where to download it. So you put
<repositories> in their pom.xml.
About the complexity of the scenario I just gave, its a common scenario
in the OSS community. So its not really that rare a scenario.
^_^
Treloar, Barrie (SAPOL) wrote:
About your inquiry, I guess proxying internal repositories is still
helpful because you need not put your internal repositories in your
project's pom.xml.
Can you explain more about putting the internal repositories in the
project's pom.xml?
The only place the repository is defined is in the
<distributionManagement> section. I have not needed to define the
<repositories> section in my pom yet, only settings.xml needs this.
So if you have 5 teams with their own repositories each, they need only
define one internal repository in their settings.xml each and of course
the mirror. When you don't proxy them, then each team will have one
internal repository in their settings.xml and all the five internal
repositories in their pom.xml.
This seems fair, if a little complicated.
I can't see our environment requiring such complexity.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
