[Soot-list] Mavenize Build (Issue 44)

[Almo]

Hey,

a) They're rarely updated as far as I know. Instead of checking them into a local maven repo manually, we could just include them as a local dependency (include in lib/ set url in pom.xml to relative path).
b) Technically we don't have a need for baf since we translate everything to jasmine.

Al



On Sunday, October 13, 2013 10:30 AM, Bernhard Berger <berber at tzi.de> wrote:
 
Hi everyone,

I started to convert the build system to maven (https://github.com/bergerbd/jasmin/tree/mavenize and https://github.com/bergerbd/soot/tree/mavenize) and have some questions regarding the current ant-based build.

a) polyglot and JastAdd
Currently, there are binary forms of these libraries checked in. How frequently are these dependencies updated? Is it sufficient to check in the binaries (local mvn repositories) and update it if necessary?

c) baf.scc
There is a grammar for baf that is not translated into a scanner. Is baf unsupported and should be removed?

d) Which are the ant targets that are still used? There are target such as: javadoc, badfields, buildtests, runtests, release, barebones, classesjar and fulljar.

The next (and last step) will be to convert the build of the eclipse-plugins. I hope the tycho plugin will work

Regards,

Bernhard
_______________________________________________
Soot-list mailing list
Soot-list at sable.mcgill.ca
http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20131013/2780b36b/attachment.html