I *think* there is no verification that all dependencies exist in central, so you would then put something into central that will not work for the the end users. We've been there several times in the past and it hasn't been a pleasant experience.
/Anders On Thu, Apr 12, 2012 at 09:41, Nord, James <[email protected]> wrote: > Hi all, > > I was wondering how things are supposed to work when you have a sync to > central but you relly on a patched version of a 3rd party artifact. > > For example lets assume my library X depends on apache common io, and the > current version has a bug that has been sitting around with a path for a > while and not making it into any release. > So according to the documents normally we would download and build a patched > verison of commons:commons-io and deploy it to our repo as > common:commons-io:1.2.3-4_JIRA1234 > > Using the same Group and artifact is recommended to avoid bringin in > duplicate classes is someone who consumes our lib also uses commons-io. > > Anyway this is all good - but what happens if we want our artifact X synced > to central - we must have all dependencies available on central but we have > no sync control on commons/commons-io. > > What would normally happen here? > > /James > > ________________________________ > > ************************************************************************************** > This message is confidential and intended only for the addressee. If you have > received this message in error, please immediately notify the > [email protected] and delete it from your system as well as any copies. The > content of e-mails as well as traffic data may be monitored by NDS for > employment and security purposes. To protect the environment please do not > print this e-mail unless necessary. > > NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 > 4EX, United Kingdom. A company registered in England and Wales. Registered > no. 3080780. VAT no. GB 603 8808 40-00 > ************************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
