[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] Tycho and dependencyManagement
|
Mistria - you need to separate the notion of maven repositories and p2 repositories.
These two can be handled differently.
The only reason why it is bad to have repositories listed directly in your pom.xml is that maven has this brilliant/bad/weird idea that anyone that depend on such a pom also need to get that repository added into their build - its basically "leaking" in the build details of how projext X was built into projext Y which is just *using* not building project X.
With Tycho this is different, especially if you just use target platform + .target file since these do *not* affect the users of your pom.xml AFAICS.
In short, this means Tycho has the possibility to proper isolate the specific list of repositories used at build time which is much better than what default maven's repository listings provides.
/max
> On 04/13/2012 12:29 PM, Igor Fedorenko wrote:
>> No, moving repository information out of project source tree
> I agree with you, but since it is currently pure investigation, we want to evaluate several approaches.
> The idea is to provide a settings.xml specific to our project containing repo information. This settings.xml will still be part of our source tree and passed to Maven with the "-s" flag, but people who have specific management of Maven repo in their organisation would only have to change it as they want (it will be their own responsability to change it).
>
> And what about dependencyManagement for Tycho?
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
