1) if you are in a bndtools workspace: say you have a project with a bndrun file like so:
workspace-root/projectA/my.bndrun then execute the gradle command: cd workspace-root ./gradlew :projectA:export.my 2) if you are in a maven project using the bnd-export-maven-plugin [1]: then execute the following: mvn bnd-export:export 3) if you are in a gradle project using the none-workspace bnd gradle plugin [2]: Create and execute an export [3] task Sincerely, - Ray [1] https://github.com/bndtools/bnd/blob/master/maven/bnd-export-maven-plugin/README.md [2] https://github.com/bndtools/bnd/tree/master/biz.aQute.bnd.gradle#gradle-plugin-for-non-workspace-builds [3] https://github.com/bndtools/bnd/tree/master/biz.aQute.bnd.gradle#create-a-task-of-the-export-type On Mon, Mar 5, 2018 at 12:49 PM, Randy Leonard via osgi-dev < osgi-dev@mail.osgi.org> wrote: > To all: > > Regarding the creation of standalone executables for enRoute projects: > > - Documentation is given here: http://enroute.osgi.org/ > tutorial_base/700-deploy.html > - Unfortunately, these are manual instructions for exporting from > within Eclipse > > > My request is for instructions to generate standalone executables via > command line script. It would be great to automate this task. > > Thanks in advance > Randy > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > 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
