if amper is now going the standalone route, it wou...

# amper

[christophsturm]

if amper is now going the standalone route, it would be cool if i could still use an amper build as part of a gradle composite build. and maybe amper can also support composite builds with other amper builds.

[Anton Prokhorov]

hi, thanks for sharing!

and maybe amper can also support composite builds with other amper builds

very important question here what is the use case behind this need, we definetely want to have something like source/binary hot swap, when you want to edit the application and external library (in terms of your application build) simultaneously

it would be cool if i could still use an amper build as part of a gradle composite build

yes, it would!

Again, it depends on a problem we are solving, we definetely are going to design some gradual migration route for Gradle builds, and it may be part of that, but there are no specifics so far (no guarantee that Amper can be part of a composite Gradle build in the future)

[christophsturm]

Two use cases: 1. composite build based mono
Repos where I can migrate slowly from gradle to amper.
2. Use git checkouts of dependencies for debugging.

[Anton Prokhorov]

yeah, got it, thanks for clarification

basically we have 3 situations with composite builds:
• Amper Amper - here I believe there is no need of having composite builds, they could be just modules
• Gradle Amper
• Amper Gradle
2 other cases gonna be covered in gradual migration from other build systems

However, I have no specifics so far about gradual migration, can't say anything now, but we are thinking about this

[louiscad]

Amper Amper composite builds would be helpful for libraries via git submodules

[Anton Prokhorov]

Amper Amper composite builds would be helpful for libraries via git submodules

Fair point, but it could be only one of the solutions of hot-swap between binary and source dependencies

[louiscad]

True, though what I had in mind is not hot swapping binary libraries, but having internal libraries that exist only as sources, with no maven repository set.

[Anton Prokhorov]

I have some something how to approach that in mind, but the use case itself is very important, thanks

I'm gonna make sure we won't forget about this use-case during the design

[louiscad]

Another use-case that is indeed linked to hot-swapping binary libraries with sources is working on libraries that will eventually be released/published.

Having minimal changes to swap somehow would be very nice for testing library changes quickly, and possibly not even have to rely on any published binaries if not necessary.

Now, even better would be the ability to have multiple projects in the IDE connected to the same library added as a composite build somehow, so that it's possible to perform library refactorings across more than one project at a time.
We have a use case for that in my company, and I have for personal projects too.

I find it much less clunky than the publish to mavenLocal dance that doesn't work on CIs unless you add dedicated (complicated?) config for it.