Re: [tei-council] antify branch

Admittedly I've only created a simple cocoon project with maven, but I've installed and used a number of projects with it. My limited understanding is that maven imposes a common project structure and makes it simple to manage dependencies. This SO answer seems helpful: http://stackoverflow.com/questions/603189/differences-between-ant-and-maven#... On Thu, Sep 24, 2015 at 9:42 AM, Peter Stadler wrote:

Yes, I’ve heard rumors about it ;) Honestly, I took just a quick glance and it looked too complicated for me at that time. But you’re right, we should at least have some sort of analysis/discussion of/about our build tool(s).

So, can anyone comment on maven and whether it’d suit us better?

Best Peter

...

Am 24.09.2015 um 15:37 schrieb Raffaele Viglianti < raffaeleviglianti@gmail.com>:

Hi Peter,

Thanks for working on this - I realize I'm making this suggestion very late at this point, but I've noticed a lot of Java projects using maven instead of ANT for building these days. Is it worth looking into it? (Converting from ANT to Maven *should* be simple)

Raff

On Thu, Sep 24, 2015 at 8:19 AM, Martin Holmes wrote:

...

HI Peter,

Bravo for this. The PDF stuff eventually should be XSL:FO with FOP, I think, because none of us now understand LateX; but I think it should all be doable using <exec> in ant; it'll have to branch depending on OS. Alternatively, you should shell out from ant to a small using <exec> Makefile as a temporary measure.

Cheers, Martin

On 15-09-24 02:31 AM, Peter Stadler wrote:

...

Dear all,

just an update on my work of antifying the build process of the Guidelines: * I more or less simply try to convert the current Makefile targets to ANT targets * I’m collecting all settings (params) in a build.properties file which can be overwritten by a local.build.properties file (which is excluded from version control) * during the build process, I’m creating a "build" folder for temporary stuff (currently, everything ends here). I envision to have a clean „dist“ folder in the end, where the to-be-distributed files are summoned, together with zipped archives. * so far I can create the Guidelines (Makefile target „teiwebsiteguidelines“) with all dependencies * leaves the hard stuff: PDF (via LaTeX) and various Tests …

Best Peter

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived