> > Do the non-Merlin-specific packages work with the released version of
> > Phoenix? For example, can they be dropped into the James MAIN branch,
> > and that continue to work properly?
> The non-Merlin specific packages have been build and tested against all
> of the cornerstone candidates and validated against JAMES MAIN.
To be clear: using Phoenix?
> A single conflict exist relative to the James reference to content
> that was deprecated in excalibur-thread which is handled in james
> with a special "deprecation handler". Removal of the handler
> results in a clean james build and deployment under the Merlin platform.
Details?
> This message is sent to you via James backed by the entire candidate
> suite (framework, excalibur, util, logging, repository, meta, merlin).
In the context of my inquiry, I couldn't care less whether Merlin even
compiles. We, James, are likely going to want to put out the next release
after 2.2 using the merged code, and I want to make sure that the released
version of Phoenix, which is what James uses, works with these new packages.
> For reference - we can setup a deployment model whereby james runs from
> a remote url, qualified by a single local overriding configuration
> (passwords and other sensitive or site specific content). If your
> interested I would more happy to provide the block model and sample
> configuration.
After the branch merger, and after I'm satisfied that we can put out new
releases based upon Phoenix, I'll be perfectly happy to look at optional
Merlin deployment.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
