Hi all,

I have searched and read about how to make maven articles able to deploy to
different environment. Most of the suggestions are recommending using maven
profiles to do filtering on the configuration files. However, how can we
solve the problem if we need to deploy the artifact to internal repository
for others to lookup? Is it the artifact that deployed to the internal
repository contains configurations for a specific environment?

Currently, we are using multi-module layout. For cross module dependency,
our idea is to depend on the artifact from the internal repository, instead
of checking out all the dependency modules and build them one by one.
However, there are some configurations within the dependencies that need to
be changed across different machine. What should we do so that we can have a
clean / easy way to solve the issue?

Thanks!


Best Regards,
Deep Blue

Reply via email to