On Tue, Jul 1, 2008 at 10:32 AM, Hans Granqvist <[EMAIL PROTECTED]> wrote:
> Hi all > > I'm looking for advice how to best maintain code that my > team develops (handlers and the UI and other components) > and the rapidly changing Shindig code. > > I am a bit unsure how to best handle the maven build since > there is quite a lot of dependencies on external components. > > While I can certainly use the Maven build as it is, it seems > dangerous to depend on external components auto-updated > by Maven. At the same time, taking a snapshot of the Shindig > code probably adds a lot of headache in the future when it > comes time to reconcile new Shindig code. > > Perhaps there is Maven magic to deal with this? Just curious > how other people make this work, especially in a setting where > you have developers who know very little about Maven. Am I > over-estimating the pain? Most of the dependencies are versioned. Some aren't, but they should be to avoid these issues (if you see any that aren't, feel free to let us know) If you're using Java already, I'd suggest just building the jars from maven and re-packaging them into your own deployment mechanism of choice. The pre-built war is there primarily for illustrative purposes, though it will probably be adequate for many containers. > > (Tried to search through Shindig and Maven list archives but > didn't see much discussion. Apologies if this is old hat.) > > Hans >
