It should be noted that it’s usually a good idea to have a configured resolve step performed by the bnd-resolver-maven-plugin. This allows you to do a resolve from the command line, and have those changes written back to the bndrun file. The resolve step in the export plugin, on the other hand, is best combined with the <failOnChanges> option enabled. This way you have a verification step that runs in every build to ensure that the resolve result is sensible, but a manual command that you can run (i.e. not run by CI) used to make changes to the checked in source (the bndrun file).
Regards, Tim > On 22 Jun 2017, at 16:27, Raymond Auge <raymond.a...@liferay.com> wrote: > > I did forget the "resolve" step! > > In the configuration of the maven plugin add: > > <resolve>true</resolve> > > - Ray > > On Thu, Jun 22, 2017 at 9:56 AM, Mark Raynsford <list+org.o...@io7m.com > <mailto:list+org.o...@io7m.com>> wrote: > On 2017-06-21T18:32:35 -0400 > Raymond Auge <raymond.a...@liferay.com <mailto:raymond.a...@liferay.com>> > wrote: > > > > <instructions> > > 'Ello! > > Thanks for the detailed instructions. I'll give this a go shortly. > > M > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > > -- > Raymond Augé <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) > Senior Software Architect Liferay, Inc. <http://www.liferay.com/> (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> (@OSGiAlliance) > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
