groovy

groovy -version could show more information about the JVM

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.8.5, 2.0-beta-2
  • Component/s: groovy-jdk
  • Labels:
    None
  • Number of attachments :
    0

Description

Occasionally, bugs or peculiarities only show themselves on certain JVMs (OpenJDK, etc)

It's often hard to find out exactly which JVM someone is running on their OS

Adding this information into the groovy -version string would be really useful

Something like:

Groovy Version: 1.8.4 JVM: 1.6.0_29 Vendor: Apple Inc. OS: Mac OS X

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Fix added a comment - - edited

well 64 or 32 bits is also good as it can greatly influence the vm behavior

Show
Fix added a comment - - edited well 64 or 32 bits is also good as it can greatly influence the vm behavior
Hide
Permalink
Roshan Dawrani added a comment -

vm vendor and os name are now included in the output.

Show
Roshan Dawrani added a comment - vm vendor and os name are now included in the output.
Hide
Permalink
Paul King added a comment -

I wonder whether the vm name would also be useful, e.g. knowing the difference between these two is often useful:

java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.name=Java HotSpot(TM) Client VM

Though perhaps it is getting too long and such information might be produce with some kind of verbose flag?

Show
Paul King added a comment - I wonder whether the vm name would also be useful, e.g. knowing the difference between these two is often useful: java.vm.name=Java HotSpot(TM) 64-Bit Server VM java.vm.name=Java HotSpot(TM) Client VM Though perhaps it is getting too long and such information might be produce with some kind of verbose flag?
Hide
Permalink
Roshan Dawrani added a comment -

It is also quite easy enough to run "System.properties.each

{println it}

" on groovy command line and have a peek at all properties of interest, whenever needed.

Otherwise, instead of "groovy -v", we might be needing "groovy -v1 -v2", where -v1 is for version and -v2 is for verbosity.

Show
Roshan Dawrani added a comment - It is also quite easy enough to run "System.properties.each {println it} " on groovy command line and have a peek at all properties of interest, whenever needed. Otherwise, instead of "groovy -v", we might be needing "groovy -v1 -v2", where -v1 is for version and -v2 is for verbosity.
Hide
Permalink
blackdrag blackdrag added a comment -

another option would be -vv with -v for being verbose and -vv for being more verbose.

Show
blackdrag blackdrag added a comment - another option would be -vv with -v for being verbose and -vv for being more verbose.

People

  • Assignee:
    Roshan Dawrani
    Reporter:
    Tim Yates
Vote (2)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: