I'd suggest to
- create an issue for the bug to be solved
- create and attach a patch to the issue
- install the patched dependency with version N+1 and classifier
(-patchXYZ123) to avoid any conflict
Nico.
My solution in such a case:
- Download the source for the broken plugin
- Fix the dependencies
- Increment the version by 1 (i.e. 2.0.2 in this case).
- Deploy the new plugin to a local repository
Now, you can use this version in your projects until the bug is fixed.
You might also want to add -SNAPSHOT to the version but then, you have to
make sure that you're not getting into conflicts with the official
snapshots.
If the plugin is released with the very same version, you have to delete
it manually on your side but until then, you can work.
How about a -PATCH version? :-)
Regards,
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]
