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

Show warnings/errors from the BND build #711

Merged
merged 1 commit into from
Aug 18, 2023

Conversation

laeubi
Copy link
Contributor

@laeubi laeubi commented Aug 16, 2023

Currently if one has an error in the pde.bnd file there is no feedback for the user about the problem.

This adds a validator that reads the errors/warning and display them to the user as error markers mapping the error to a line number if possible.

Fix #699

@HannesWell @vik-chand I'd like to include this into M3 as it is otherwise very hard for users to notice that something is wrong (beside from getting annoyed that 'something' seems not working)

@laeubi laeubi requested a review from HannesWell August 16, 2023 09:48
@github-actions
Copy link

github-actions bot commented Aug 16, 2023

Test Results

     246 files  ±0       246 suites  ±0   1h 8m 11s ⏱️ - 7m 5s
  3 299 tests ±0    3 274 ✔️ +2  24 💤 ±0  1 ±0 
10 194 runs  ±0  10 121 ✔️ +2  72 💤 ±0  1 ±0 

For more details on these failures, see this check.

Results for commit f4823ba. ± Comparison against base commit c71d0c1.

♻️ This comment has been updated with latest results.

Copy link
Member

@HannesWell HannesWell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In generell I would be OK with submitting this fix for a relativly new feature, but I think it needs little adjustments.

@laeubi laeubi force-pushed the issue_699 branch 2 times, most recently from a43bbb8 to ff190a5 Compare August 16, 2023 16:26
@laeubi laeubi requested a review from HannesWell August 16, 2023 16:26
Copy link
Member

@HannesWell HannesWell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, looks good.

Since we are relativly close to contribution of M3 on friday I suggest we wait until then and submit it immediatly afterwards.
Then we have some time until RC1 to fix if any regression occures.

Currently if one has an error in the pde.bnd file there is no feedback
for the user about the problem.

This adds a validator that reads the errors/warning and display them to
the user as error markers mapping the error to a line number if
possible.

Fix eclipse-pde#699
@HannesWell
Copy link
Member

@laeubi I have slightly stream-lined the code in two places and force pushed it to trigger a re-build (the previous one seems to had some outages).

Since M3 is now available I plan to merge this as soon as the build succeeds so we have as much time as possible to test this with I-builds.

@HannesWell HannesWell merged commit 81b5061 into eclipse-pde:master Aug 18, 2023
11 of 14 checks passed
@HannesWell HannesWell added this to the 4.29 RC1 milestone Aug 20, 2023
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.

Support for automatic manifest generation: No error markings on bnd file
2 participants