-
Notifications
You must be signed in to change notification settings - Fork 6
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
introduce properties for flags list #9
base: master
Are you sure you want to change the base?
Conversation
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 good. this is for CLI use mostly, right?
@mbien not only but this is on two repository :D |
@mbien I just added the two differents add-open IDE style and jdk style. |
<!-- jms flags with IDE prefix --> | ||
<addopenflags>${addopensflagsList}</addopenflags> | ||
<!-- jms flags standard --> | ||
<addopenfflags>${addopensfflagsList}</addopenflags> |
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 there no way to avoid this somehow? Why does the maven archetype need to know about the "-J" list too?
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.
I will remove this, the nbm-application that may need the -J is for the other archetype.
ok hope this is good now |
This is the #2 followup to let NetBeans set the addopensflagsList properties itself.
Should let end user configuring in only one place in case of evolution