docs: add Eclipse IDE import steps and known Eclipse validator issues - #343
Open
KushalGupta0 wants to merge 1 commit into
Open
docs: add Eclipse IDE import steps and known Eclipse validator issues#343KushalGupta0 wants to merge 1 commit into
KushalGupta0 wants to merge 1 commit into
Conversation
Signed-off-by: Kushal Gupta <pcc.varshney@gmail.com>
Contributor
|
I’ll validate this when I am able. As far as I know, Eclipse IDE is still yet to support Jakarta EE 10, and the Payara plugin still doesn’t work. mvn clean install working is way too low of a usability bar for an IDE. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #201
This adds Eclipse IDE setup steps to the README, mirroring the existing VS Code section.
While testing the import (File > Import > Maven > Existing Maven Projects), I ran into a bunch of Facelet/JSF validator errors in Eclipse's Problems tab — turned out these are just Eclipse's bundled validators not fully understanding the
jakarta.*namespace used in Jakarta EE 10. The actual Maven build (mvn clean install) works fine regardless, so these are false positives. Disabling a few specific validators in project Properties > Validation clears most of the noise.There are also a couple of harmless XML warnings left in
web.xmlaround the${db.jdbcUrl}placeholder — these come from Eclipse validating the file before Maven does its resource filtering, so they're expected and safe to ignore.Added both the import steps and a note about these known issues to the Known Issues section, so future contributors don't get stuck wondering if something's actually broken.