Stan, I am not surprised. Sinan changed the layout of the build directory in 2.0 and that is probably what is screwing faxien. You can probably point faxien directly to the built apps (via a path) and it will handle things correctly though. Its more work but is doable.
Eric On Tue, Mar 13, 2012 at 5:15 PM, Stan McQueen <[email protected]> wrote: > Sorry, I guess I spoke too soon! Apparently I had a _build/development > directory left over from a prior sinan 1.0.1 build. After clearing it > out and then building with the new sinan, I am still not able to > publish with faxien. > > Stan > > On Tue, Mar 13, 2012 at 4:12 PM, Stan McQueen <[email protected]> wrote: >> I may have this working, now. I found the documentation on specifying >> dependencies in sinan and that appears to solve my problem. If there >> is more that I should know about this, I would appreciate the >> information. >> >> Thanks, >> Stan >> >> On Tue, Mar 13, 2012 at 2:58 PM, Stan McQueen <[email protected]> wrote: >>> That works; thanks very much. Now my problem is as follows: >>> >>> We're currently building with sinan, publishing to a portius repo with >>> faxien, and finally using faxien to install new releases on our test >>> and production servers. The new sinan doesn't seem to produce a >>> configuration that faxien understands. Previously, i could build a >>> release that contained a number of sub-projects, then "faxien publish" >>> would publish the appropriate combination of libs and releases to >>> portius. This process has been working very well for the 1.0 release >>> of our new servers. >>> >>> Is there an erlware replacement for this build-publish-deploy process? >>> >>> Stan >>> >>> On Mon, Mar 12, 2012 at 4:18 PM, Eric Merritt <[email protected]> >>> wrote: >>>> Stan, >>>> >>>> From sinan 1.0.1 to the 2.0.0 and beyond the main user visible things >>>> that changed is the sinan config. Mostly this was a move towards a >>>> term format for the config and more flexible configuration. If you >>>> where not using the config before you should be able to nuke the old >>>> sinan config and have the new sinan just work. >>>> >>>> Obviously, that doesn't seem to be happening here but without seeing >>>> any of your errors its hard to tell what is actually broken. >>>> >>>> Eric >>>> >>>> >>>> On Mon, Mar 12, 2012 at 5:13 PM, Stan McQueen <[email protected]> >>>> wrote: >>>>> Is there a way to convert old sinan 1.0.1 projects to the new sinan? >>>>> When I try to build (via "sinan dist") my old projects, I get various >>>>> errors. We have an extensive server architecture that is being built >>>>> with sinan and faxien and after installing Erlang R15, sinan 1.0.1 >>>>> will no longer run. >>>>> >>>>> Stan >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "erlware-dev" group. >>>>> To post to this group, send email to [email protected]. >>>>> To unsubscribe from this group, send email to >>>>> [email protected]. >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/erlware-dev?hl=en. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "erlware-dev" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/erlware-dev?hl=en. >>>> > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
