Push maven profiles down into a parent POM #2
Labels
Comments
tfennelly
added a commit
that referenced
this issue
Aug 30, 2016
* Import by version range ... history might look weird after this commit because I stupidly reset to an earlier commit and had to use the IDE's local history to recover the changes ... phew !! * Created ModuleSpec and Version types * Extract Version and ModuleSpec types into modules of their own * Split out Version and ModuleSpec tests into spec files of their own * More Version and ModuleSpec tests (and fixes) * Higher level version range bundle load tests * Fix module CSS url * Fix ModuleSpec.prototype.getLoadBundleFileNamePrefix to normalize the package name E.g. where there's an org in the name * Fix for Array iteration bug + nsProvider in importAs * set beta version * Stash docs * fix dep versions * Remove dependency on window-handle * New beta version * 0.0.6 release version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hooking Gulp, Browserify etc into a maven build currently requires some
<profiles>to be added to the build. It's ugly/bloaty, made worse by the fact that we currently have to manually download and install io.js (#3).Would clean things up a bit (and reduce setup effort) if these
<profiles>were in a parent POM.The text was updated successfully, but these errors were encountered: