[
https://issues.apache.org/jira/browse/CALCITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246573#comment-14246573
]
Vladimir Sitnikov commented on CALCITE-484:
-------------------------------------------
Updates: for maven-compiler there is a workaround, for maven-resources I hope
there would be a fix.
{quote}0) maven-compiler-plugin is recompiling all the sources since we have
lots of {{package-info.java}} files that procuce _no_ {{package-info.class}
files.{quote}
The relevant ticket for maven is https://jira.codehaus.org/browse/MCOMPILER-205.
As a temporary workaround I suggest adding a dummy annotation for each
package-info.java.
I did a quick check for avatica and it helps:
{code:java}
@PackageMarker
package org.apache.calcite.avatica;
import org.apache.calcite.avatica.util.PackageMarker;
{code}
{quote}1) maven-resources-plugin rewrites destination files when filtering is
active.{quote}Relevant ticket is http://jira.codehaus.org/browse/MSHARED-394
{quote}3) generate-fmpp-sources – seems to regenerate the same parser again and
again{quote}
Here's issue for https://github.com/freemarker/fmpp/issues/11
If we fix maven-resources-plugin somehow, then we can workaround fmpp as
follows: put fmpp output to some staging folder and use maven-resources just to
copy from staging to "actual". Here maven-resources would eliminate rewrite of
the file since it would compare the contents.
{quote}4) hydromatic-resource-maven-plugin seems to regenerate the same
runtime for each execution{quote}
[~julianhyde], do we really need this dependency? If we do I can file an issue
against https://github.com/julianhyde/hydromatic-resource/, however I suppose
it might be easier if we just commit the
{{org.apache.calcite.runtime.Resources}} in Calcite repository.
Either way works for me.
> Heal incremental maven compilation: each mvn install rebuilds the whole thing
> -----------------------------------------------------------------------------
>
> Key: CALCITE-484
> URL: https://issues.apache.org/jira/browse/CALCITE-484
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating
> Reporter: Vladimir Sitnikov
> Assignee: Julian Hyde
> Labels: newbie
>
> Currently the jar files are rebuild even if the source files were not
> modified.
> It would be nice to eliminate unnecessary work from the build.
> The list of bad plugins is:
> 1) maven-resources-plugin. It always regenerate files above files from
> velocity templates.
> 2) git.properties -- we might not need the exact build timestamp for dev
> builds
> 3) generate-fmpp-sources -- seems to regenerate the same parser again and
> again
> 4) hydromatic-resource-maven-plugin seems to regenerate the same
> runtime for each execution
> 5) org-apache-calcite-jdbc.properties includes build.timestamp
> If I "disable" those plugins, the subsequent builds take 6-7 seconds
> and the jars are not updated.
> Total time: 6.237 s
> Most time consuming are:
> 1.4s Calcite
> 1.2s Calcite Ubenchmark
> 0.9s Calcite Plus
> 0.8s Calcite Core
> 0.6s Calcite Spark
> http://mail-archives.apache.org/mod_mbox/incubator-calcite-dev/201411.mbox/%3CCAB%3DJe-FviBdTtSm%3D74vUSPrwQBESU4XsDpDtmGgJhS2rsp%2BdpA%40mail.gmail.com%3E
> http://mail-archives.apache.org/mod_mbox/incubator-calcite-dev/201411.mbox/%3CCAB=je-gqe83f3qhcofxniu8eq9yygos-jy4dscr-qmpuxxo...@mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
