Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building blocks for custom package formats? #312

Closed
copumpkin opened this issue Aug 5, 2014 · 2 comments
Closed

Building blocks for custom package formats? #312

copumpkin opened this issue Aug 5, 2014 · 2 comments
Labels
documentation Documentation should be extended or updated

Comments

@copumpkin
Copy link

Is there an API to facilitate packaging in non-standard/provided formats? I haven't poked around the source much, but I assume there's a decent amount of overlap in shared functionality between the different packaging formats, and that sbt-native-packager could also facilitate packaging to more obscure formats that aren't directly supported.

If there is such an API, can it be more documented? If not, can we get it? 😄

@muuki88 muuki88 added macosx and removed macosx labels Aug 5, 2014
@muuki88
Copy link
Contributor

muuki88 commented Aug 5, 2014

Everything is based in the universal packaging layout. If you want
the startscript to work, you have to use this layout.

Whats your usecase?

@muuki88 muuki88 added documentation Documentation should be extended or updated and removed feature request labels Sep 23, 2014
@muuki88
Copy link
Contributor

muuki88 commented Sep 23, 2014

I'll change this to a documentation thing. Normally you can reuse all the settings defined by the sbt-native-packager like, daemonUser, mappings, etc. to build your own task/settings in your build which create a custom package format.

An example for this is the sbt-assembly example with native-packager. Instead of a a list of jars you get single fat-jar

muuki88 added a commit that referenced this issue Sep 25, 2014
…in Universal and Linux

Conflicts:
	src/sphinx/DetailedTopics/index.rst
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation should be extended or updated
Projects
None yet
Development

No branches or pull requests

2 participants