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

Unit test MavenProjectParser #918

Closed
BoykoAlex opened this issue Dec 6, 2022 · 1 comment
Closed

Unit test MavenProjectParser #918

BoykoAlex opened this issue Dec 6, 2022 · 1 comment
Assignees
Labels
for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: internal-architecture theme: refactoring type: enhancement

Comments

@BoykoAlex
Copy link
Contributor

Some tests for MavenProjectParser would be useful. For example test that resources you're expected to be parsed and present in the list of sources, only them and nothing more.
It is important to have a grip over resources being parsed for example not to parse files especially POM's from the output folder (i.e. /target or /bin)

@BoykoAlex
Copy link
Contributor Author

Addressed for now with c8b12a3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: internal-architecture theme: refactoring type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants