Say if xmlrpc decide to split into xmlrpc-common, xmlrpc-server,
xmlrpc-client, xmlrcp-all then it can say that it "conflict" with xmlrpc
- and for xmlrpc-all it can say that it "replace" xmlrpc.
Still, user intervention is required, but thats better than having the
same library on the path multiple times, just due to the fact that the
name differs.
AFAIK this this what the <relocation> element is designed for in POMs
If you ask for xmlrpc and new version has split as you suugest, a POM
can be deployed with relocation to xmlrpc-all
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
