[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ide-dev] Ctrl-1 driven development
|
On 19 Oct 2015, at 16:10, Doug Schaefer wrote:
Even better, add the supported file types as a provided capability in
the
p2 metadata just like we do with Java packages now.
can you explain that part a bit more ? what do we do with java packages
now in p2 metadata ?
That¹s something we
could easily do now with no code required by the provider other than
the
p2.inf file. And on the consumer side, it should be easy to install
with
the capability as a dependency.
WTP actually recently added support for using p2 info for enhancing the
server adapter install.
Still needs some central place (i.e. marketplace) to perform this lookup
in unless you assume
users have all worlds p2 update sites added to their install ;)
/max
Doug
On 2015-10-19, 10:04 AM, "ide-dev-bounces@xxxxxxxxxxx on behalf of
Torkild
Ulvøy Resheim" <ide-dev-bounces@xxxxxxxxxxx on behalf of
torkildr@xxxxxxxxx> wrote:
I¹ve been following this discussion with interest and I just wanted
to
point out a possible, somewhat vague, solution to one of these
issues. A
registry of file types and associated editors with p2 install
locations
could be shipped with each EPP package, so that Eclipse would know
how to
install the preferred editor when missing. This could even be
extended to
use the Eclipse Marketplace for file types not supported by any of
the
Eclipse projects. ³Someone² could flag i.e. the WTP XML editor as
³recommended², other editors supporting XML should also be listed.
Best regards,
Torkild
--
Torkild Ulvøy Resheim
Consultant / Eclipse Committer / Senior Software Developer
Itema AS - http://itema.no
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev
/max
http://about.me/maxandersen
