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

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

Some tips in point 2 of this 
https://docs.gradle.org/current/userguide/migrating_from_maven.html 


{noformat}
Develop a mechanism to verify that the two builds produce the same artifacts

This is a vitally important step to ensure that your deployments and tests 
don’t break. Even small changes, such as the contents of a manifest file in a 
JAR, can cause problems. If your Gradle build produces the same output as the 
Maven build, this will give you and others confidence in switching over and 
make it easier to implement the big changes that will provide the greatest 
benefits.

This doesn’t mean that you need to verify every artifact at every stage, 
although doing so can help you quickly identify the source of a problem. You 
can just focus on the critical output such as final reports and the artifacts 
that are published or deployed.

You will need to factor in some inherent differences in the build output that 
Gradle produces compared to Maven. Generated POMs will contain only the 
information needed for consumption and they will use <compile> and <runtime> 
scopes correctly for that scenario. You might also see differences in the order 
of files in archives and of files on classpaths. Most differences will be 
benign, but it’s worth identifying them and verifying that they are OK.
{noformat}


> Acceptance criteria checklist
> -----------------------------
>
>                 Key: JAMES-3273
>                 URL: https://issues.apache.org/jira/browse/JAMES-3273
>             Project: James Server
>          Issue Type: Sub-task
>            Reporter: Ioan Eugen Stan
>            Assignee: Benoit Tellier
>            Priority: Major
>
> We need a list of acceptance criteria for making the gradle migration.
> We need a checklist so we know when we are ready for the merge.
> Please add this checklist here. 
> Some items are sub-tasks of https://issues.apache.org/jira/browse/JAMES-3260 



--
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

Reply via email to