Rename master > main

[laeubi]

No description provided.

[laeubi]

@HannesWell @merks can you probabbly look at the setup files if I did adjusted them correctly?

[github-actions]

Test Results

  321 files    321 suites   52m 41s ⏱️
  680 tests   659 ✅ 20 💤 0 ❌ 1 🔥
2 040 runs  1 979 ✅ 60 💤 0 ❌ 1 🔥

For more details on these errors, see this check.

Results for commit 4050a39.

♻️ This comment has been updated with latest results.

[merks]

Looks ok. It will effectively disable the project setup reference in existing workspace.setup, i.e., existing installations will no longer see or use the project setup.

[merks]

If you want to fix and existing installation after this is committed, you can use Navigate -> Open Setup -> Workspace, use Open in Text Editor on the context menu, change master to main, and save:

[laeubi]

@HannesWell it seems that changing the markdown file generates a version bump, I tried to fix that for the future but the configuration looks odd, it tells it wants pom.xml changes (but why?!?) and disables all jgit ignores... confusing.

Another way would maybe to just move the markdown to the root...

[HannesWell]

@HannesWell it seems that changing the markdown file generates a version bump, I tried to fix that for the future but the configuration looks odd, it tells it wants pom.xml changes (but why?!?) and disables all jgit ignores... confusing.

In case of the lemminx-bundle the inclusion is of the embedded lemminx jar is driven by the pom.xml file. And in case the lemminx version is changed in this pom we want to have a an updated qualifier.
However I don't see in the parent (anymore) that pom.xml files are generally excluded. Maybe that's from the past.

[laeubi]

In case of the lemminx-bundle the inclusion is of the embedded lemminx jar is driven by the pom.xml file.

But should not the embedded jar itself already make a difference?

[laeubi]

Further refinements can better be made in separate PRs.

[HannesWell]

In case of the lemminx-bundle the inclusion is of the embedded lemminx jar is driven by the pom.xml file.

But should not the embedded jar itself already make a difference?

The jar is not committed into the repository, it's just copied into the project by the build. Therefore a change in the jar itself doesn't change the git-timestamp.