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

Do not process constants #18

Open
maxdobler opened this issue Apr 29, 2016 · 3 comments
Open

Do not process constants #18

maxdobler opened this issue Apr 29, 2016 · 3 comments

Comments

@maxdobler
Copy link
Contributor

Hi,

I have a bean which has a private static final constant.
The @GenerateMatcher annotation tries to generate a Matcher for this constant...
Is it possible to exclude static final fields from processing?

Greetings,
Max

@lanwen
Copy link
Contributor

lanwen commented Apr 29, 2016

You can unmark class and use annotation directly on the fields you need

@pkokoshnikov
Copy link

I think it no so comfortably to use fields GenerateMatcher. What i have 10 fields and one constant. Besides for ex, selenium pojo is already annotated by annotations. And it looks cumbersome

@lanwen
Copy link
Contributor

lanwen commented Jan 31, 2017

Note for myself:

we can also just ignore fields without getters

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants