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

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" wrote:

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: Compiler plugin & JDK 9 & classpath/modulepath question

On Wed, 09 Nov 2016 13:24:02 +0100, Matej Novotny wrote: Hello, I was recently trying the following scenario with JDK 9 and mvn compiler 3.6.0: A new Maven project, with module-info, running with JDK 9, having a dependency on one other non-modular project (Weld SE

First build in CI with Maven 3.0.5 gets bundle errors

I'm working with a large multi-module project that produces OSGi artifacts. I cloned it to my desktop, and it builds fine with maven 3.3.9. Today I set up a Jenkins pipeline job to build it. The first time I ran it, I saw errors like the following: --- Invalid extension descriptor

[ANN] Apache Maven Doxia Sitetools 1.7.4 released

The Apache Maven team is pleased to announce the release of the Apache Maven Doxia Sitetools, version 1.7.4 Doxia Sitetools is an extension of base Doxia component that generates either HTML sites, consisting of decoration and content that was generated by Doxia, or documents like RTF or

How to put project information metadata into a top-level POM, and have it be part of generated effective POM in META-INF/maven tree?

I work on a large multi-project build. We produce a framework that other teams use. Although all of the teams that use our framework know who we are, it occurred to me that it would be considerate to make sure that there is metadata in the generated artifact that would give someone

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

Hi, > what could be interesting is to include the exact git commit at point > of packaging Use the buildnumber-maven-plugin for this, together with maven-jar-plugin manifestEntries config: https://github.com/scijava/pom-scijava-base/blob/pom-scijava-base-1.0.0/pom.xml#L233-L238