Hi Igor,
do you have suggestions for how to best handle the "management" of
update sites
in the context of Tycho, e.g. where to store them?
The infrastructure I'm building up is for separate teams who develop Eclipse
plugins and want to publish them via update sites so that other teams can
leverage them. To me an update site is basically just another form of
artifact
which I want to put somewhere and which should be HTTP accessible.
I don't want to get into the business of managing the update site repository
"by hand". Ideally a developer should be able to create an update-site type
project and when she builds it (mvn deploy), the update site ends up at the
"right" place.
I'm using Nexus for my Maven group repository and I'm wondering whether
there's
a way to let Nexus handle this problem.
I guess overall I'm struggling with the different way Maven and Eclipse do
things with respect to artifact storage. We talked about this briefly
in the
past.
What would you recommend?
Regards,
-Max
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
