Hi, there is already an open PR for the maven-hpi-plugin to add the metadata to Manifest: https://github.com/jenkinsci/maven-hpi-plugin/pull/68
Cheers, Zbynek On Tuesday, June 25, 2019 at 11:09:09 AM UTC+2, Daniel Beck wrote: > > > > > On 24. Jun 2019, at 20:27, 'Gavin Mogan' via Jenkins Developers < > [email protected] <javascript:>> wrote: > > > > So looks like one either uses properties, or a new doctype. I feel like > the doc type might be way too hard. > > > > <jenkins.plugin.changelog.url> > > > > Would that be too hackish? For the site backend? > > Don't start here. > > This should be done (IMO) via new entries in the plugin's MANIFEST.MF > file. > > To accomplish that, extend maven-hpi-plugin to have a new option for the > changelog or whatever, and if set and non-empty, add that to the manifest. > > Then update the plugin parent POM to the new release of maven-hpi-plugin, > and parameterize the new option based on a property. > > Then you can update the plugin's POM to the latest parent POM and set the > property. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/dacf9e37-58bb-4f9a-a844-3567ee583114%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
