> > 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. > > I would do everything that I could to get this patch applied by the dev team > and > have another release produced by them with this fix included. Can you tell us > the specific JIRA number which you are referencing?
Commons-io was just an example - I could just have easily said foobarwhizzylib. Turns out the OSS product I was referening to actually deploys the patched libs under its own GAV which I missed when looking at it - so this isn’t actually an issue to me anymore. > Otherwise you would follow these directions: > https://docs.sonatype.org/display/Repository/Uploading+3rd- > party+Artifacts+to+The+Central+Repository ************************************************************************************** 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 **************************************************************************************
