I've been manually setting up project-level composite p2 sites that reference release-specific sites. The project sites are in turn included in the composite site for all of Modeling. I plan to do the same for UML2 if/when the build is moved over to Buckminster...
As I mentioned, you can look at how modeling/updates creates an
aggregate for Helios. Kenn's knows the details better---he helped set
this up---but he's on vacation this week and next so we'll need to wait
to get his assistance.
Ed Willink wrote:
After Alex's comment that separate update sites is the preferred
policy, an aggregate site is what we should be looking at.
Presumably we need to manually migrate the existing UML2, UML2-Tools,
old OCL contributions to their new individual sites, and replace the
mdt update site by an aggregate.
Is this right?
Is this what UML2 and UML2-Tools want to do?
Any clues on how to create an aggregate?
On 05/08/2010 14:25, Ed Merks wrote:
For Helios we created an aggregate site that delegated onto the more
specific sites. These are in CVS modeling/updates. That seems like a
better way to go. I.e., keep specific sites and do virtual aggregation
when combined sites are needed.
Ed Willink wrote:
Modisco certainly has its own site.
Papyrus does not list a site.
The communal mdt update site is just UML2, UML2-Tools and old OCL.
It seems that with MDT becoming many rather than just three projects a
communal update site was not tenable.
However since UML2 has no separate update site and both UML2 and OCL
are 'core' components, I think OCL should revert to the communal site,
then users will find the communal site, find good content, and quite
possibly never even find the other site, particularly if we stop
Once you've figured out how the mdt/ocl update site is maintained by
the new releng, perhaps you can revert to the mdt site and perhaps
manually add all the missing 3.x entries and update the project
On 05/08/2010 09:43, Adolfo Sánchez-Barbudo Herrera wrote:
While working on releng, I realised that just OCL has its own update
site. The point is that no other MDT component has one, so I'm not sure
if it's a problem of the MDT/OCL component, otherwise it's a problem of
the other components. Do you have any information/newsgroup link about
"The migration of components to use their own update site" ?
P.S: Releng progress: I committed some releng stuff last friday, but
unfortunately it's not still working ;P. I'll retake the task during
today, let's see if we get a functional bucky build at the end of the
El 04/08/2010 19:24, Ed Willink escribió:
The migration of components to use their own update sites creates
confusion for users.