Look's like all the breakages are just because Louis's change was
outdated. I'll fix them now...

On Tue, Apr 22, 2008 at 6:53 AM, Brian Eaton <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 21, 2008 at 3:11 PM, Cassie <[EMAIL PROTECTED]> wrote:
>> I checked in the last piece today and updated all of the READMEs.
>>  Everything is stable and the following instructions are what you want:
>>
>>  cd java
>>  mvn package
>>  cd gadgets (or social-api or server)
>>  mvn jetty:run-war
>
> Been there, done that, saw the build choke and die.
>
> There's a fix for one build break attached to
> https://issues.apache.org/jira/browse/SHINDIG-206.
>
> When I run jetty in java/gadgets, mvn jetty:run-war works.  (Hooray!
> No way I'm actually going to try testing the server yet.)
>
> When I run jetty in java/social-api, mvn jetty:run-war appears to
> work, but throws a Guice exception that looks like it might be fatal:
> 1) Error at 
> org.apache.shindig.gadgets.BasicRemoteContentFetcher.<init>(BasicRemoteContentFetcher.java:64):
>  Binding to org.apache.shindig.gadgets.ContentCache not found. No
> bindings to that type were found.
>
> When I run jetty in java/server, the build chokes and dies for reasons
> I don't understand, but appear maven and/or pom related:
>
> Missing:
> ----------
> 1) org.apache.shindig:social-api:jar:1-SNAPSHOT
>
>
> A couple of questions:
> - Anybody tried eclipse yet?  I was able to import java/pom.xml as a
> maven project into eclipse, but needed to add a bunch of dependencies
> before the build would work.  Am I doing something wrong, or am I just
> a trail blazer?  I suspect it may be both.
>
> - I'm hating on maven.  Is this the best it can do, or are we using it
> wrong?  Things that should be simple, like updating a dependency for
> the project or updating the project version number, appear to require
> hand editing multiple pom.xml files in multiple places.  I counted the
> phrase "1-SNAPSHOT" on 14 lines in 5 files.
>

Reply via email to