> Andy Dingfelder wrote:
> The reason I do not want to try and put the jars in my
> repository is that I have the 3rd party jars checked into SVN
> as a project in my workspace, and thus can ensure that my 3rd
> party jars are accessible on any machine that tries to do the build.
>
> My thinking was that if they were in the repository , I would
> have to have some way of syncing those 3rd party jars
> manually on each machine to ensure they got updated.
>
> Perhaps I am doing it backwards but I want an easily
> reproducible environment.
>
> How do others deal with this?
>
A couple suggestions:
Setup an organizational (company) repository. This is easy. I think most
people are using http servers for this - we are.
Your useage of svn is the right idea (centralize your artifacts) but
company repositories do this. If you really feel strongly about using a
revisioning system like svn for the repository I believe some of the
repository managers allow this.
Distribute an organizational global settings file, settings.xml - you'll
want to add your company repo information in here.
Finally, create an organizational pom. This should be the top most
parent project for most of your organizations projects. Here you can
define a dependencyManagement section for things like your serialio
artifact if you wish.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
