ot; 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
> -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 jar
u, Nov 10, 2016 at 6:38 PM, KARR, DAVID 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 mani
> -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 jar
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
plu
