My interpretation of the theory is that each project has its own
deployment need so that putting the distribution management at the
settings.xml level would be problematic.
On the other hand all projects probably share the same sources for
libraries so putting the repo config in settings makes sense.
My feeling is that the "right" way to handle distribution is in the
project's parent pom (not at the corporate level).
That way each project can have its own deployment specification but the
individual programmer does not have to worry about it.
The parent for the project is set up once by the core team and the rest
of the developers don't have any changes to make at all.
Ron
On 28/02/2012 11:51 PM, Rajwinder Makkar wrote:
Hi,
I have just setup Artifactory 2.4.2 and Maven 3.0 in our environment.
I have this scenario which probably is pretty common in any dev environment
but just want to take inputs on the approach.
My current understanding :
- Only way that maven deploy phase uses to put artifacts in remote repo is
by reading "distributionManagement" tag in the pom.xml. There is no way to
configure the repo for deployment in settings.xml ( under ../conf as well
as user home dir)
Scenerio is :
If i have 100 development teams then :
- either every one need to have distributionManagement tag in 100 pom.xml
- We can has one super pom with the entries and all 100 dev team will
inherit this super pom.
Will appreciate if i can get some help around this on if my assumption are
correct or not , secondly what is the best way to handle this scenarios.
Thanks in advance
-Raj
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
