This occurs if the network connection is interrupted or if curl fails downloading for any other reason.

Need to add a check for the zip integrity after downloading.

ZIP_OK=$(zip -T "$HOME/.gvm/archives/grails-2.0.4.zip" | grep 'OK')

If ZIP_OK is empty then, handle the condition.

Requires new dependency on zip command, so install.sh also needs to be updated.

In the following scenario after a fresh gvm install:

gvm use grails 2.1.1

...should just work, for maximum "wow" factor. i.e. without an explicit install. IMO install should not usually be needed.

I would expect "use" to prompt the user instead of complaining that 2.1.1 is not installed yet:

gvm use grails 2.1.1
Grails version 2.1.1 is not currently installed, would you like to install it now? (y, n)

That would rock

There seems to be a path issue on Windows with Cygwin. When I call the list command,

gvm list grails

See the following errors at the end of the output:

ls: cannot access /home/IE: No such file or directory
ls: cannot access User/.gvm/grails: No such file or directory

Then, neither the installed or usable grails versions have the proper highlight next to them.

The output is as follows:

$ gvm list grails
Groovy Version Manager 0.1
GVM server 0.1 on vertx 1.2.3.final

=== BROADCAST ==========================================
This application is currently in beta. If you experience
any problems then please raise an issue on GitHub at:
https://github.com/freshgroovy/gvm/issues

Only Grails is available in this beta release. Groovy,
Griffon and Gradle coming soon!
========================================================
ls: cannot access /home/IE: No such file or directory
ls: cannot access User/.gvm/grails: No such file or directory

--------------------------------------------------------
Available Grails Versions
--------------------------------------------------------

   1.3.7
   1.3.8
   1.3.9
   2.0.0
   2.0.1
   2.0.2
   2.0.3
   2.0.4
   2.1.0
   2.1.1
--------------------------------------------------------
* - installed
> - currently in use
--------------------------------------------------------

Cannot seem to download the grails 2.2.0.RC1 release, currently available on grails download archives

Try to install grails 1.3.4 via

gvm install grails 1.3.4

Get Stop! 1.3.4 is not a valid grails version.

Seems gvm only supports the grails versions held in Amazon S3, but not those in Codehaus.

http://grails.org/download/archive/Grails

Use mongo for persistence

Should allow basic tasks (such as the use command) to be performed without an internet connection.

The selfupdate command causes the script to overwrite itself with a new version. This causes bash to dump out the following to standard out.

/Users/omid/.gvm/bin/gvm: line 258: unexpected EOF while looking for matching `"'
/Users/omid/.gvm/bin/gvm: line 259: syntax error: unexpected end of file

Clean this up by writing standard out to /dev/null

Call gvm uninstall, without providing it a candidate name.

This seems to remove the .gvm directory and make everything not work anymore.

Command should check that a proper candidate is provided before deleting.

This may be a question of personal preference, but it's difficult to use gvm in scenarios where you want different versions active in different terminal windows/tabs. For example, I may be working with a Grails app that's 2.1.1 and a plugin that's 2.0.4. Switching version every time I switch between terminal windows between the app and the plugin is way too awkward.

I guess this is fundamental to the way gvm works, but it's almost a blocker for my workflow. I'll try to think of some solutions.

I'm finding it really annoying that the broadcast message is displayed every time I run a command. It's a huge amount of noise and particularly distracts from the commands that only have a line or two of output.

Can we show each broadcast message just once for a particular GVM installation?

It would be nice to have the option to share installations between all users of a machine (maybe with a user-specific symlink to the active version).

These two values are found throughout the scripts and need to be DRY. Possible solution is to serve the gvm, gvm-install.sh and install.sh as templates and replacing the values from one of the two:

• fetch them out of the datastore
• set them in a properties file

Here is rvm's output:

• To start using RVM you need to run source /Users/tomaslin/.rvm/scripts/rvm
  in all your open shell windows, in rare cases you need to reopen all shell windows.

Would be nice to have the same option in gvm rather than being told to open windows.

To install gvm on Ubuntu, I ran the following command:

curl -s beta.freshgroovy.org | bash 

to install gvm. This added

[[ -s "$HOME/.gvm/bin/gvm-init.sh" ]] && . "$HOME/.gvm/bin/gvm-init.sh"

to .profile. However, when I executed

gvm help

I got a "command not found" error. Once I read the updated .profile using

. .profile

everything worked fine, but ideally this should happen automatically (or at least the installation instructions should advise that this is necessary

As a Groovy developer, I often install development versions of Groovy locally.
It's usually the master branch of upcoming Groovy releases, etc.

It'd be nice if I could tell GVM to use my local installation as well, in addition to all the known release versions. For example:

gvm install local groovy 2.1.0-SNAPSHOT /dev/groovy/master/target/install

Or something like that. I'm sure you'll find a better command-line to use.

Currently on u2

It seems odd that I can't do gvm list grails without having first done gvm install grails. I should be able to check what versions are available before deciding which one to use.

The 'Report issues' and 'Issue lists' links still refer to old freshgroovy repository.

It seems that .profile is not ran by the default cygwin installation by default.

Need to call source .profile to get gvm running on cygwin.

I installed grails 2.1.1and grails 1.3.9. When I use grails 2.1.1 and execute

grails --version

It works fine, but when I switch to 1.3.9 this same command fails:

gvm@Office100:~$ grails --version
Welcome to Grails 1.3.9 - http://grails.org/
Licensed under Apache Standard License 2.0
Grails home is set to: /home/gvm/.gvm/grails/1.3.9

Base Directory: /home/gvm
Resolving dependencies...
Dependencies resolved in 1011ms.
Running pre-compiled script
Script 'Version' not found, did you mean:
   1) SetVersion
   2) GenerateController
   3) Interactive
   4) CreateFilters
   5) CreateController
Please make a selection or enter Q to quit: 

it's possible that

grails --version

also fails under "vanilla" grails 1.3.9, but I don't think so.

There are several issues here. First, running the tests produces a NullPointerException if GVM_DIR is not set. I had to look at test report to see the stack trace to identify which file was throwing the error in order to determine the ultimate cause of the error.

Second, it seems that nothing mentions that GVM_DIR needs to be set. And finally, I can't tell what it should be set to.

I'd like to contribute a simple current command to gvm with test, but I need to be able to run the tests to do that.

I would like to be able to make changes to my gvm source tree and then install those into the ~/.gvm directory via an install task. Useful for testing.

One thing I'm not sure about is whether to support something like revert or whether to rely on the developer switching to a working branch and doing the install again.

If a project was created with a different version of grails/gradle/griffon to the currently selected candidate, it would be nice to have a command that switches to the correct version of the appropriate candidate.

For more background, check out issue #32

The current output says:

Downloading: grails 1.3.7 from:

but does not show where it is being downloaded from. Should just remove the from: or actually specify a location

Installation should be as easy as downloading an install.sh and running it.

I'm getting a failure attempting to install Grails 2.2.0.RC1. Here's the output:

  % gvm install grails 2.2.0.RC1                                                                                                         !991
zsh: correct 'grails' to '.grails' [nyae]? n
Groovy enVironment Manager 0.5
GVM server 0.5 on vertx 1.2.3.final

=== BROADCAST ==========================================
This application is currently in beta.
Report issues: https://github.com/freshgroovy/gvm/issues
--------------------------------------------------------
Latest update:
Lots of bug fixes.
Issue list, latest fixes on top: http://bit.ly/SPcnrl
========================================================

Stop! 2.2.0.RC1 is not a valid grails version.

The Cucumber tests should verify that both the client and server are working as expected. At the moment, they're using a stub server implementation. Since I want to add a test for checking the behaviour of out-of-date versions of gvm and the implementation of that feature requires code changes on the server, we really need to be running against the server code.

I guess the issue here is the dependency on MongoDB, but I wonder whether it's possible to run the server app with a dummy mongo-persister busmod that we can initialise with duff data. Or we can have the Cuke tests require a running MongoDB instance, but that's probably a non-starter.

Maybe a regexp to search for gvm-init.sh on this file before may help.

what about using JSON, for future interoperability :)

gswitch has a nice feature where it selects the version to switch to based on your local Grails application. This is really nice when you have many Grails projects, as it saves you from inspecting application.properties just to type in the same version. With this feature you simply type gswitch and your done:

$ gswitch 
Local Grails Application is using version 2.0.3
Setting to version 2.0.3... done.

Would be nice to have a similar feature in gvm, like gvm use grails.
Or automatically switching to correct version when changing directory to a Grails application, like rvm has with its .rvmrc:

$ cd octopress/
Using /Users/ronny/.rvm/gems/ruby-1.9.3-p125

Other candidates could have this feature as well, if it makes sense for that particular candidate.

Call gvm install gradle

Get an amazon application error html page in the output stream.

When entering:
gvm uninstall grails

All versions installed up to this point will be deleted.

When I have a grails version installed from gvm, the initial install script ( curl -s beta.gvmtool.net | bash ) will complain that grails is already installed and fail to continue.

Should probably ignore grails versions within .gvm directories or detect that gvm is already installed.

Checking for previous versions of Grails...
Grails found.

======================================================================================================
 You already have Grails installed. This will cause problems with GVM.
 Grails was found at:

 /Users/tomaslin/.gvm/grails/current/bin/grails

 Please remove it from your PATH and restart.
======================================================================================================

If my gvm version is out of date I get the following message even if the command I issued was gvm selfupdate:

===============================================
Your version of GVM is out of date!
-----------------------------------------------

Current version installed : 0.7
Latest available version  : 0.8

This upgrade can be performed by:

    gvm selfupdate

===============================================

Use the gradle git plugin to deploy to the heroku test and prod servers.

When I use gvm to install grails, always see

$ grails help
cygpath: can't convert empty path

| Loading Grails 2.1.1
| Configuring classpath
| Downloading: C:\cygwin\home\IE User\.gvm\grails\2.1.1\lib\org.springframework.                                                                           uaa\org.springframework.uaa.client\ivy-1.0.1.RELEASE.xml
| Downloading: C:\cygwin\home\IE User\.gvm\grails\2.1.1\lib\com.google.protobuf\ 

seems that somehow it inserts and incorrect path during installation somewhere

Currently, the bash install script checks for a grails version and fails if grails has already been installed.

However, this makes it impossible to use gvm to manage only groovy versions, for example.

The check for a grails version being installed should probably be moved to the installation of the candidate, so that an error occurs only when the user tries to use gvm to manage grails.

Seeing this output:

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
85 46.2M 85 39.6M 0 0 539k 0 0:01:27 0:01:15 0:00:12 601k

See an empty line in curl that seems to fetch nothing.

Make the help text on gvm help a bit more verbose:
Have each command on it 's own line with a short description (also with possible command parameters)

Unzip is not installed by default in cygwin.

When trying to install a new grails version, you get

Downloading: grails 1.3.8 from:


  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 46.2M  100 46.2M    0     0   510k      0  0:01:32  0:01:32 --:--:-- 1370k

Installing: grails 1.3.8
/home/IE User/.gvm/bin/gvm: line 162: unzip: command not found
mv: cannot stat `/tmp/grails-1.3.8': No such file or directory
Done installing!