dev-java/ant-ivy-2.1.0 has been released on Oct 08, 2009.
A simple rename/copy of the ebuild seems to do the trick.
While you're at it, 2.2.0 has been released as well. That version has a dep on the Bouncy Castle Crypto APIs, which are not in portage yet.
Can we look at this again, I've installed 2.1 on my system with a simple ebuild rename with no issues.
Created attachment 318908 [details] ant-ivy-2.2.0.ebuild Initial version of ant-ivy-2.2.0.ebuild. It requires bcpg (#427636)
Created attachment 324624 [details] ant-ivy-2.2.0.ebuild new ebuild version: unnecessary dependency fixed, do all tests pass.
Created attachment 324626 [details] files/ant-ivy-2.2.0-build.xml.patch
Attached ebuilds would need to be investigated on whether they contribute necessary changes; I haven't looked into them yet, but that they were left here without an explanation concerns me. (In reply to Ole Langbehn from comment #2) > While you're at it, 2.2.0 has been released as well. That version has a dep > on the Bouncy Castle Crypto APIs, which are not in portage yet. Affirmative, saw that too, I'll create a bug for that right now and block.
+ 05 Jul 2013; Tom Wijsman <TomWij@gentoo.org> +ant-ivy-2.3.0.ebuild: + Version bump to 2.3.0. This was bumped as part of a large series of dev-java/ant* related bumps, therefore attribution is missing in the commit message; therefore, thank you very much for reporting and contributing!
