Jason van Zyl wrote:
Maybe you have the old jars, but site.xml and other update site
metadata files you copied from the dev site don't have previous
releases anymore, hence they can't be installed using Eclipse update
manager. It is easy to see if you compare your site.xml with site.xml
I published for 0.9.6 and previous releases.
The steps required for publishing release are outlined on the wiki at
http://docs.codehaus.org/display/M2ECLIPSE/Developer+Guide#DeveloperGuide-Publishingrelease
Those don't seem to point out the actual commands or tools to run like
that for indexing the p2 metadata.
That is why I called it the outline. The reference to p2 command been
removed from the guidelines for publishing dev build because Tycho can
generate p2 metadata now. If you look into the wiki history, you can
recover command for generating p2 metadata, e.g.
http://docs.codehaus.org/pages/viewpage.action?pageId=112132170#ConfiguringDevelopmentEnvironment-GeneratingP2metadataforupdatesite
Note that -metadataRepositoryName and -artifactRepositoryName should
be unique for each repository or else p2 update manager gets confused or
user will see multiple entries with the same name.
Unfortunately there is no support in Tycho for merging update sites
and I don't think it is possible to use Tycho to regenerate metadata for
manually merged update site.
I'll sync up with Igor and get this fixed up later today. Until then
you can try the current release and anyone who is desperate can use
the /update-previous address.
Like I described in my other email, current release can't be installed
because it conflicts with the dev update site.
Also, it seems like you also forgot to tag the release in svn.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
