RE: Strategies for augmenting jar manifest with source provenance info?

> -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

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. 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

Strategies for augmenting jar manifest with source provenance info?

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

[ANN] Maven Fluido Skin 1.6 released

The Apache Maven team is pleased to announce the release of the Maven Fluido Skin, version 1.6. This module generates browsable HTML pages from Java source code. https://maven.apache.org/skins/maven-fluido-skin/ You should specify the version in your project's site configuration: