You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Ioan Eugen Stan (Jira)" <se...@james.apache.org> on 2020/07/02 10:49:00 UTC

[jira] [Commented] (JAMES-3260) Explore building Apache James with Gradle

    [ https://issues.apache.org/jira/browse/JAMES-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150179#comment-17150179 ] 

Ioan Eugen Stan commented on JAMES-3260:
----------------------------------------

The gradle build passes locally for me and other developers and I am working to make it build on builds.apache.org. 
Some integration tests are disabled because of dependency issues. 
Some tests are disabled because they fail.

One (mpt test) is disabled because it is also disabled in maven. 

{noformat}
 git grep 'enabled = false'
mpt/impl/imap-mailbox/cyrus/build.gradle:    enabled = false
mpt/impl/imap-mailbox/external-james/build.gradle:    enabled = false
mpt/impl/smtp/cassandra-rabbitmq-object-storage/build.gradle:    enabled = false
mpt/mavenplugin/build.gradle:    enabled = false
server/container/core/build.gradle:    enabled = false
server/container/guice/blob-objectstorage-guice/build.gradle:    enabled = false
server/container/guice/cassandra-rabbitmq-guice/build.gradle:    enabled = false
server/container/guice/cassandra-rabbitmq-ldap-guice/build.gradle:    enabled = false
server/data/data-jmap/build.gradle:    enabled = false
server/mailet/integration-testing/build.gradle:    enabled = false
server/protocols/jmap-draft-integration-testing/rabbitmq-jmap-draft-integration-testing/build.gradle:    enabled = false
server/protocols/jmap-rfc-8621-integration-tests/distributed-jmap-rfc-8621-integration-tests/build.gradle:    enabled = false
server/protocols/webadmin-integration-test/distributed-webadmin-integration-test/build.gradle:    enabled = false
{noformat}

The focus is to make the build work on builds.apache.org and then fix the integration tests.


> 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: 8.5h
>  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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org