as part of updating our jetty development setup I found that we declare openmrs-core dependencies without specifying that they are
provided which causes jetty to find them multiple times on the classpath.
by adding mavens
provided scope this issue is solved. I will add the missing scope as these libs have to be provided by the container the openmrs.war is deployed to.
Taglibs have been added back in TRUNK-4789, it has been mentioned that modules depend on some dependencies transitively, which I think is a bad habit we have, we should be explicit in what we depend on.
What I am wondering is why are they even in openmrs-core and not for example in the legacyui module? They are declared as dependencies in the web module but we do not have jsps/taglibs anymore in core. Is it because we still provide the possibility of deploying an openmrs module with jsps into a deployed openmrs.war without the legacyui?
Thank you for helping me understand