We are setting the manifest entries of the archiver to the project properties and the OSGi header. https://maven.apache.org/shared/maven-archiver/examples/manifest.html
Gruss Bernd -- http://bernd.eckenfels.net On Fri, Nov 11, 2016 at 10:35 PM +0100, "KARR, DAVID" <dk0...@att.com> wrote: > -----Original Message----- > From: Stian Soiland-Reyes [mailto:st...@apache.org] > Sent: Thursday, November 10, 2016 4:20 PM > To: Maven Users List > Subject: Re: Strategies for augmenting jar manifest with source > provenance info? > > Look in META-INF/maven of the jars made with Maven, which should include > a copy of pom.xml. Then just make sure your project has an updated > block. I reposted a separate question on this, but perhaps I should have just continued this thread. My problem with this approach is that I want to store this info in the very top-level POM, and have it be used in all of the subprojects. I don't understand how to make that happen. > On 10 Nov 2016 11:35 pm, "KARR, DAVID" wrote: > > > I'm thinking of augmenting builds to add provenance info to the > > manifest of the artifacts we produce, to indicate what git url the > > current artifact is associated with (a "ContactInfo" tag might also be > > useful). Is this something that anyone has ever tried to do? If so, > > what strategies have you used? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
