Oh, my misunderstanding then. If that's the case, then there is one technicality of the apache release process blocking the release (distributing dependencies alongside source), although not a tough one. I'll file a Jira and reflect it at the project incubation status page.
regards, juan pablo On Wed, Jul 11, 2012 at 1:31 PM, Jukka Zitting <jukka.zitt...@gmail.com>wrote: > Hi, > > On Tue, Jul 10, 2012 at 11:03 PM, Juan Pablo Santos Rodríguez > <juanpablo.san...@gmail.com> wrote: > > Regarding the binary dependencies. Wasn't the discussion on general@more > > focused on (or raised because of) transitive dependencies which were > > brought into the build and not being AL-compatible? > > No, all the dependencies discussed were compliant with Apache > policies. The problem was about having binaries included in the source > archive. > > > Also, the build is Ant based, so we need them to be there in order to be > > able to build. > > The proposed solution for this case was to put the dependencies in a > separate -deps archive, that can be combined with the source release > to make it buildable. The build script can also automatically download > such separate binary dependencies. > > BR, > > Jukka Zitting > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
