You want to use Long if you allow the value to be null. Otherwise you
want to use long.
On 10/17/2013 01:17 PM, Mike Caspar wrote:
The app I am using needs to receive a *"long"* to provide to it's subclass.
For @DataboundConstructor and the privates I have a choice between Long and
long. I can use "long" but wanted to make sure it wasn't going to cause
problems elsewhere (or in the future).
* I could just guess one and hope it works out in the future.
* I could have just used int and translated in the app, but figured that
would
just eventually possibly lose people their settings during an upgrade.
* Long and long "act" similarly but there are some minor differences in
testing and error trapping.
If someone has a quick answer, that would be awesome!
If not, I'll start hunting through all the github repos to see if there is any
convention that's being used.
I did a search on the wiki first and can't find anything there.
Thanks for any guidance.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
