Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update WTP site for 3.32.0 #1429

Merged
merged 1 commit into from
Oct 9, 2023
Merged

Conversation

merks
Copy link
Contributor

@merks merks commented Oct 9, 2023

No description provided.

@merks merks merged commit f8e4be4 into eclipse-platform:master Oct 9, 2023
1 of 2 checks passed
@merks merks deleted the pr-update-setup-wtp branch October 9, 2023 12:18
@vogella
Copy link
Contributor

vogella commented Oct 9, 2023

What is WTP used for? Maybe we could use wild web developer (cc @mickaelistria); AFAIK WWD is in a better state.

@akurtakov
Copy link
Member

Actually WTP is not used but the helper releng tools are used org.eclipse.wtp.releng.tools.feature . Unfortunately, I don't remember what exactly are these used for.

@zulus
Copy link

zulus commented Oct 9, 2023

We use this also in PDT, these helper allow us to modify p2 metadata. Mirrors url (in theory supported by tycho now) and stats url

@laeubi
Copy link
Contributor

laeubi commented Oct 9, 2023

We use this also in PDT, these helper allow us to modify p2 metadata. Mirrors url (in theory supported by tycho now) and stats url

If anything is needed from Tycho and one likes to contribute that feel free to open a PR, if it is important for platform as well I can even consider adding support for it.

@akurtakov
Copy link
Member

Quite often the problem is not functionality is not in Tycho but that old way of doing things stays as no one has the time to redo it in the new way.
P.S. I'm not saying this is or isn't the case here but I had to do exactly this many many times.

@zulus
Copy link

zulus commented Oct 9, 2023

I've checked

  1. Hardcoded WTP repository (from 2010) that remove "Uncategorized" category, in theory no longer necessary: eclipse.platform.releng.tychoeclipsebuilder/eclipse/buildScripts/process-artifacts.xml
  2. org.eclipse.wtp.releng.tools.addRepoProperties as in PDT, it's setup MIRRORURL, p2ArtifactRepositoryName, p2MetadataRepositoryName, see cje-production/promotion/promoteSites.sh

As far as I remember, tycho long time ago, always ignored properties from category.xml, I don't know how it looks now

@laeubi
Copy link
Contributor

laeubi commented Oct 10, 2023

@zulus thanks for investigation, I'm not sure I completely understand (1) so you like to remove the category from the generated updatesite so it is not shown to the user? Why do we need to add uncategorized items to the updatesite at first place? Maybe with modern Tycho we can do better here at the source.

For the second: Since Tycho 4 it is much easier / flexible to add support I think the best would be to provide an integration-test to demonstrate such property usage in category.xml, if it does not work we can quite easy add support for it!

@zulus
Copy link

zulus commented Oct 10, 2023

@zulus thanks for investigation, I'm not sure I completely understand (1) so you like to remove the category from the generated updatesite so it is not shown to the user? Why do we need to add uncategorized items to the updatesite at first place? Maybe with modern Tycho we can do better here at the source.

This was workaround for old bug, already fixed, so could be dropped.

For the second: Since Tycho 4 it is much easier / flexible to add support I think the best would be to provide an integration-test to demonstrate such property usage in category.xml, if it does not work we can quite easy add support for it!

In theory Tycho allow setup such properties directly in tycho-p2-repository-plugin via extraArtifactRepositoryProperties and repositoryName configuration. The problem is that you have to know target repository URL during build. It's not a problem in smaller projects like PDT, but platform have "promotion" procedure and need to setup these url's later, on already generated repository.

@vogella
Copy link
Contributor

vogella commented Oct 10, 2023

This was workaround for old bug, already fixed, so could be dropped.

Thanks @zulus can you send a PR to remove this? You already looked into it, so I assume it is easy for you to get rid of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants