Berin:
I was under the impression that James has started using Merlin. I guess I was wrong.
Niclas:
Accordig to Steve, the CVS HEAD of James is done with migration to Merlin. Release pending.
Stephen uses Merlin, and I am happy for his continue support and testing (in fact, I am hoping that he'll get time this weekend to commit the latest Avalon packages into our build system).
There are no direct dependencies between the recently released distributions and James. However, James has dependencies on cornerstone components and these components have dependencies of excalibur components - notably the excalibur-event package from the cornerstone-threads package (which was bumped to 1.1). This means that we should be bumping the cornerstone-threads version, and testing this against James under the current Phoenix dist before committing an updated corenerstone jar into the James CVS. I.e. it's not a this weekend exercise.
However, all of our releases use Phoenix. I expect our next tests to still
be using Phoenix. I expect that our next release will still use Phoenix,
but if we can, I am thinking that we could put out an alternative packaging
using Merlin.
I figure there is some work ahead in updating the builds to handle the separation of james with respect to its deployment target. If I get time in the coming weeks (the next two are already looking "heavy") I could start thinking about how we handle this. BTW - are there any additional thoughts about migrating to a maven based build as this would eliminate the need to registered artifacts in the James CVS?
Then if we get the right feedback from the user community, we can decide to stop providing a Phoenix packaging, but I am far from predicting that event. We're not in the business of disenfranchising our user community, and we don't know all of what they are doing, including in their own custom code.
Two comments here - firstly, I'm running James day in and day out relative to a reasonably simple configuration using a file system based datastore. I have not deployed james using a database. My only concern is that as we move forward on this someone it would be good to get someone from James to head up the James/Merlin testing and packaging side of things. Secondly - the Phoenix to Merlin question should in principal not impact user with respect to custom code because Phoenix does not support cross-app integration. If a user of James is doing something with other custom apps in Phoenix they will be interacting on James assigned ports - which means that this will independent of the James deployment platform.
Perhaps more of an immediate concern is some good migration documents (script changes, etc.) for supporting the transition from Phoenix to Merlin.
Stephen.
--- Noel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
