Hi *,
I was able to invest some time into srcdeps in the recent couple of
months. Srcdeps is now a bit more powerful - esp. it is able to handle
all kinds of dependencies incl. parents and BoM imports. The new
functionality was enabled by using the Maven Core Extensions API instead
of Maven Plugin API.
Technically, srcdeps now provides its own custom implementation of Maven
Local Repository [1]. In this way srcdeps is able to intercept every
single request to the Maven Local Repository and eventually build the
requested artifact from source and install it locally if necessary.
The convention to declare a source dependencies using
-SRC-revision-{sha1} suffix stayed unchanged. However, the mapping from
GAVs to git repositories now lives in .mvn/srcdeps.yaml file rather than
in pom.xml file.
In the coming weeks, I'll be preparing PRs to migrate from the old
srcdeps-maven-plugin to the new srcdeps core extension.
I'll also introduce mvnw (a.k.a. Maven Wrapper [2]) so that there is a
common way for developers, CI and srcdeps to get the same clearly
defined version of Maven.
Are there any concerns or questions?
[1]
https://github.com/srcdeps/srcdeps-maven
[2]
https://github.com/takari/maven-wrapper#maven-wrapper
Thanks,
Peter