Hi Pulasthi,
We have already developed a test case in the same test class to find out
duplicate jars inside a distribution , which will help us to get an idea
about the distribution size.
Regards
On Wed, Nov 6, 2013 at 12:38 PM, Pulasthi Supun pulas...@wso2.com wrote:
Hi,
Rather than just
Hi Dimuthu,
Ok great :)
Regards,
Pulasthi
On Wed, Nov 6, 2013 at 2:01 PM, Dimuthu De Lanerolle dimut...@wso2.comwrote:
Hi Pulasthi,
We have already developed a test case in the same test class to find out
duplicate jars inside a distribution , which will help us to get an idea
about the
Note: The test will use a common value of 20 MB for all products. In case
the difference between running distribution's size compared to maven repo's
latest distribution size exceeds 20 MB the test will encounter a failure.
Your suggestions to estimate a more accurate common value for comparison
Hi,
Rather than just giving a failure notice is it possible to display some
information on why the distribution size has grown. ex. if there are any
duplicate jars, files as i remember you were looking into the possibility
of achieving this. I am not sure about the feasibility of finding out
Hi All,
We are going to implement the $subject. Our strategy for this is to
validate the running distribution pack's size against the latest
distribution hosted in the maven repo. This means that we are assuming
maven repo always carries the latest released product distribution of a
given
