Factor boilerplate from phantomjs to an sbt-dependent library

Bug #1175428 reported by Stephen Compall
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
platform-executing
Fix Released
Wishlist
Stephen Compall

Bug Description

phantomjs, the sample of a capturing library, manages to offload *most* of its build system magic to the core platform-executing library. There's still a bunch of weirdly specific boilerplate, though.

Much of this could go in a p-e dependent, sbt-dependent library.

* unmanagedSources in Compile <+= (PhantomJS.java "generator"): Should be a triple of these properties as sbt settings instead, which generates the relevant Java file.

* phantomjsBinaries, phantomjsVersion: I don't think we can produce those Scala symbols without adding a metametaproject, but the setting keys are straightforward, and you get a nice obvious error when you fail to set them.

* licenses <++=. Supply the licenses present when a binary is present, and it will add an entry when it's right to add.

* mappings in (Compile, packageBin): Pure boilerplate given the above.

Changed in platform-executing:
milestone: 0.2.0 → 0.3.0
Changed in platform-executing:
milestone: 0.3.0 → sbt-plugin-0.3.0
Changed in platform-executing:
status: New → In Progress
assignee: nobody → Stephen Compall (scompall)
Revision history for this message
Stephen Compall (scompall) wrote :

phantomjs r53 illustrates usage of the new style.

Changed in platform-executing:
status: In Progress → Fix Committed
Changed in platform-executing:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.