Skip to content
This repository has been archived by the owner on Aug 25, 2020. It is now read-only.

Use version ranges for third-party dependencies #116

Closed
danbim opened this issue Dec 29, 2011 · 1 comment
Closed

Use version ranges for third-party dependencies #116

danbim opened this issue Dec 29, 2011 · 1 comment
Labels
Task

Comments

@danbim
Copy link
Member

danbim commented Dec 29, 2011

Currently, whenever a third-party library used increases its minor version number (such as netty goes from 3.2.3 to 3.2.4) and we use this library in Testbed Runtime and other projects that TR depends on we have to change the version number in all these projects. Therefore we should change the dependency definitions in such a way that minor version increments are automatically used.
@danbim
Copy link
Member Author

danbim commented Aug 5, 2012

Outdated. Closing...

@danbim danbim closed this as completed Aug 5, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danbim