[jbosstools-dev] [Soa-tools-list] JBTIS: Managment of External Components

[Max Rydahl Andersen]

>> Actually, this was found during the site build, which is actually 
>> better,
>> because there is no way of knowing whether or not various components 
>> have
>> updated their poms to use the latest TP (which is probably why SY was
>> removed from the distro: to get the site projects building again), so 
>> there
>> is no real advantage to keeping this in the TP versus accessing the 
>> mirrored
>> repo from the site projects.  In either case, the artifacts in 
>> question are
>> mirrored appropriately (they're either part of the TP repo or the 
>> JBTIS
>> repo).
>
> Actually, since we're providing a single TP repo for a platform, I 
> think it actually makes more sense to include things like this in the 
> JBTIS repo.
> If we need to roll versions in the future, that would mean updating 
> the TP, which could break existing JBTIS repo's (because the latest TP 
> has an incompatible version).

Not fully sure what you mean here. When you say JBTIS repo what do you 
mean ?

And how would existing JBTIS repos be broken by a change to a newer 
version of the TP ? If they get broken they need to break wont they so 
we can fix it ?

/max
http://about.me/maxandersen