Re: [aether-users] Multiple processes writing to same local repository (

[Ron Pressler <ron@xxxxxxxxxxxxxxxxxxx>]

The answer is yes -- the processes will interfere with one another and corrupt the artifacts (or, at least, some of the processes will fail). The solution is to use this Aether plugin that allows concurrent access to a shared local repository (it uses lock files).

On Thu, Apr 23, 2015 at 3:57 PM, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx> wrote:

Hi,

I am wondering if multiple Aether *processes* (not threads) will corrupt
a shared local repository if the following conditions are met:

- All processes use the *same* remote repository
- All processes only write to the local repository through Aether
- All artifacts in the remote repository are snapshots
- The local repository is managed using
aether.artifactResolver.snapshotNormalization=false.

I observe *.part and .part.lock files being created during the download
and the code in org.eclipse.aether.connector.basic.PartialFile suggests
that multiple processes downloading the same file won't step on each
others toes. Is this true?

And yes, I am aware of the takari-local-repository project [1], but this
also has to handle cases like multiple, different remote repositories,
so it might be overkill. (Besides, it's unlikely that I can get
takari-local-repository and friends OSGified and IP-reviewed in time for
Eclipse Mars.)

Best wishes,

Andreas

[1] <https://github.com/takari/takari-local-repository>

--
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
aether-users mailing list
aether-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/aether-users