[jbosstools-dev] Who uses .target file?

[Max Rydahl Andersen]

> 
>> And sure - if I remove all my mirrors from settings.xml, do not build other plugins than from one specific branch/trunk on my machine with the same ~/.m2/repo in it then you are correct.
> Having stuff is a settings.xml makes build non portable. It reduces the control build provider have on dependency management since you (as a consumer) decided to use other repositories. Having a settings.xml with repo in it is just like adding stuff to the parent pom, we cannot guarantee that much with customized pom.xml, it's the responsability of the user.

yes, adding repositories to settings.xml is non portable.

Same is it to add it to pom.xml and having different repositories in profiles and see the examples Nick was passing around - they are using arguments
to change the repository and they all make things nonportable.

That is not a bad thing as long as you have a target platform that you use to restrict the resolution of the versions - similar to what plain maven <dependencyManagement> is doing.
 
> I agree that having a clean repo for each branch is an annoying step. But that's the only way I know to guarantee build isolation and consistency (cf Jenkins), and it's working well.

Jenkins is not the only place builds are done.

>> We build from multiple branches
> Ok.
>> we want to use mirrors
> Really? How useful is it? 

*speed*!

> Having customized mirrors in settings.xml is not very compatible with having strong management of dependency sources.

How different is this from using -Dlocal.site=<pathtomirror> ?

*zero* afaics.

/max