Make abstract package protected methods in PEPItem public

[rvaibhav]

fixes SMACK-372

[Flowdalic]

Thanks for your contribution.

Could you shorten the subject of the commit message so that it follows the 50/72 rule. E.g. "Make abstractpackage protected methods in PEPItem public". Also please mention the issue key "SMACK-372" somehwere in the commit messages body.

[rvaibhav]

@Flowdalic to shorten the git message shall I open a new pull request and close this one?

[Flowdalic]

No you can update existing PRs by just issuing a forced push to the source branch.

[rvaibhav]

@Flowdalic ammended the commit message.
Can you please review again.

Thanks

[Flowdalic]

There is a missing space between "abstract" and "package". Also please don't put the issue key in the subject. Simply add

Fixes SMACK-372

in the body.

[rvaibhav]

@Flowdalic Made changes as per review comments. Please review again.

[Flowdalic]

The issue key is still part of the subject. Cherry picked with minor modifications as 3bbffea

[rvaibhav]

@Flowdalic
Issue key is "Make abstract package protected methods in PEPItem public"
or "SMACK-372"?

Wanted to confirm so that I do not goof up in future commits.

Thanks
Vaibhav

[Flowdalic]

SMACK-372 is the (JIRA) issue key. See also the commit message of 3bbffea

[rvaibhav]

Thanks!