Add test scope to hamcrest dependency#428
Conversation
|
Thanks for the quick review, @lprimak, but we need someone with write access and I don't think such a person will be made available hastily considering that the last commit was 8 months ago :) |
|
I'll happily become a committer if you could arrange it somehow |
|
Hi there @lprimak @nlisker , sorry about being absent for the past couple of months. Our entire business unit got moved to a different company, we had to settle in, we're switching to a different infrastructure, our Nexus got decommissioned and we had to tackle many more challenges along the way. That being said, we didn't forget about Shrinkwrap :) Still got in on my to-do list and in the upcoming weeks I'd like to ask some of my colleagues to help me maintain it, now that the dust is settling down. Just please bear with me for the time being |
|
@petrberan We still don't have access to this ShrinkWrap organization, so that's what's blocking the rest of us working here... |
|
I'm hoping that this week I'll resolve the issue with releasing a new version and new SET member will take over Shrinkwrap @rhusar |
Hamcrest isn't declared as test dependency, which causes it to be pulled into a shrinkwrap archive.