architecture - Maven exclude philosophy -
- what maven excluded dependencies invented for?
- should care exclude dependencies other fixing libraries conflicts?
- what maven project architecture like:
- tend exclude as possible
- or minimum needed?
i don't know reasons design i've seen used in following cases:
- i had library had
junitcompile time dependency junit code leaked production code. - i had library uses
log4j. since i'm usingslf4j, used dependency exclusion rid of hardwired logging framework , usedslf4j-log4jbridge instead loglogback. - in case, using features of framework , didn't need dependencies. since weren't optional in first place, used exclusions keep classpath lean , clean.
general rules:
- use rid of things break build
- get rid of things you're replacing else
- get rid of things know don't need (optional)
if none of rules apply, leave dependency alone; chances immediate dependency might change on time , suddenly, need dependency seemed superfluous before , code unexpectedly break.
Comments
Post a Comment