What steps will reproduce the problem?
1. Make a full build
What is the expected output? What do you see instead?
Something similar, that can be found on the download page
What version of the product are you using? On what operating system?
Windows, 1.5.4 version
Please provide any additional information below.
During the discussion of 204 Johan said it would be helpful to provide help in
building up the release artifacts, which had to be adjusted manually for each
release. I am going to provide this now.
Please find the attached patch. Can be applied against the 1.5.4 branch (I
guess with minimal changes also against trunk. I compared the result of the
assembly zips with the downloadable bundled zips on the homepage. They are the
same.
One sidenote: I think adding CGLIB and Hamcrest to the mockito specific
artifacts does not make a sense, since mockito-all contains them already, but
maybe I am wrong. I added some comments to the poms and assembly files into the
patch about this.
I changed the maven-assembly-plugin version from 2.2 to 2.4. 2.2 had problems
with filtering the transitive dependencies and basicly behaved randomly. Now
with the 2.4 it seems predictable and working. One more thing is that the
default scope processed by the maven assembly plugin is the runtime scope, so I
instructed it to get the compile scope instead.
Original issue reported on code.google.com by gabor.li...@gmail.com on 8 Feb 2014 at 10:50
Original issue reported on code.google.com by
gabor.li...@gmail.comon 8 Feb 2014 at 10:50Attachments: