[
https://issues.apache.org/jira/browse/JAMES-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Baechler updated JAMES-3260:
-------------------------------------
Description:
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
was:
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
> 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: 1h 10m
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
