If Project B has a dependency on Project A.
Do I need to do a maven install on Project A every single time I make a change to one of the classes in A in order for B to see the update?
Share
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.
If Project B has a dependency on Project A.
Do I need to do a maven install on Project A every single time I make a change to one of the classes in A in order for B to see the update?
It depends how you created the projects. If you have a common parent pom, then you won’t need to run
mvn installfor one project to see the changes on the other.If the projects don’t share a common parent pom, I think it might be better to configure eclipse manually so it knows that B depends on A, and you’ll also need to remove the dependency on the snapshot jar (otherwise you might get funky classloader errors). I have to say that every time that I had projects dependencies like this, the projects shared a common parent.