Add limiting scope to pom.xml as suggested in README #98
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.
As the README states:
Derive4J should be declared as a compile-time only
dependency (not needed at runtime). So while derive4j is
(L)GPL-licensed, the generated code is not linked to derive4j, and thus
derive4j can be used in any project (proprietary or not).
However, the provided maven tags do not impose this requirement
potentially causing legal issues for folks who accidentally forget the
proper scope in proprietary codebases.
This PR ensures that the default pom example uses the recommended
practices.
This also removes a bit of unnecessary whitespace in the README.