[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Validating Aggregator fails because of legacy update site -> MAT
|
HI all,
Apologies if my update of MAT yesterday caused trouble for the rest. As we contribute relatively seldom, I just kept doing what used to work in the past.
Do I understand it correctly what “legacy update sites” means – for me this is the old-style structure with a site.xml and no p2 metadata – is this so?
The structure of the site I contributed yesterday (http://download.eclipse.org/mat/oxygen/RC1/update-site/) looks like this:
binary/
features/
plugins/
artifacts.jar
artifacts.xml.xz
content.jar
content.xml.xz
p2.index
We build it with tycho using packaging eclipse-repository. I compared with some of the other contributions, and it seems to be the same structure. Am I missing something?
Regards,
Krum
On 23.05.17, 21:47, "cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of David Williams" <cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of david_williams@xxxxxxx> wrote:
On 05/23/2017 01:47 PM, Alexander Nyßen wrote:
> Hi all,
>
> when validating the Oxygen aggregator on my machine, the validation
> fails because of an unsupported legacy update site. It seems this was
> introduced by updating MAT. If I disable MAT and Andmore (which
> depends on it), the validation succeeds on my local machine.
>
I will also add, in case not obvious, that "legacy update sites" are
explicitly dis-allowed in the Sim. Rel. aggregation. The aggregator
itself should still allow it, if someone was building their own site and
set the property "Allow Legacy Sites" to "true".
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
