christian wrote in post #1151869:
I am happy to improve the jruby build process to be more suitable for
Thank you, Christian! The typical build-steps used during packaging
(whether in a FreeBSD’s port-build or when creating a Linux RPM, etc.)
- config – which lets the packager turn various optional parts of the
software on and off
- download – which (which rpmbuild does not handle, actually, but
- extract sources
- patch sources (with rpmbuild extraction and patching are the same
- build (rpmbuild combines configure and build into a single %build
- test (what FreeBSD ports call “regression-test” and rpmbuild refers
to as %check)
- package or install
Having a command (an mvn goal, make or ant target) for each of these
steps would be ideal. The commands should not overlap – for example,
the build should not perform tests and the test should not rerun the
entire build (although it is Ok for it to ensure, the build succeeded).
It should be possible to communicate the options, if any, specified by
the user in the first step of the process, via either command-line flags
(such as -Pfoo) or environment variables.
Another wish is for the package-building to be self-contained:
currently, I’m fighting maven’s attempts to download files into the
packager’s home directory by giving it a a custom settings.xml. But
that’s of secondary importance, because work-arounds exist.
after that you might want to in jruby-launcher gem
bin/jruby -S gem install jruby-launcher
which gives you a faster startup for jruby command line execution.
Can this be run after mvn -Pdist – but before packaging up the results?