This seems to be a bug or something not quite right with the
bnd-maven-plugin. I've filed an issue:
https://github.com/bndtools/bnd/issues/2454
Plugins like the maven-jar-plugin (and evidently the
maven-bundle-plugin) appear to do the right thing, but the
bnd-maven-plugin seems not to. Strangely,
On 2018-05-19T14:35:25 +0200
Andreas Sewe wrote:
>
> Maybe it depends on the Maven version (here: 3.5.2)? Try to clone the
> above Github repository, do a "mvn clean verify" and check what "unzip
> -p
>
Mark Raynsford wrote:
> Spoke a bit too soon. I'm using the bnd-maven-plugin, but I don't think
> that changes anything. I have:
>
>
> biz.aQute.bnd
> bnd-maven-plugin
> ${io7m.bnd-maven-plugin.version}
>
>
>
>
>
On 2018-05-18T16:50:56 +0100
org.apache.maven.u...@io7m.com wrote:
> On 2018-05-18T17:01:52 +0200
> Andreas Sewe wrote:
>
> > here's what I use as an for the maven-bundle-plugin to
> > generate a Bundle-License line in my MANIFEST.MF:
> >
> > >
On 2018-05-18T17:01:52 +0200
Andreas Sewe wrote:
> Hi,
>
> > Is there a way to access the contents of the element as POM
> > properties? I'd like to reference the URL of the first license element
> > in a plugin execution, but there doesn't appear to be a
>
Hi,
> Is there a way to access the contents of the element as POM
> properties? I'd like to reference the URL of the first license element
> in a plugin execution, but there doesn't appear to be a
> ${pom.license.url} or anything similar.
here's what I use as an for the maven-bundle-plugin to