Yes, it seems there is no easy way to set a higher timeout per project, see e.g. <https://issues.apache.org/jira/browse/GUMP-131>https <https://issues.apache.org/jira/browse/GUMP-131>:// <https://issues.apache.org/jira/browse/GUMP-131>issues.apache.org <https://issues.apache.org/jira/browse/GUMP-131>/ <https://issues.apache.org/jira/browse/GUMP-131>jira <https://issues.apache.org/jira/browse/GUMP-131>/ <https://issues.apache.org/jira/browse/GUMP-131>browse <https://issues.apache.org/jira/browse/GUMP-131>/ <https://issues.apache.org/jira/browse/GUMP-131>GUMP <https://issues.apache.org/jira/browse/GUMP-131>-131 <https://issues.apache.org/jira/browse/GUMP-131>.
We can probably try splitting the downloading and the generation step, not sure if it will help until we have a proper split-up of the schemas. Dominik. Maybe its possible to split the compilation in smaller parts and reference the already compiled schema, i.e. something like in [1] I guess this would lead to a faster compilation with a smaller memory footprint. ... and of course this would fit with my plan to have separate modules/schema jars :) Andi [1] http://stackoverflow.com/questions/2743131/how-to-import-other-schema-jars-when-using-the-scomp-tool -- View this message in context: http://apache-poi.1045710.n5.nabble.com/GUMP-vmgump-Project-ooxml-schemas-in-module-poi-failed-tp5721599p5721603.html Sent from the POI - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
