[
https://issues.apache.org/jira/browse/JAMES-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140485#comment-17140485
]
Ioan Eugen Stan commented on JAMES-3260:
----------------------------------------
Replying to [~matthieu] from https://issues.apache.org/jira/browse/JAMES-3225 .
Regarding the gradle POC you did.
Is that something we can use - can you rebase it on current master?
I know gradle has some migration functionality build in so it might be the same
effort to start from scratch.
I would like to contribute to this, so we can sync + work together on a branch
once we decide how we create that branch.
I would create it on apache and sync via personal PR's from each of our git
repos to this feature branch.
Once we are satisfied we can merge it in master and have both working side
until we are confident we can drop the maven build.
The final check would be: we are able to release Apache James with Gradle
instead of Maven.
> Explore building Apache James with Gradle
> -----------------------------------------
>
> Key: JAMES-3260
> URL: https://issues.apache.org/jira/browse/JAMES-3260
> Project: James Server
> Issue Type: Improvement
> Reporter: Ioan Eugen Stan
> Priority: Major
>
> Creating an issue to track the process of using Gradle for building Apache
> James.
> There have been a few discussions on this topic from multiple parties.
> The main benefit is having faster builds which Maven is unable to provide
> because of it's limitations on how it approaches build life-cycle and
> caching.
--
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
