Thanks for your enthusiasm Steve. Some responses below: On 29 July 2010 13:04, Steve Baker <[email protected]> wrote:
> On Jul 29, 12:03 pm, Alex North <[email protected]> wrote: > > Thus I'd like to announce a new repository in the wave protocol > project: > > That is great news. It would be great if this was also used as an > opportunity to get binary jar files out of the source control. Also > since you're prepared to work through this disruptive process it would > be a shame if you got to the end of it and still didn't fully cater > for an ecosystem as large as Maven: > http://jarvana.com/jarvana/info/repository_statistics > > To this end I've put together a pom.xml to provide maven builds for > wave-protocol-libraries. I'm more than happy to do what it takes to > make this a supported build system for wave-protocol-libraries. > I'm going to discuss this with the rest of the team. I'm not greatly familiar with either ant or maven, but a decision I'm fairly confident about is that we don't want the overhead of supporting two different build systems. It's fantastic that you're willing to help us get started but the fact remains that having two different builds will add continued overhead to making changes. > > The only things missing to get a full build appears to be these packages: > org.waveprotocol.wave.client.editor.constants > org.waveprotocol.wave.client.editor.content.paragraph.constants > Oops, looks like I missed quite a few things from the initial code drop. We're sorting them all out now. > > Could you please consider not including the following packages in > wave-protocol-libraries? > org.waveprotocol.wave.crypto > org.waveprotocol.wave.federation.Proto > org.waveprotocol.wave.federation > org.waveprotocol.wave.federation.xmpp > > The reasoning would be as follows: > - these are self-contained packages concerned with server<->server > transport and federation > - org.waveprotocol.wave.federation.xmpp adds many jar dependencies, > including a custom-patched jar that exists in no public repository and > is no longer maintained by upstream (whack/xmpp) > - the bulk of wave-protocol-libraries has minimal dependencies and > compiles to GWT > > These packages could stay in fedone-server for now, or go into their > own wave-protocol-federation project. (Likewise, a > wave-protocol-websockets project could be created for client<->server > transport) > We're going to make the build more modular, perhaps with a jar per top-level package, which will help the self-contained packages stay self-contained and reduce the overhead of using any one. I'll look into the individual ones you mention, but if they're useful outside any one application then I suspect libraries is the right place for them. Federation-related libraries still need sharing. I'll see if something can be done about that unmaintained jar, too. Cheers, Alex -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
