Skip to content

Conversation

@plamentotev
Copy link
Member

This is my attempt to fix #10

This is somewhat simple approach. It adds entries synchronously while it could add them in parallel as long as it does not add them in parallel with entries from the same resource collection.

Alternative approach could be for example to have Executor that allows only one entry from a given non-concurrent collection to be added. Maybe it could lead to better performance but I would rather prefer the simpler approach.

plexus-io 2.7 adds support for resource collection that does not allow
concurrent access to it's entries. Add flag to ArchiveEntry so archiver
implementations could know that they should add entries form such
collections synchronously.
@plamentotev plamentotev changed the title Add entries synchronously Add entries synchronously from resource collections that do no support concurrent access Dec 14, 2015
@plamentotev plamentotev changed the title Add entries synchronously from resource collections that do no support concurrent access Add synchronously entries from resource collections that do no support concurrent access Dec 14, 2015
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Manifests are not added in parallel anyway but just in case.

@krosenvold krosenvold merged commit 1a75e20 into codehaus-plexus:master Mar 3, 2016
@plamentotev plamentotev deleted the add-entries-synchronously branch March 3, 2016 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

addArchivedFileSet to ZipArchiver does not work with tar archives

2 participants