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 "Robert Burrell Donkin (JIRA)" <se...@james.apache.org> on 2009/02/28 16:10:13 UTC
[jira] Updated: (JAMES-792) James artifacts in the Maven repository
[ https://issues.apache.org/jira/browse/JAMES-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin updated JAMES-792:
----------------------------------------
Affects Version/s: 3.0
Fix Version/s: 3.0
Assignee: Robert Burrell Donkin
> James artifacts in the Maven repository
> ---------------------------------------
>
> Key: JAMES-792
> URL: https://issues.apache.org/jira/browse/JAMES-792
> Project: JAMES Server
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 3.0
> Reporter: Jukka Zitting
> Assignee: Robert Burrell Donkin
> Priority: Minor
> Fix For: 3.0
>
>
> The James artifacts should be deployed on the central Maven repository for easy access by external projects that want to implement custom mailets or embed individual James components. The NOTICE/LICENSE files should be included in the jar files, and at least simple POM files with correct dependencies should be maintained. Additionally, as mentioned by Stefano Bagnara on the server-dev mailing list: "[...] it is not only a matter of gpg signing, adding a pom and submit the package to the repository: we should first VOTE to release the JARs alone."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org