eclipse-plugin-cup: use `buildEclipsePlugin`

Since the `buildEclipsePlugin` function now can cope with multiple
plugin JARs we can avoid the workaround used by the cup plugin.

+11 -22
+11 -22
pkgs/applications/editors/eclipse/plugins.nix
··· 291 291 }; 292 292 }; 293 293 294 - cup = buildEclipsePluginBase rec { 294 + cup = buildEclipsePlugin rec { 295 295 name = "cup-${version}"; 296 296 version = "1.1.0.201604221613"; 297 297 version_ = "1.0.0.201604221613"; ··· 301 301 sha256 = "13nnsf0cqg02z3af6xg45rhcgiffsibxbx6h1zahjv7igvqgkyna"; 302 302 }; 303 303 304 - srcPlugin1 = fetchurl { 305 - url = "http://www2.in.tum.de/projects/cup/eclipse/plugins/CupReferencedLibraries_${version_}.jar"; 306 - sha256 = "0kif8kivrysprva1pxzajm88gi967qf7idhb6ga2xpvsdcris91j"; 307 - }; 304 + srcPlugins = [ 305 + (fetchurl { 306 + url = "http://www2.in.tum.de/projects/cup/eclipse/plugins/CupReferencedLibraries_${version_}.jar"; 307 + sha256 = "0kif8kivrysprva1pxzajm88gi967qf7idhb6ga2xpvsdcris91j"; 308 + }) 308 309 309 - srcPlugin2 = fetchurl { 310 - url = "http://www2.in.tum.de/projects/cup/eclipse/plugins/de.tum.in.www2.CupPlugin_${version}.jar"; 311 - sha256 = "022phbrsny3gb8npb6sxyqqxacx138q5bd7dq3gqxh3kprx5chbl"; 312 - }; 313 - 314 - srcs = [ srcFeature srcPlugin1 srcPlugin2 ]; 310 + (fetchurl { 311 + url = "http://www2.in.tum.de/projects/cup/eclipse/plugins/de.tum.in.www2.CupPlugin_${version}.jar"; 312 + sha256 = "022phbrsny3gb8npb6sxyqqxacx138q5bd7dq3gqxh3kprx5chbl"; 313 + }) 314 + ]; 315 315 316 316 propagatedBuildInputs = [ zest ]; 317 - 318 - phases = [ "installPhase" ]; 319 - 320 - installPhase = '' 321 - dropinDir="$out/eclipse/dropins/${name}" 322 - mkdir -p $dropinDir/features 323 - unzip ${srcFeature} -d $dropinDir/features/ 324 - mkdir -p $dropinDir/plugins 325 - cp -v ${srcPlugin1} $dropinDir/plugins/''${srcPlugin1#*-} 326 - cp -v ${srcPlugin2} $dropinDir/plugins/''${srcPlugin2#*-} 327 - ''; 328 317 329 318 meta = with stdenv.lib; { 330 319 homepage = http://www2.cs.tum.edu/projects/cup/eclipse.php;