You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm uploading an assembled artifact to our internal Maven repo, and would like to include a -sources.jar that was the merged sources of the main project + the dependencies that end up in the assembly jar.
assembly-src would be analogous to package-src as assembly is to package, except Scala library source should not be included by default. Likely it would expand AssemblyOption, which currently works like this:
assemblyOption in assembly <<= (assembleArtifact in packageBin,
assembleArtifact in packageScala, assembleArtifact in packageDependency, excludedFiles in assembly) {
(includeBin, includeScala, includeDeps, exclude) =>AssemblyOption(includeBin, includeScala, includeDeps, exclude)
},
assemblyOption in packageDependency <<= (assemblyOption in assembly) { opt =>
opt.copy(includeBin =false, includeScala =true, includeDependency =true)
},
assemblyOption in packageScala <<= (assemblyOption in assembly) { opt =>
opt.copy(includeBin =false, includeScala =true, includeDependency =false)
},
The build user should be able to control the default assembly behavior by setting:
assembleArtifact in packageSource :=true
assembleArtifact in packageDependencySource :=true
In other words, assemblySource would be a specialized version of assemblyOption:
@stephenh wrote:
assembly-src
would be analogous topackage-src
asassembly
is topackage
, except Scala library source should not be included by default. Likely it would expandAssemblyOption
, which currently works like this:The build user should be able to control the default
assembly
behavior by setting:In other words,
assemblySource
would be a specialized version ofassemblyOption
:The text was updated successfully, but these errors were encountered: