> -----Original Message----- > From: KARR, DAVID > Sent: Tuesday, November 14, 2017 10:24 AM > To: users@felix.apache.org > Subject: How to augment final jar manifest with data from git-commit-id- > plugin > > I work on a large multiproject build, where the build artifacts are > bundles. All the child poms are packaging "bundle", and they use the > maven-bundle-plugin, and sometimes the "build-helper-maven-plugin" to > attach other artifacts. > > I decided I wanted to augment the final manifest to include the current > git commit id. I found the "git-commit-id-plugin", which seems to do > the trick. On simple test cases using "jar" packaging, it correctly > adds a manifest attribute with my git commit id to the manifest in the > resulting jar. > > However, what I find in my real projects, using "bundle" packaging, is > that the properties appear to be set, and the entry I added to > "manifestEntries" for the "maven-jar-plugin" does result in a line being > added to the manifest, but it doesn't substitute the property values in > that resulting line. > > The difference here appears to be bundle packaging. What do I have to > do here to property augment the resulting manifest with the properties I > want? > > I posted the details of my situation at > https://urldefense.proofpoint.com/v2/url?u=https- > 3A__stackoverflow.com_questions_47272026_git-2Dcommit-2Did-2Dplaced- > 2Dinto-2Dpom-2Dmemory-2Ddoesnt-2Dgo-2Dinto-2Dmanifest&d=DwIFAg&c=LFYZ- > o9_HUMeMTSQicvjIg&r=OsTemSXEn-xy2uk0vYF_EA&m=f62nIj17mFVuf4sbcWxf6B6- > PJVu9GNzijoREZMKsh0&s=r3iJ6tIo7mX2hDTjwNAZLamp7oqLCQ_2WIHl51ehNnE&e= .
I managed to resolve this soon after posting this. It just required adding some default instructions in a maven-bundle-plugin configuration. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
