So instead of build/${name} it would be ${buildDirName}/${name}
If we do add this we should also handle building into a directory N levels deep, including N=0 aka the cwd/project root.
We could rename buildDirName to buildDir and support configuration as a path (relative to root). So build/, dist/, and dist/deep/build/ would all work. And . could represent root.
We also should support out dirs for each individual build though, something @keanulee was asking for. So one project-level setting and one build-level.
/sub
Any news?
This would go a long way, as we have customized builds of the same application for different customers. Currently every build flavour needs to be a separate app, that pulls in the source as a dependency, which make it difficult to build every flavour.
any update ?
FWIW, we use Maven as our build orchestrator tool of choice, and ideally, we'd point polymer to the 'target' directory so it's automatically cleaned up with maven clean.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
If we do add this we should also handle building into a directory N levels deep, including
N=0aka the cwd/project root.We could rename
buildDirNametobuildDirand support configuration as a path (relative to root). Sobuild/,dist/, anddist/deep/build/would all work. And.could represent root.