Grails

SNAPSHOT plugins cause grails to fail when no internet connection available

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-M1
  • Fix Version/s: 2.0-RC1
  • Component/s: Build System
  • Labels:
    None

Description

If I add spock:0.6-SNAPSHOT plugin to my grails app, whenever I'm offline, running "grails" fails as it can't resolve the plugin. It's in my local Ivy cache of course (from previous times I ran grails when I was online) but the resolution logic seems to insist that SNAPSHOT items must come from t'Internet every time. Ideally it would fall back to the locally cached copy when offline.

Further to that, maybe performance in all situations can be improved by not going to the internet every time? Personally I would prefer it to never go the internet unless it didn't have a cached copy locally yet, or I ran an explicit update-snapshot-dependencies command to tell it to get the latest as a one-off. Having your dependencies potentially changing underneath you is a variable most people surely don't want whilst developing their own code.

Issue Links

relates to

New Feature - A new feature of the product, which has yet to be developed. GRAILS-1559 Add an offline mode

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

Activity

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

Can GRAILS-1559 be reopened?

Show
Raviteja added a comment - Can GRAILS-1559 be reopened?
Hide
Permalink
Peter Ledbrook added a comment -

Can you please try Grails 2.0.0.RC1 or later with the --offline option? That should allow you to run Grails without an internet connection. There is also a configuration setting, but I can't remember what it is off the top of my head.

Show
Peter Ledbrook added a comment - Can you please try Grails 2.0.0.RC1 or later with the --offline option? That should allow you to run Grails without an internet connection. There is also a configuration setting, but I can't remember what it is off the top of my head.
Hide
Permalink
Sam Carr added a comment -

The --offline option for grails seem to do the trick for me at least in rudimentary testing - i.e. I can launch grails into interactive mode with it, whereas I can't without the --offline flag (dependency resolution fails for Spock SNAPSHOT as ever).

I'd still prefer the default behaviour to be not to update snapshots ever unless they haven't been fetched at all yet, or when explicitly invoked to do so. Alternatively some more clever logic that issues only a one-line warning when resolution fails for SNAPSHOTS but carries on and uses the previous local copy if it has one. It should probably only even try to fetch an update once daily ata maximum otherwise a great deal of time is wasted checking and rechecking the internet and slowing down grails startup enormously.

I am concerned that people will be put off Grails otherwise (even with the new --offline flag, which they probably won't know about) as they stumble through this irritation. My hair is now slowly growing back and I have returned to Grails after a absence of many months and I'm very glad to see this aspect is being improved.

I understand that the planned significant changes to the Grails project build system might completely upend this conversation anyway, but that it will be a good year or more before they are in place.

Show
Sam Carr added a comment - The --offline option for grails seem to do the trick for me at least in rudimentary testing - i.e. I can launch grails into interactive mode with it, whereas I can't without the --offline flag (dependency resolution fails for Spock SNAPSHOT as ever). I'd still prefer the default behaviour to be not to update snapshots ever unless they haven't been fetched at all yet, or when explicitly invoked to do so. Alternatively some more clever logic that issues only a one-line warning when resolution fails for SNAPSHOTS but carries on and uses the previous local copy if it has one. It should probably only even try to fetch an update once daily ata maximum otherwise a great deal of time is wasted checking and rechecking the internet and slowing down grails startup enormously. I am concerned that people will be put off Grails otherwise (even with the new --offline flag, which they probably won't know about) as they stumble through this irritation. My hair is now slowly growing back and I have returned to Grails after a absence of many months and I'm very glad to see this aspect is being improved. I understand that the planned significant changes to the Grails project build system might completely upend this conversation anyway, but that it will be a good year or more before they are in place.
Hide
Permalink
Graeme Rocher added a comment -

Thanks for the feedback.. closing

Show
Graeme Rocher added a comment - Thanks for the feedback.. closing
Hide
Permalink
Peter Ledbrook added a comment -

Sam: you can also set grails.offline.mode = true in your ~/.grails/settings.groovy file. This will default to offline mode. Not sure whether it can be overridden with the --force-resolve option though.

Show
Peter Ledbrook added a comment - Sam: you can also set grails.offline.mode = true in your ~/.grails/settings.groovy file. This will default to offline mode. Not sure whether it can be overridden with the --force-resolve option though.

People

  • Assignee:
    Unassigned
    Reporter:
    Sam Carr
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: