Skip to content

JCP fails on unknown value #17

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.

Sign up for GitHub

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

Jump to bottom
Closed
reisi007 opened this issue Apr 20, 2017 · 3 comments
Closed

JCP fails on unknown value #17

reisi007 opened this issue Apr 20, 2017 · 3 comments
Assignees
@raydac
Labels
enhancement

Comments

@reisi007
Copy link

Hi,

I am using JCP for a product line. If a feature is included (e.g. for the feature belt) //#define belt is added.
Currently //#if belt && dev fails, if belt or dev is unknown. Note that this is possible to rewrite as 2 //#ifdef after each other, which is not possible with //#if belt || dev. It would be great to have a way to treat all undefined variables as false in the #if...

Thanks!
@raydac raydac self-assigned this Apr 20, 2017
@raydac
Copy link
Owner

raydac commented Apr 21, 2017

ok, I will add special flag to recognize unknown variables as FALSE

raydac added a commit that referenced this issue Apr 21, 2017
@raydac
#17 added flag to interpret unknown variable as FALSE
408c88b
@raydac
Copy link
Owner

raydac commented Apr 21, 2017

added /U CLI option and unknownVarAsFalse boolean option into Maven and ANT to enable interpretation of unknown variables as FALSE, information about detection of such variables will be printed if caller in debug mode, now you can try

@raydac raydac closed this as completed Apr 21, 2017
@reisi007
Copy link
Author

Thanks! Works as expected 😀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@raydac raydac

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@reisi007 @raydac