We are releasing the source for the flex-messaging-common.jar, not creating some dependency on a jar of unreleased sources. The source passed IP Clearance. We actually have lots of “new" source in 4.14, not just the flex-messaging-common sources: the FlatSpark sources are going out for the first time as well. Hopefully they will all pass review as will any other changes made to the source since 4.13.
-Alex On 12/15/14, 5:18 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >This now deserves it's own thread. Please create one before replying to >the >BlazeDS issue. > >Thanks, > >EdB > > > >On Tuesday, December 16, 2014, Justin Mclean <justinmcl...@me.com> wrote: > >> Hi, >> >> > We are releasing the required files as part of the SDK source package. >> >> There been several discussions on the general @ and elsewhere about >>this. >> eg [1]. I think some caution is needed here. >> >> Note Bertrand's email in that thread. The context here is unreleased >>code >> from a podling but it's not unreasonable to assume that it would apply >>to >> all unreleased code. >> >> "if another project release contains unreleased code from a podling, it >> might not be clean." >> >> And while not exactly the same situation here's something similar [2]. >> >> The relevant part being: >> "Until an official, non-incubation release of Thrift comes >> out (and thrift moves from incubation), the Apache Management will veto >> any redistribution of the thrift JARs; they aren't signed off as for >> public use." >> >> > This is the similar to what we’ve done with TLF for several releases >>now. >> >> Except that TLF was reviewed after the donation from Adobe. BlazeDS is >>yet >> to have a decent IP review or a release. >> >> Justin >> >> 1. http://apache.markmail.org/thread/us5d6ruj6lcfmy2p >> 2. >> >>http://mail-archives.apache.org/mod_mbox/hadoop-general/201012.mbox/%3C4C >>f63ed4.2000...@apache.org%3E > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
