Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a way to tell maven to continue the build although a dependency ist missing?
I tried <optional>true</optional> but this doesn’t seem to do it in this scenario.
I have build a costum Maven Plugin for the package phase and it does still have to package even if one or multiple dependencies could not be found.
Thanks in advance.
Optional means that a client using your library does not necessarily need that dependency. An example is Spring’s ORM module, that has optional dependencies to Hibernate, JDO, JPA and mybatis. Nobody will ever use all of these in a project, so each is marked as optional.
Your case is completely different, you are trying to compile something, and you can only do that if the libraries you compile against are present. Sorry, it don’t work like that.