0

I have the next problem. "A" library contains custom JSF components. "B" library contains Selenium tests for these custom components, and some others (Primefaces JSF components).

When I develop "A", I want to test any change using "B" in order to check if I've broken something. So "A" needs "B" dependency in test scope.

When I develop "B", I want to test any change using "A" for deploying a website on the fly at testing-time in order to check if I've broken something. So "B" needs "A" dependency in test scope.

So, How is the best way to avoid the cyclic dependency and get my goal?

New contributor
Jesus Lunar Perez is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

0

Your Answer

Jesus Lunar Perez is a new contributor. Be nice, and check out our Code of Conduct.

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.