[JAMES-2877] release process should deploy and generate more artifacts

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.7.0
• Component/s: Build System
• Assignee: Unassigned
• Reporter: Matthieu Baechler
• Created: 06/Sep/19 07:46
• Updated: 04/Sep/21 05:45
• Resolved: 04/Sep/21 05:45

Description

During the release of James, we lack some artifacts that in theory should be part of the staging repository before the vote then would go to Apache Dist when releasing.

Here is the list of artifacts we should produce and deploy to staging:

• the zip file containing all the source code (it's generated but not uploaded)
• a zip file for each product we provide with compiled artifacts (spring-app is handled but guice products are not)

Issue Links

• relates to: JAMES-3225 Provide automated builds for Apache James - (restore builds.apache.org ?)