james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Leangen (Jira)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-3260) Explore building Apache James with Gradle
Date Tue, 04 Aug 2020 12:19:00 GMT

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

David Leangen commented on JAMES-3260:

Hi [~ieugen]. The gradle build is awesome! Thanks so much for doing this.

I am wondering what the process is to keep it up to date. I tried running the gradle build
today, but it exits with errors.

My goal is to adapt it so I can release snapshots. It would be ideal if James released these
daily (I think some Apache projects do that), but in the meantime I would be satisfied to
be able to do that successfully to my own Nexus server.

I need this so I can attempt to have a proper build/deploy process for my custom James server.

I need that so I can continue with my Documentation project.

> 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: 10.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

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message