james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-792) James artifacts in the Maven repository
Date Thu, 03 May 2007 09:12:15 GMT

    [ https://issues.apache.org/jira/browse/JAMES-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493318

Stefano Bagnara commented on JAMES-792:

About "correct dependencies" I have to add that we have some custom dependency in JAMES Server
that will not be possible to make available via maven repository.

As you can see in our stage folder and in the current pom.xml dependencies we depend on "patched"
versions of 3rd party (or other ASF projects) libraries:

You ask why we depend on patched cornerstone libraries? https://issues.apache.org/jira/browse/EXLBR-30
About bcmail I should check if the newest releases still have the problem I foound with the
129 (there was a missing class in bcmail: the workaround is needed to avoid dependencies on
the full bouncycastle JCE).

> James artifacts in the Maven repository
> ---------------------------------------
>                 Key: JAMES-792
>                 URL: https://issues.apache.org/jira/browse/JAMES-792
>             Project: James
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Jukka Zitting
>            Priority: Minor
> 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

View raw message