Couldn't we add a shell script to install the dependencies in the "tools" directory ?

This would make it easier for others with the same issues.

On 24-03-2011 11:45, Vicente J. Ruiz Jurado wrote:
El 23/03/11 19:26, Nelson Silva escribió:
Well, there doesn't seem to be much interest in this...

Vicente, how did you deploy the dependencies to your repo ?
mvn deploy:deploy-file

Did you
create a pom.xml for :

<groupId>org.waveprotocol.box</groupId>
<artifactId>wave</artifactId>
<version>0.3-SNAPSHOT</version>
<packaging>jar</packaging>

or did you simply install all the deps in the repo and added them all to
your project ?
I do the two things. As I'm patching WIAB because of #235, for me it's
more easy to generate an unique (and unofficial) server jar only for
testing. But when I have something usable I deploy all the jar in our repo.

It seems to me we're basically facing the same issues, just caught up
with your patch to facilitate the registration of other servlets and the
injection of WIAB instances in other projects.
Perhaps you should create a wiki page for these things...
Yes, we are commenting a proposal of patch:
http://codereview.waveprotocol.org/552005
in
http://tinyurl.com/6e36ny7
join us to talk about your project necessities.

Here:
https://code.google.com/p/wave-protocol/issues/detail?id=235
you have a sample of use of the previous patch. But it's not decided the
path to follow to permit that.

Greetings / saudações

Reply via email to