Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] FW: Steps before deprecating eclipse-update-site

>Are we done with THE BIG RENAME?

yes. You can go ahead with branching/staging from our point of view.

Jan

-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
Sent: Freitag, 15. April 2011 02:24
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] FW: Steps before deprecating eclipse-update-site

Are we done with THE BIG RENAME? If so, let me merge 342637 to master,
branch 0.12.x and stage both 0.12.0 and 0.11.1. We need to branch before
any new development starts.

As for eclipse-update-site, I believe it is quite different from
eclipse-repository. First, update sites only include "included"
dependencies, i.e., m2e update site only includes m2e features/bundles
but does NOT include m2e dependencies. Second, update sites can include
multiple versions of the same feature, i.e., m2e 0.10.0, 0.12.0, 0.12.1
and 0.12.2 can all be included in the same update site. Based on our
Eclipsecon discussion, I believe new repository descriptor format is
required before these can be supposed by eclipse-repository packaging.

--
Regards,
Igor

On 11-04-14 03:59 PM, Oberlies, Tobias wrote:
> With eclipse-repository becoming more mature and more complete, I
> believe it is time to get rid of the duplication of packaging types
> for building p2 repositories in Tycho. As a first step, we should
> mark eclipse-update-site as deprecated, once eclipse-repository can
> be used in all supported cases.
>
> I currently only know case where using eclipse-repository is not yet
> possible: if the target platform is defined via
> pomDependencies=consider [1]. This issue should be resolved soon; we
> are planning to work on this from next week. After this we will
> replace eclipse-update-site by eclipse-repository in the Tycho
> integration tests - to be sure that everything is covered.
>
> Do you know of additional cases where eclipse-repository is lacking
> functionality or is not suited for your needs? If yes, please create
> bugs or enhancement requests and link them to the umbrella bug for
> the eclipse-update-site deprecation [2]. If you have more general
> concerns, we can also discuss them here.
>
> Best regards Tobias
>
>
> [1] https://issues.sonatype.org/browse/TYCHO-570 : Artifacts from POM
> dependencies missing in eclipse-repository [2]
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=342876 : Deprecate
> packaging type eclipse-update-site
>
> _______________________________________________ tycho-user mailing
> list tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user


Back to the top