| Basic update site maintenance question [message #598027] |
Mon, 01 June 2009 20:23 |
 michael.sacarny
Messages: 103
Registered: July 2009
Location: USA |
Senior Member |
|
|
I'm able to use site.xml, Update Site Map, and Build All to build an
update site for various add-ons to our 3.5 Product. Our add-ons appear as
jars in the 'binary', features', and 'plugins' subfolders of the repo
site. When I rebuild, I get additional versions of jars in these three
folders. Root files and custom install actions all work properly, so all
is well and good.
Thinking forward, we might at some point want to remove the older versions
of the components from the update site and move them to an archive site.
How this is done is not at all clear. To remove a set of components, I can
manually edit the artifacts.xml and content.xml files. That seems to work,
but is there a 'correct' way?
I'm at a loss as to how to add existing feature, plugin, and root file
binaries to an existing site. I've tried the Eclipse Ant p2.generator
task, but that doesn't seem to produce metadata for root files or custom
install handlers.
As a related question, imagine a complex repo site that has grown over a
couple of years using Update Site Map. You have all the components, but
due to a mishap, you need to recreate the site. How do you do this?
Any guidance would be very appreciated!
MSacarny
|
|
|
Powered by
FUDForum. Page generated in 0.02842 seconds
] 
Search
Help
Register
Login
Home
