Krystian Panek

considering https://taskfile.dev/experiments/env-precedence/ now mvnw could be integrated in simpler way

hey @mitchross ; now Maven Wrapper is in use. the new AEM projects after AEMC project scaffold command run will use mvnw (instead of mvn) which eliminated a need to...

[1] is fixed

Nice one. To have two-way sync. Thanks @kwin 🙂

opting for 1.

also consider implementing AEMC Packer Provisioner - https://developer.hashicorp.com/packer/docs/plugins/creation/custom-provisioners

thanks for reporting, will be implemented within this month ;)

when deploying a package that is changing some configuration of `ResourceResolverFactory` then AEM may restart many bundles and become unstable for a longer time. but... this usually is a one-time...

thinking about sth like that: then such `foo` pkg settings will be automatically in-use basing on path pattern and the fact if package was deployed before or not, `AEM_INSTANCE_CHECK_PACKAGE=foo sh...

regarding second point - will be addressed by #159 generic check will have a form of current configuration/options that AEMC gives currently; third point is a thing to address here...