-
Notifications
You must be signed in to change notification settings - Fork 19
Update lfetool to use LFE 0.9.0 #111
Comments
I'm still traveling, but am trying to get things with lfetool to a stable state. This will probably mean fixing the current lfetool to explicitly use 0.8.0. [See footnote 1] Here's what needs to be done:
I will create (or update) tickets for these. Footnotes [1] Thanks to the way that rebar handles (or doesn't handle) multiple versions of the same project, to support 0.9.0, I will need to update all projects that lfetool uses as dependencies when it creates skeleton projects. [2] This is necessary to support older releases of lfetool that are still in use, which depend upon the master branch being where it currently is |
Oh, I meant to also add the work-around until the bug is fixed:
|
I've created the following related tickets for these issues:
|
I'm going to rename this ticket from "LFE master branch has switched to 0.9.0" to what needs to be done, i.e., "Update lfetool to use LFE 0.9.0" |
@oubiwann up on this, any updates / ETAs ? |
The lfetool dev-1 branch is using LFE v0.9.0. Once the 1.4 milestone is complete, this (dev-1) will get merged to stable. No ETA on completing the milestone right now, but I myself have been using lfe from the dev-1 branch ... |
@pigmej I'm going to try to release 0.9.0 support today, if I can get all the necessary tasks accomplished. Outstanding issues I will move to a new 1.5 milestone. 1.5 will support LFE v0.10.0, which I also hope to get out very soon. |
Is it possible for lfetool to get the latest commit on the master branch Note I don't know if this is possible, Robert On 4 January 2015 at 21:18, Duncan McGreggor notifications@github.com
|
I've just released lfetool 1.4.0 which has LFE 0.9.0 support. Am getting ready to set up 1.5.0 milestone which will support 0.10.0-dev LFE. |
On Sun, Jan 4, 2015 at 3:28 PM, Robert Virding notifications@github.com
Using non-versioned repos by default can get a bit messy, strange, and Explicit version numbers is the fix for this. However, as you and other have noticed, this locks projects into very Working on the LFE-in-Docker project was absolutely awful for that one
That would definitely be better. There are ways we might be able to do this If they fixed this issue, much of the pain would go away: Then users could just update their project rebar.config to the versions But, that's not fixed, so we have to work with what we've got :-/
There are a couple of things that come to mind ... but I think we'd have to:
I'm not sure if this can be done within the confines of rebar's current I'll ponder it some more... |
I am going to close this issue (since 0.9.0 support is now released); let's continue the conversation about fixing the version-pinning problem in issue #135, "Working with versioned deps can be a nightmare". |
The LFE branch on github.com/rvirding/lfe has switched to 0.9.0 and creating a new project with
lfetool new service blah
fails on the dependency check forltest
("0.8.0" expected, "0.9.0" found).The text was updated successfully, but these errors were encountered: