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
Currently one has to configure target environments rather globally and then they are used to resolve all projects, this currently leads to the situation that each project resolved the same things multiple times. Also if there is a platform filter one still needs to configure one even though the target is known. There is only one place where different environments are relevant and that is for building a product with different natives.
My proposal is to change the behavior so what we already have at some places:
If a platform filter is there use that as the target to resolve dependencies
Otherwhise use the current running target it it matches any of the configured environments
Use all configured ones if it does not match
with the exception of products, but there it should be considered to simply allow to configure additional environments in the materialize-product mojo instead of have them globally.
The text was updated successfully, but these errors were encountered:
Currently one has to configure target environments rather globally and then they are used to resolve all projects, this currently leads to the situation that each project resolved the same things multiple times. Also if there is a platform filter one still needs to configure one even though the target is known. There is only one place where different environments are relevant and that is for building a product with different natives.
My proposal is to change the behavior so what we already have at some places:
with the exception of products, but there it should be considered to simply allow to configure additional environments in the materialize-product mojo instead of have them globally.
The text was updated successfully, but these errors were encountered: