Closed scherzhaft closed 6 years ago
Breaking up the initial baseline scan can be done by running the app on different subdirs in parallel. But I do see the value of also allowing individual files being passed in. These won't have the context of maven-metadata.xml
then, so we need to deal with that separately from the MavenRepoWalker
code path.
Following the maven G/A/V/.jar convention would a `dirname G/A/V/.jar` and/or a double dirname work?
Poking around in the code and doing some testing, it looks like I am able to get a 'quazi' explicit mode by specifying the full path to a given maven-metadata.xml as the repo path.
... a 'quazi' explicit mode by specifying ...
So, is the status-quo okay for you? If yes, please close this issue.
I am currently sending explicit maven-metadata.xml paths to it one at a time and using xargs -P to speed it up, seems to be working fine that way.
On Thu, Aug 23, 2018, 10:41 AM Christian Stein notifications@github.com wrote:
... a 'quazi' explicit mode by specifying ...
So, is the status-quo okay for you? If yes, please close this issue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sandermak/modulescanner/issues/5#issuecomment-415443094, or mute the thread https://github.com/notifications/unsubscribe-auth/AFP8cUpm7I3U18ZMvNu-hVFIhWcc-Ov8ks5uTr8OgaJpZM4VPfug .
Being able pass a list of files to scan will be very helpful for doing scans, both for scanning the deltas of new releases to Central, and for breaking the initial baseline scan up into several smaller more reasonable scans.