The Buildbot has detected a restored build on builder tapestry-site-production
while building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/tapestry-site-production/builds/1052
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-cms-slave
Build
The Buildbot has detected a new failure on builder tapestry-site-production
while building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/tapestry-site-production/builds/1053
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-cms-slave
Build
Apart from repackaging... Is there anything special we do with ASM?
Perhaps we could automate this using jarjar or shadow gradle plugins?
On 12 Aug 2015 11:34, Jochen Kemnade jochen.kemn...@eddyson.de wrote:
Hi,
currently, we ship ASM 5.0.1 with plastic, the latest version is 5.0.4:
I'd love to automate it, but right now it is just manual.
It would also be nice to analyze which subset of ASM classes we actually
need, and exclude the rest.
I believe I've done this in the past by just copying the sources as is
under plastic/src/external, and then doing a package rename from
