[
https://issues.apache.org/jira/browse/CALCITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250662#comment-14250662
]
Vladimir Sitnikov edited comment on CALCITE-484 at 12/17/14 10:19 PM:
----------------------------------------------------------------------
{quote}Is it possible to exclude it by default but include it in a profile that
we can enable for testing? (E.g. in travis-ci.) I want to prevent
bit-rot.{quote}
I have no idea. Then I keep the module intact.
What do you think if we change travis-ci command to {{mvn test && mvn
-DskipTests -Dcheckstyle.skip=true site}}?
This should speed-up site generation while still test all the things as part of
initial mvn test
was (Author: vladimirsitnikov):
{quote}Is it possible to exclude it by default but include it in a profile that
we can enable for testing? (E.g. in travis-ci.) I want to prevent
bit-rot.{quote}
I have no idea. Then I keep the module intact.
What do you think if we change travis-ci command to {{mvn test && mvn
-DskipTests -Dcheckstyle.skip=true -Dsource.skip=true site}}?
This should speed-up site generation while still test all the things as part of
initial mvn test
> 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)
