-
Notifications
You must be signed in to change notification settings - Fork 10
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
Support package level annotations #5
Conversation
Signed-off-by: Nicolas De Loof <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Signed-off-by: Nicolas De Loof <[email protected]>
made a minor change as this makes access-modifier easier to implement: Drawback doing so is that such entries in index will produce |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks acceptable even with such warning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine 👍
@oleg-nenashev can you merge (and release) this or do you expect more reviews ? |
@jglick as the last person to release it, could you please also take a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actual behavior can be tested like this. Probably you want to syntactically distinguish package names in the index file, e.g.
some.pkg.*
src/main/java/org/jvnet/hudson/annotation_indexer/AnnotationProcessorImpl.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Nicolas De Loof <[email protected]>
@jglick can you please reconsider your review with latest changes ? |
@jglick ping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it still actual @ndeloof ? Looks so
inactive, feel free to take over |
I will take it over, thanks! |
@oleg-nenashev could you please cherry-pick those commit into your own fork so I don't get notified on this PR, I also plan to cleanup my hundreds jenkins-* forks |
Please give me few days to do so
…On Sun, Sep 8, 2019, 18:35 Nicolas De loof ***@***.***> wrote:
@oleg-nenashev <https://github.com/oleg-nenashev> could you please
cherry-pick those commit into your own fork so I don't get notified on this
PR, I also plan to cleanup my hundreds jenkins-* forks
thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=AAW4RIGRFVCDQSE2WFQ6HVDQIUSV5A5CNFSM4FEVKVYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6FT4LI#issuecomment-529219117>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAW4RIAFS3SMXWGMLPK54ZTQIUSV5ANCNFSM4FEVKVYA>
.
|
@oleg-nenashev did you pulled my commits ? |
I just got it merged. Should be good enough for now, thanks! |
see jenkinsci/configuration-as-code-plugin#278 for initial discussion
see jenkinsci/lib-access-modifier#13 for actual usage