Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Request for comment: Provide standard update site locations

Hi Michael,

> Likewise it is also sometimes *very* difficult to find the git/svn repository of a given plug-in.

This is technically solved already with the Eclipse-SourceReferences header in the MANIFEST.MF file.
EGit supports this since version 2.0:

The Eclipse Platform acutally uses this, and the workflow for end users is really nice:
- Open the Plug-Ins view in the Plug-In Development Perspective
- Pick your plugin, right-click > Import As > Project from a Repository...
- It clones the git repo into your workspace and you're all set. 

Not being able to pick a location for the cloned repo is one of the known limitations right now, but for an occasional look-up in a plugin that you don't need too often, or for a quick patch, that is still good enough.

What I don't know at this time is in what respect Tycho / CBI already supports generating the Eclipse-SourceReferences header,
and what a project needs to do to adopt this.

Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River
direct +43.662.457915.85  fax +43.662.457915.6

-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Michael Scharf
Sent: Friday, March 15, 2013 4:02 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Request for comment: Provide standard update site locations

Hi all,

I wonder what the sate of "findable" updates sites is? There has not been much progress on the issue recently. I think one problem is to have a common pattern but another problem is "how to find the update site". Today I was looking for the update site of EMF 2.9.
This is not easy. Once I found it, it could not update because the plug-ins I needed also needed a new version of xtext. So another round of hunting started.

As a user this is really difficult. P2 solved a lot of dependency problems but the new type of dependency is to find the correct update site. Once they are found, p2 does a great job...

Ideally there should be a simple update site and repository search facility that allows to look up the update sites and the repository for a given plug-in or feature.

Hmm, thinking of it, it would be nice to get form a package or a class to the project, the update site, to the repository, mailing list, newsgroup, and to the correct component in bugzilla etc.

E.g. on the page could be a search button that would find the resources associated with a package, plug-in or feature.

Or does such a facility already exist and I have not found it?


On 4/18/12 6:57 PM, Miles Parker wrote:
> Hi all,
> Please see the bug below. Isn't it about time we had a good common approach to this?
> 377111: Provide standard update site locations 
> Please follow up on bug.
> cheers,
> Miles
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx

cross-project-issues-dev mailing list

Back to the top