Timothy,
I will try that, it sounds like the ideal solution.
Cheers,
Andy
>>> "Timothy Reilly"
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
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please consider the environment before printing this email
WARNING: This email and any attachments may be confidential and/or privileged.
They are intended for the addressee only and are not to be read, used, copied or
disseminated by anyone receiving them in error. If you are not the intended
recipient,
please notify the sender by return email and delete this message and any
attachments.
The views expressed in this email are those of the sender and do not
necessarily reflect
the official views of SirTrack. see http://www.sirtrack.com
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
