-
Notifications
You must be signed in to change notification settings - Fork 928
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
Ability to programmatically define projects: Seq[Project] #2532
Comments
@Duhemm has explored trying to port this in #2183. I've needed access to Also I think this might be a blocker for https://github.com/sbt/sbt-pom-reader. |
That's interesting. It is explicitly read-only, but this ticket is to allow the "mutation" of Somewhat related is the ability to specify / select the |
Yes, that pull requested morphed into read-only. But I'm agreeing with you, there are use-cases that require programmatically defining projects, for which, to my knowledge, there's no facility currently in 1.0. |
@eed3si9n can this please be considered for 1.0? This one really is a blocker for me at work in moving to 1.0. |
for MiMa to convert to |
This adds support to generate synthetic subprojects from an auto plugin. In addition, a method called `projectOrigin` is added to distinguish Organic, BuildExtra, ProjectExtra, and GenericRoot.
This adds support to generate synthetic subprojects from an auto plugin. In addition, a method called `projectOrigin` is added to distinguish Organic, BuildExtra, ProjectExtra, and GenericRoot.
FPORT: Add extraProjects adn derivedProjects. Fixes #2532
Nice! I'll try this out sometime |
@fommil It'll be part of 0.13.13 (and available in the 0.13.13-RC2 pre-release) |
@dwijnand to help you test the fix, could I interest you in submitting a PR upgrading MiMa to use 0.13.13-RCx and addressing https://github.com/typesafehub/migration-manager/blob/7c956c57ae137dbfc729db54f5d35d33b9436347/project/Build.scala#L85-L87? “to help you”, my god, how transparent. see, it's all about you |
Sure. |
Is there a corresponding |
dependsOn(Project("aaa", file("yyy")), Project("xxx2", file("yyy2")))
|
With the new move to
.sbt
files, we will lack a key feature which is the ability to transformSeq[Project]
.A typical usecase for this is when the build structure is generated (perhaps translated from another tool) and the owner of the sbt build scripts can only apply transformations to the
Project
object rather than edit thebuild.sbt
directly.I feel this is a blocker for 1.0.
The text was updated successfully, but these errors were encountered: