[
https://issues.apache.org/jira/browse/JAMES-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136505#comment-17136505
]
Ioan Eugen Stan commented on JAMES-2826:
----------------------------------------
Maven doesn't do much caching.
It always runs through every phase and goal regardless if inputs changed or not.
Gradle is more smart and can cache the results of the builds.
It can also work with a build server - to cache builds remotely/distributed.
It works because compilation is a pure function (most of the time :D) and if
you checksum the inputs, and the configuration, the result should always be the
same.
I think our solution to this is to leverage gradle.
Another solution is to split the project (again) in multiple git repositories
and not pay the compilation cost for things we did not work on.
Gradle has came up a few times in discussions.
I think we can have a goal to migrate to gradle if people agree. ( I do and I
support this migration).
I believe we can have both builds side by side for some time.
We could start with a smaller project first and then learn what we need to do
for james-project itself.
WDYT? If you agree, let's move things forward.
We should have some progress for 3.6.x .
> Improve compile time
> --------------------
>
> Key: JAMES-2826
> URL: https://issues.apache.org/jira/browse/JAMES-2826
> Project: James Server
> Issue Type: Improvement
> Reporter: Matthieu Baechler
> Assignee: Ioan Eugen Stan
> Priority: Major
>
> Given that javac is a very fast compiler, we should be able to have a very
> fast compile phase with maven.
> However, it takes several minutes right now.
> We should bring back some sanity to this build.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
