Details
-
Type:
Bug
-
Status:
Reopened
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 1.4-M1
-
Fix Version/s: 2.0-RC1
-
Component/s: Build System
-
Labels:None
Description
This is a clone of this issue which has been marked resolved in 1.4-M1, but I'm using this version and I still find that SNAPSHOT dependencies are not updated. I have the following dependency configured in BuildConfig.groovy
def esdVersion = '1.0-SNAPSHOT' compile("com.example:domain:$esdVersion", "com.example:managers:$esdVersion") { excludes 'commons-io' changing = true // should force Grails to check Maven repo for update instead of retrieving old version from Ivy cache }
If I rebuild the dependency (using Maven), and restart the Grails app, it loads the version of the dependency from the Ivy cache. The only way I can get the Grails app to pick up the newer version in the Maven repo is to delete the dependency from the Ivy cache.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Git Commits
Donal Murtagh
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Affects Version/s | 1.4-M1 [ 11040 ] | |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Component/s | Configuration [ 10415 ] | |
| Summary | CLONE - 'changing' attribute not honored in BuildConfig dependency resolution | 'changing' attribute not honored in BuildConfig dependency resolution |
| Affects Version/s | 1.3.7 [ 11039 ] | |
| Description |
The development build of our grails projects has some snapshot dependencies. We had been using Ivy's 'changing' attribute to handle this: compile ('com.me:mydep:1.0.0-0-SNAPSHOT') { changing: true } This would keep our build in sync with the latest snapshot versions of our dependencies. Since upgrading to Grails 1.3.7, this mechanism seems to have been broken - our snapshots are not getting pulled from our Nexus repo even though they are newer than what is in the local Ivy cache. http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency.html documents the 'changing' attribute. |
This is a clone of an issue which has been marked resolved in 1.4-M1, but I'm using this version and I still find that SNAPSHOT dependencies are not updated. I have the following dependency configured in BuildConfig.groovy {code} def esdVersion = '1.0-SNAPSHOT' compile("com.dailydate:domain:$esdVersion", "com.dailydate:managers:$esdVersion") { excludes 'commons-io' changing = true // should force Grails to check Maven repo for update instead of retrieving old version from Ivy cache } {code} If I rebuild the dependency (using Maven), and restart the Grails app, it loads the version of the dependency from the Ivy cache. The only way I can get the Grails app to pick up the newer version in the Maven repo is to delete the dependency from the Ivy cache. |
| Component/s | Build System [ 10680 ] |
Donal Murtagh
made changes -
| Description |
This is a clone of an issue which has been marked resolved in 1.4-M1, but I'm using this version and I still find that SNAPSHOT dependencies are not updated. I have the following dependency configured in BuildConfig.groovy {code} def esdVersion = '1.0-SNAPSHOT' compile("com.dailydate:domain:$esdVersion", "com.dailydate:managers:$esdVersion") { excludes 'commons-io' changing = true // should force Grails to check Maven repo for update instead of retrieving old version from Ivy cache } {code} If I rebuild the dependency (using Maven), and restart the Grails app, it loads the version of the dependency from the Ivy cache. The only way I can get the Grails app to pick up the newer version in the Maven repo is to delete the dependency from the Ivy cache. |
This is a clone of [this issue|http://jira.grails.org/browse/GRAILS-7427] which has been marked resolved in 1.4-M1, but I'm using this version and I still find that SNAPSHOT dependencies are not updated. I have the following dependency configured in BuildConfig.groovy {code} def esdVersion = '1.0-SNAPSHOT' compile("com.dailydate:domain:$esdVersion", "com.dailydate:managers:$esdVersion") { excludes 'commons-io' changing = true // should force Grails to check Maven repo for update instead of retrieving old version from Ivy cache } {code} If I rebuild the dependency (using Maven), and restart the Grails app, it loads the version of the dependency from the Ivy cache. The only way I can get the Grails app to pick up the newer version in the Maven repo is to delete the dependency from the Ivy cache. |
Donal Murtagh
made changes -
| Summary | 'changing' attribute not honored in BuildConfig dependency resolution | updates to changing = true depencies are ignored |
Donal Murtagh
made changes -
| Summary | updates to changing = true depencies are ignored | updates to changing = true dependencies are ignored |
Graeme Rocher
made changes -
| Fix Version/s | 1.4-M1 [ 11040 ] | |
| Fix Version/s | 2.0-M2 [ 12805 ] |
Burt Beckwith
made changes -
| Workflow | jira [ 39966 ] | Grails [ 41566 ] |
Burt Beckwith
made changes -
| Workflow | Grails [ 41566 ] | Copy of Grails [ 48988 ] |
Burt Beckwith
made changes -
| Workflow | Copy of Grails [ 48988 ] | Grails [ 56398 ] |
Donal Murtagh
made changes -
| Status | Open [ 1 ] | Edit [ 10000 ] |
| Description |
This is a clone of [this issue|http://jira.grails.org/browse/GRAILS-7427] which has been marked resolved in 1.4-M1, but I'm using this version and I still find that SNAPSHOT dependencies are not updated. I have the following dependency configured in BuildConfig.groovy {code} def esdVersion = '1.0-SNAPSHOT' compile("com.dailydate:domain:$esdVersion", "com.dailydate:managers:$esdVersion") { excludes 'commons-io' changing = true // should force Grails to check Maven repo for update instead of retrieving old version from Ivy cache } {code} If I rebuild the dependency (using Maven), and restart the Grails app, it loads the version of the dependency from the Ivy cache. The only way I can get the Grails app to pick up the newer version in the Maven repo is to delete the dependency from the Ivy cache. |
This is a clone of [this issue|http://jira.grails.org/browse/GRAILS-7427] which has been marked resolved in 1.4-M1, but I'm using this version and I still find that SNAPSHOT dependencies are not updated. I have the following dependency configured in BuildConfig.groovy {code} def esdVersion = '1.0-SNAPSHOT' compile("com.example:domain:$esdVersion", "com.example:managers:$esdVersion") { excludes 'commons-io' changing = true // should force Grails to check Maven repo for update instead of retrieving old version from Ivy cache } {code} If I rebuild the dependency (using Maven), and restart the Grails app, it loads the version of the dependency from the Ivy cache. The only way I can get the Grails app to pick up the newer version in the Maven repo is to delete the dependency from the Ivy cache. |
Burt Beckwith
made changes -
| Workflow | Grails [ 56398 ] | Grails2 [ 63994 ] |
Raviteja
made changes -
| Status | Edit [ 10000 ] | Open [ 1 ] |
Graeme Rocher
made changes -
| Fix Version/s | 2.0-RC1 [ 12803 ] | |
| Fix Version/s | 2.0-M2 [ 12805 ] |
Luke Daley
made changes -
| Assignee | Luke Daley [ ldaley ] |
Luke Daley
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Luke Daley
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
Burt Beckwith
made changes -
| Workflow | Grails2 [ 63994 ] | jira [ 71457 ] |
Burt Beckwith
made changes -
| Workflow | jira [ 71457 ] | Grails2 [ 79900 ] |
Peter Ledbrook
made changes -
| Last Reviewed | 01/Jan/10 |
Peter Ledbrook
made changes -
| Workflow | Grails2 [ 79900 ] | jira [ 88705 ] |
Peter Ledbrook
made changes -
| Workflow | jira [ 88705 ] | Grails2 [ 96866 ] |
Luke Daley
made changes -
| Assignee | Luke Daley [ ldaley ] |
Graeme Rocher
made changes -
| Assignee | Graeme Rocher [ graemerocher ] |