Am 2014-06-26 14:34, schrieb Mark Derricutt:
In last weeks dev hangout I raised the idea of removing <repository>
elements due to some issues with them regarding mirrors etc which was
somewhat negatively received, however I've been thinking about this a
bit and came up with an interesting idea earlier in the night whilst at
a gig.
One of the problems I'm often seeing is that:
1) a project uploads their artefact to a repository ( mostly maven
central )
2) 90% of their dependencies are available from the repository in question
3) 1 critical dependency is not - which ultimately means you can't
build......if you have a mirror setup
(usually because you've not noticed a <repository> declaration which you
need to configure in your nexus/arifactory/archiva etc. )
The idea I had is three fold:
1) Fallback on original repository when a mirror doesn't resolve
When maven is checking for a repository for an artefact, and using a
mirror - if that artefact can't be found, maven should retry using the
original repository directly with builds warnings.
Not going to work if you are behing a MRM instance and proxied in a
company like me.
2) Deploy transitive runtime dependencies along with your release
This beats DRY and reinvents the wheel.
I would obstain doing either one.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
