Mavenize Walkaround

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to build and run the wave server with eclipse plugin.
2. Read build.xml
3. Want maven to control build processes.

The gwt+appengine maven archetype has more control than ant builds, and support 
for running the gwt plugin, generating rpcs or css classes, and most 
importantly, dependency management.

Perhaps there is an easier way to get a live copy up and running, but I do know 
that ant converts easily to maven, and it can make it a lot easier to pull in 
the code you need without the piles that you don't.

Maven is by Apache, so it could be possible to get some help mavenizing the 
wave protocol, to keep up on the library core without pulling in all the jetty 
dependencies =}

Original issue reported on code.google.com by internetparty@wetheinter.net on 2 Apr 2012 at 9:29

[GoogleCodeExporter]

Is there a general list of what abstract parts of the protocol need to be 
imported, and which are to be left out, I could try putting an archetype 
together and throwing it on github.  Is the wave protocol source in 
third_party_src a modified trunk of wave protocol, or just a frozen copy used 
to keep dependencies in line?

Are there repackaging license restrictions on some of the jars needed?

When I tried checking out the trunk of wave protocol and using it instead of 
the jar'd copies, it really didn't work very well.  I'm sure it can be juggled 
into position, but if that juggling is done in maven, at least other developers 
can check it out and start patching without jar-management nightmares... 

...And I'm cool with sh update scripts, but a maven build script is platform 
independent and future-friendly.  It could make working on multiple branches a 
lot easier, since each branch can exist as a source folder that can be turned 
on or off to test. 

Original comment by internetparty@wetheinter.net on 2 Apr 2012 at 9:54

[GoogleCodeExporter]

This has been brought up several times in the mailing list so you can easily 
find previous discussions about this.

I had even started working on this but I believe I never got it fully working.
You can see what's done here: 
https://github.com/nelsonsilva/wave-protocol/tree/maven/tools/maven
(It's an older version of the code base)

Original comment by nelson.s...@gmail.com on 2 Apr 2012 at 10:03

[GoogleCodeExporter]

I have no objections to mavenizing walkaround if it helps you and you are 
willing to do the work.  The first step would be to understand the script 
get-third-party-deps; that should answer most of your questions.

If mavenizing walkaround also requires mavenizing Apache Wave, you might get 
objections from there, though.

Original comment by oh...@google.com on 2 Apr 2012 at 11:16

[GoogleCodeExporter]

Ahh, yes; I sort of assumed as much.  I'm putting together a PlayN project, 
which is heavily mavenized, which I intend to use as my universal frontend for 
all platforms, and then drop the wave server into the browser editor platform.  
It may take a while to get to the backend, but it's on my list, so mavenizing 
of walkaround will have to happen eventually, even if just as a dependency in 
the web module. =}

I am definitely willing to do the work, but between my day job and my frontend, 
it could be a while.  If anyone else on the list is interested, I am down for 
collaboration.

In regards to apache wave, I'm not actually sure how many shared dependencies 
there are, or if they will be getting updates; if the shared code is relatively 
stable, it wouldn't be that hard to just mavenize the bits needed for 
walkaround and leave the apache project to their own devices.

Thank you! 

Original comment by internetparty@wetheinter.net on 19 Apr 2012 at 9:32

[GoogleCodeExporter]

You have your work pretty much completed at https://github.com/pires/wave

Original comment by pjpi...@gmail.com on 30 May 2012 at 3:54

[GoogleCodeExporter]

See also https://github.com/goodow/wave and https://github.com/goodow/walkaround

Original comment by i...@goodow.com on 12 Sep 2012 at 12:50