-
Notifications
You must be signed in to change notification settings - Fork 34
Don't enforce upper case for variables. #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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,9 +27,7 @@ public abstract class PortType implements ExtensionPoint, Describable<PortType>, | |
| public final String name; | ||
|
|
||
| protected PortType(String name) { | ||
| // to avoid platform difference issue in case sensitivity of environment variables, | ||
| // always use uppser case. | ||
| this.name = name.toUpperCase(); | ||
| this.name = name; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's a breaking change as well. It should be managed by a system property IMO
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Plugin must just save what user entered and then pass to environment. Current behaviour absolutely not obvious. I'm configuring job, entering variable "my_port", pressing save, then build is broken because code decided to do upper case. And this is really breaking change.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Property can't care about slave systems. Passing as is without doing magic is the best behaviour imho. |
||
| } | ||
|
|
||
| /** | ||
|
|
||
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.
It's a breaking change BTW. I think the author just wanted to have a case-insensitive comparison, so I would use http://docs.oracle.com/javase/6/docs/api/java/lang/String.html#equalsIgnoreCase(java.lang.String)
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.
For case-sensitive system i will be unable to use two variables different in registry.
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.
But i can accept such limitation. Then comparison may really makes sense.