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 IntelliJ. But sed might work just as well. On Thu, Aug 13, 2015 at 4:42 AM, Lance Java <lance.j...@googlemail.com> wrote: > 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: > > http://asm.ow2.org/history.html. As the 5.4 release seems to be coming > > close (yeah!), I'd like to get that up-to-date. > > What's the current way to update the sources? Is it a completely manual > > process, as in download the tgz, extract the relevant part from the > archive > > and sed the package statement? > > > > Jochen > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: dev-h...@tapestry.apache.org > > > > > -- Howard M. Lewis Ship Looking for Clojure engagements: coding, architecture, mentoring & more! Creator of Apache Tapestry (971) 678-5210 http://howardlewisship.com @hlship
