[
https://issues.apache.org/jira/browse/JAMES-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ioan Eugen Stan closed JAMES-3260.
----------------------------------
Resolution: Abandoned
I think maven is pretty good for James.
Maybe more work could be done to avoid building some components that are not
needed like:
* avoid building distributed instance when you want single instance James only
* Avoid running integration tests during regular build
* etc.
> 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
> Assignee: Ioan Eugen Stan
> Priority: Major
> Time Spent: 10h 50m
> Remaining Estimate: 0h
>
> 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.
> We should take care of:
> * all that is related to release and deploy (but this can be taken from other
> Apache projects already using Gradlle)
> * the site building (but this should disappear with the migration to Antora)
> * the mailets plugin
> * checking Spring build
> * adding partial tests on JMAP integration (allowing to run only some smoke
> tests on some big integration tests suite)
> * adding and configuration the checkstyle plugin
> * updating the Jenkins build
> * documenting the migration for all the users that are building James
> themselves
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
