#1 update to version 1.12
Merged 4 years ago by decathorpe. Opened 4 years ago by decathorpe.
Unknown source master  into  master

file modified
+4
@@ -1,3 +1,7 @@

+ /results_*

+ /*.src.rpm

+ 

  /fusesource-pom-1.5.tar.bz2

  /fusesource-pom-1.9.pom

  /fusesource-pom-1.11.pom

+ /fusesource-pom-1.12.pom

file modified
+5 -2
@@ -1,6 +1,6 @@

  Name:             fusesource-pom

- Version:          1.11

- Release:          6%{?dist}

+ Version:          1.12

+ Release:          1%{?dist}

  Summary:          Parent POM for FuseSource Maven projects

  License:          ASL 2.0

  URL:              http://fusesource.com/
@@ -33,6 +33,9 @@

  %license LICENSE

  

  %changelog

+ * Sat Oct 05 2019 Fabio Valentini <decathorpe@gmail.com> - 1.12-1

+ - Update to version 1.12.

+ 

  * Thu Jul 25 2019 Fedora Release Engineering <releng@fedoraproject.org> - 1.11-6

  - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild

  

file modified
+1 -1
@@ -1,1 +1,1 @@

- SHA512 (fusesource-pom-1.11.pom) = ec58f78348489f9d1b4a4bb545eeae2820126bcd9152f32a76086c29a5a795c247773c2c4251c319b09424e346b252e0d2be90bf5d3f8e0614682be8ba63ea89

+ SHA512 (fusesource-pom-1.12.pom) = 1378fc44bd73525218e4e435b638d77de1c41185c1813220a024a564d63a1bdcb9fb20fb460937cd7e26b302d5ed0024835c8337b807f1e2f8c4cd63a16db794

This PR updates fusesource-pom to the latest version (1.11 → 1.12). Looking at the diff, the update is harmless.

Test rebuilds of dependent packages were successful:

https://copr.fedorainfracloud.org/coprs/decathorpe/fusesource-pom-pr/monitor/

  • jspc already fails due to a broken dependency (groovy18 was retired)
  • logback already fails due to broken dependencies (felix-osgi-* to osgi-* transition missing from felix-main) - both logback and felix-main are orphans

Ah, perhaps I'm going to ask a stupid question, but why do we actually need this package? Isn't it just a pom? Does a raw pom with no JAR/classes/etc. do anything for anybody?

Why (and how!) does what depends on it actually use it? Seems like we might be better off updating our packages and orphaning it...?

@cipherboy maybe we can do %pom_remove_parent in packages that use this. Sometimes this works, but if other packages actually use metadata from parent POMs, it doesn't work.

Ah is this like oss-parent where all of FuseSource's projects use it? Hmpfh.

Still wish there was a way we could bundle this with the packages themselves. Seems wasteful to ship a RPM with a single POM file just to appease the Fedora Packaging Committee.

Ah well, ship it!

Fedora Packaging Committee here. This does not appease me :D

Pull-Request has been merged by decathorpe

4 years ago