I have a Java web project that I deploy to AWS Elastic Beanstalk. It has the AWS SDK for Java libraries as well as my Maven dependencies. There are conflicting versions of a few jars. For example: AWS SDK: httpclient-4.2.3.jar Maven: httpclient-4.3.jar
I don't run into the conflict locally, but when I deploy to AWS, both jars are deployed. The website doesn't work in this state, so I have to remove the old ones manually, then do a restart.
Not sure what the best option is, if it's a project setting/exclusion, or a setting for the deployment.
I have a Java web project that I deploy to AWS Elastic Beanstalk. It has the AWS SDK for Java libraries as well as my Maven dependencies. There are conflicting versions of a few jars. For example: AWS SDK: httpclient-4.2.3.jar Maven: httpclient-4.3.jar
I don't run into the conflict locally, but when I deploy to AWS, both jars are deployed. The website doesn't work in this state, so I have to remove the old ones manually, then do a restart.
Not sure what the best option is, if it's a project setting/exclusion, or a setting for the deployment.
0 commentaires:
Enregistrer un commentaire