build should be good. the only thing left to fix is the fact that when you run java/server it gets an exception from oauth because it can't find the oauth.xml file. I don't know why this is happening yet.
- cassie On Tue, Apr 22, 2008 at 10:19 AM, Ian Boston <[EMAIL PROTECTED]> wrote: > > Ian > > > > On 22 Apr 2008, at 05:53, Brian Eaton wrote: > >> 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. >> > > > Have you tried > > cd shindig/java > > mvn eclipse:eclipse > > and then import the projects into eclipse ? > > This will generate the .classpath and .project files correctly for you. > When you want a new dep, add it to the pom and repeat the > > mvn eclipse:eclipse > > It also adds the transitive dependencies so is much faster than hand > editing eclipse properties. You can also ask it to get the source jars and > link them into the classpath. > > > >> - 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. >> > > Dependencies, > We should have a dependency management statement in the base pom that > contains the version numbers of everything we use (except internal > references) so that we dont have to remember or update version numbers. > > We might also consider putting all the standard plugin config and repo > information in the base pom. > > > SNAPSHOT > the maven-release-plugin automates the tagging, version change, release > process and deployment to the external maven repo. > > Not editing required > > > When set up properly.... it saves a huge amount of time, and makes it much > much easier for others to use the outputs. No more chasing bugs because you > have managed to package the wrong version of a dependency in production. > > > >
