This message was deleted.

Why can't you rename the projects? They could stay in the same place on disk. That way manual substitutions should not be necessary.

because renaming the projects would make all command line cumbersome with everything prefixed with

micronaut-

. Not mentioning that it would mean rewriting all project dependencies.

Commandline is imho not that problematic, as you can use

m-foo

or

mFoo

and do not have to type it out completely. But yeah, the dependencies would need to be rewritten once. Good time to introduce Project accessors maybe? 😄

I think that would also ruin our GE test execution history model (for predictive test selection)

Or not forcing to

${project.group}:${project.name}

but somehow provide another mean to define the coordinates in a composite build compatible way independent from project group and name. Maybe that's worth a feature reuquest if there is none yet. 🙂

the pb for composite builds is discovering the publications. Currently it misses the fact that the artifact ids are renamed, probably because of how it builds its model. So if instead of tweaking the publications to change the artifact ids, there was something in

settings.gradle

which defined the "project naming strategy" and its mapping to publication coordinates, then it would be an easy win for composites.

I didn't look at the code, just at the docs. And there it says that you need manual substitution

When the

maven-publish

or

ivy-publish

plugins are used for publishing, and the publication coordinates don’t match

${project.group}:${project.name}

.

That's why I thought some way independent from project group and name that is supported by composite build is necessary.

because of this issue, I always start new projects with names that I intend to live with Forever (™️). But of course that's not a solution for a preexisting project. At least in your world people tend to set the

group

! No one does that in Android-land 😭