Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark BuildMojo as threadSafe #364

Merged
merged 4 commits into from
Aug 21, 2018
Merged

Mark BuildMojo as threadSafe #364

merged 4 commits into from
Aug 21, 2018

Conversation

timkrueger
Copy link
Contributor

This annotation will remove a maven build warning.

Resolves: #326

This annotation will remove a maven build warning.

Resolves: #326
@coveralls
Copy link

coveralls commented Aug 15, 2018

Coverage Status

Coverage decreased (-1.1%) to 64.948% when pulling 2cca1e8 on timkrueger:mark-thread-safe into 869aa78 on asciidoctor:master.

@timkrueger
Copy link
Contributor Author

Hmm. Is there a meaningful test which I can add for my pull request?

@abelsromero
Copy link
Member

We could try a it test with a couple of submodules with differnet documents.
If the documents don't mix content, we can assume it's OK (here there's an example https://github.com/abelsromero/asciidoctor-maven-plugin/tree/add_capture_of_Asciidoctor_log_messages/src/it/spi-registered-log).
Reviewing Maven documentation & code again, I don't see why it should fail un multi-thread scenario.

Tim Krüger added 3 commits August 20, 2018 15:28
All three modules produces the same result. If the content
is mixed during the parallel execution the results will
be different and the test fails.
Set 'headerFooter' to 'false'. The generated html files must
not contain timestamps.
@timkrueger
Copy link
Contributor Author

I think now I got it 😁

@abelsromero
Copy link
Member

I guess that should be enough 👍

@abelsromero abelsromero merged commit 48d1142 into asciidoctor:master Aug 21, 2018
@timkrueger timkrueger deleted the mark-thread-safe branch August 21, 2018 12:42
@timkrueger
Copy link
Contributor Author

@abelsromero Any plans when 1.5.7 will be released?

@abelsromero
Copy link
Member

Only pending thing is #363. Since is a long requested feature I'd really appreciate some feedback :% but I'd probably merge this weekend regardless.

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.

None yet

3 participants