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

Make glassfish json a required dependency again #368

Merged
merged 2 commits into from
Nov 27, 2019

Conversation

aguibert
Copy link
Member

While testing out some local changes with 1.0.6-SNAPSHOT, I noticed that it is no longer possible to run a standalone program by simply adding Yasson to my pom.xml. I got errors indicating no JSON-P implementation (Glassfish) was found.

Back in 1.0.5 I thought we had Glassfish marked as an optional dependency, but due to some odd interactions with the old <dependencyManagement> block it ended up being a required dependency.

In order to preserve existing behavior with 1.0.5 and earlier we must add glassfish json back in as a required dependency.

@Verdent please review

@aguibert aguibert added the bug Something isn't working right label Nov 26, 2019
@aguibert aguibert requested a review from Verdent November 26, 2019 00:40
@aguibert aguibert self-assigned this Nov 26, 2019
Comment on lines 2 to 16
mvn checkstyle:checkstyle && \
mvn org.glassfish.copyright:glassfish-copyright-maven-plugin:copyright && \
echo "Completed normally"
Copy link
Member

Choose a reason for hiding this comment

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

Where is this file used?

Copy link
Member Author

Choose a reason for hiding this comment

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

This file is not directly used anywhere in the build pipeline. It's just something I wrote for myself to quickly run the delivery checks locally before opening a PR and I thought I'd share it by checking it in

Copy link
Member

Choose a reason for hiding this comment

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

OK, well just in that case I would suggest to be aware of that "copyright" goal does only print out warnings about the files and not fails itself. Goal "check" fails, but does not print any warnings. :D

This is fine if you know about this, but if someone will use it and doesn't know that, he might be a bit surprised after push even when he got "Completed normally".

Copy link
Member Author

Choose a reason for hiding this comment

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

yea that is not ideal, could we perhaps configure the copyright goal to fail instead of just warn?

Copy link
Member

Choose a reason for hiding this comment

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

That is the problem. I tried configure it that way, but I am not sure it is possible right now. Maybe I am missing something, but I could not find any correct settings for that. (That is the reason why I do have both goals under "copyright" profile.)

Copy link
Member Author

Choose a reason for hiding this comment

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

@Verdent I've updated the PR to run etc/copyright.sh so it will fail if the copyright goal fails 👍

Copy link
Member

@Verdent Verdent Nov 26, 2019

Choose a reason for hiding this comment

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

Sounds good to me. Just beware of the file with results that will this copyright.sh creates. It might be worth removing it when you are done.

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll change the copyright.sh script so that it outputs the results to the target/ folder

@aguibert aguibert added this to the 1.0.6 milestone Nov 26, 2019
@aguibert aguibert force-pushed the glassfish-json-required branch from b5142d5 to 3f67491 Compare November 26, 2019 15:24
@aguibert aguibert force-pushed the glassfish-json-required branch from 3f67491 to efd41e6 Compare November 26, 2019 16:43
Copy link
Member

@Verdent Verdent left a comment

Choose a reason for hiding this comment

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

LGTM

@aguibert aguibert merged commit ab32c02 into eclipse-ee4j:master Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants