History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: GRAILS-1724
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Graeme Rocher
Reporter: Marc Palmer
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Grails

dependsOn map on plugins is too strict with version numbers

Created: 19/Oct/07 12:08 PM   Updated: 30/Nov/07 05:06 AM
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0-RC2

Time Tracking:
Not Specified


 Description  « Hide
We have a problem but I don't know what the solution is. Specifying a specific version in dependsOn is a serious problem because there is no concept of "anything newer than X" so if for example you are writing a plugin that can work with 1.0-RC1-SNAPSHOT but you're installing the plugin into a 1.0-RC2-SNAPSHOT application, it will fail to load.

This is a serious limitation but without enforcing some kind of numbering scheme I don't know how we can do it. Compare numerically up to the first non-numeric char? I think this was mooted before.

It needs to be sorted out before 1.0 final if we want the plugin marketplace to work.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Graeme Rocher - 19/Oct/07 02:49 PM
Maybe we should just support something like:

dependsOn = [core:"1.0".."*"]

With wild cards for the upper end


Graeme Rocher - 30/Nov/07 05:06 AM
I've added support for version expressions in the dependsOn String so you can do:
def dependsOn = [core:"0.6 > 1.0"]

or

def dependsOn = [core:"0.6 > *"]

or

def dependsOn = [core:"* > 1.0"]