I think at this time obviously we have to change
in parent/pom.xml#build/pluginManagement to never skip downloading
dependencies, because it is most common use case. After it is done we can
remove unnecessary <skip>false</skip> throughout the projects.
Yes - your conclusion matches mine on the jira and what mistria suggestion for fixes
and with my updates handles.
Can you make it happen ?
If there are libs for (2) and (3) downloaded from external URL using
download-maven-plugin/maven-download-plugin we should probably move them to
Main problem I know is forge, hibernate and openshift afaik.
forge and openshift would not be able to move very fast if we moved their libs for Locus.
Hibernate - we don't actually want/intend to expose the internal apis of hibernate so not
sure if pushing all variations of hibernate into Locus is such a good idea....but it could
One thing that might be worth looking for are those bundling mockito or other testing libs
that we might already have put into locus or use from orbit so these are not even relevant anymore.