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 commas embedded in command line arguments from Maven plugin #18688
Labels
status: superseded
An issue that has been superseded by another
Comments
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
Oct 22, 2019
philwebb
added
type: bug
A general bug
and removed
status: waiting-for-triage
An issue we've not yet triaged
labels
Oct 22, 2019
I think we should consider this a bug, but I'm worried it might involve making a breaking change. I'll target it to 2.2.x for now. |
nosan
added a commit
to nosan/spring-boot
that referenced
this issue
Oct 23, 2019
nosan
added a commit
to nosan/spring-boot
that referenced
this issue
Oct 23, 2019
Closing in favor of PR #18711 |
philwebb
added
status: superseded
An issue that has been superseded by another
and removed
type: bug
A general bug
labels
Oct 23, 2019
nosan
added a commit
to nosan/spring-boot
that referenced
this issue
Oct 24, 2019
nosan
added a commit
to nosan/spring-boot
that referenced
this issue
Oct 25, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's actually impossible (as far as I can tell) to specify a command line argument that has a comma embedded in it. The comma is swallowed by Maven and turned into a value separator.
E.g.
only exposes one endpoint.
Other Maven plugins seem to make configuration properties of type
String
and parse them out to aString[]
manually. Example: http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#locales. We would have to document an escape sequence, or alternative separator.The text was updated successfully, but these errors were encountered: