robert burrell donkin ha scritto: > On 7/16/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: >> robert burrell donkin ha scritto: >> > On 7/16/07, Bernd Fondermann <[EMAIL PROTECTED]> wrote: >> >> Bernd Fondermann wrote: >> >> > ATM, we have to translate james-assembly.xml into Spring beans >> >> > definition. I want to reuse james-assembly.xml in Spring by >> writing a >> >> > "mapper bean factory". Switching between deployments would be rather >> >> > easy then. >> >> >> >> The very first step is committed. >> > >> > cool :-) >> > >> > maybe we should think about a plan for cutting milestones...? >> > >> > - robert >> >> What are you thinking about? > > if some measure of support for spring were patched into trunk then > this might justify a milestone > > - robert
IMHO it is not spring support to justify a milestone or not. It is a cool, long awaited feature, for sure (and kudos to Bernd for this) but Spring support will be only one more of the *127* bugs fixes/features we already have in trunk: https://issues.apache.org/jira/browse/JAMES?report=com.atlassian.jira.plugin.system.project:roadmap-panel My question was about the plan details: I was curious about how do you propose to manage the milestone cut. While I'm here, I've a doubt: is there any limitation in packaging an early access version of javamail in a official release (even if it is only a milestone ?). I remember in past the SUN "ea" releases had a special license (that wouldn't have allowed a release), but now in the jar LICENSE file I can't find any pointer but a standard CDDL. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
