This is tricky dealing with the fast-moving shindig since we don't have a formal release process yet. But there are ways to deal with Maven's aggressive updating. You can set it to offline mode, you can force it to only look to a local update repository with only stuff you approve in it and you can make all these changes to your local system permanent by making a .m2/settings.xml file. I've done this and it's worked out pretty good.
davep 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? > > (Tried to search through Shindig and Maven list archives but > didn't see much discussion. Apologies if this is old hat.) > > Hans >
