I think this would be better as an enforcer rule - and could be very quickly implemented using evaluateBeanshell. Existing scripting plugins (groovy, jruby, etc.) could also do this in very few lines without a custom plugin.
- Brett On 11/04/2011, at 6:50 PM, Anadi Misra wrote: > Hi! > > wanted to know your thoughts on having a plugin that checks the size of a > built artifact in case of JAR, or the exploded/built artifact in case of war > archives. The reason is quite a few hosting services providers put a price on > size of WAR archives being uploaded, tracking the war file size for failure > of build if it becomes too large might be a good idea for such projects. We > have added this plugin to our build life-cycle since in our case it is very > expensive to increase the allowed exploded size from 20MB to 25MB by our > CDN/Cloud computing provider. > > Please do let me know your comments / feedback. > > BR/ > Anadi Misra. -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
