> -----Original Message----- > From: Stian Soiland-Reyes [mailto:st...@apache.org] > Sent: Thursday, November 10, 2016 4:20 PM > To: Maven Users List <users@maven.apache.org> > 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 <scm> > block.
Ah, and even better would be the info about the people working on the project. That looks like a good strategy. > Now what could be interesting is to include the exact git commit at > point of packaging, which I believe could be possible to add using the > release plugin..? (It already rewrites the scm tag of the pom). One step at a time. :) > On 10 Nov 2016 11:35 pm, "KARR, DAVID" <dk0...@att.com> 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 > > > >
