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 "Jukka Zitting (JIRA)" <se...@james.apache.org> on 2007/05/03 10:57:15 UTC
[jira] Created: (JAMES-792) James artifacts in the Maven repository
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
[jira] Commented: (JAMES-792) James artifacts in the Maven
repository
Posted by "Jukka Zitting (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493324 ]
Jukka Zitting commented on JAMES-792:
-------------------------------------
Perhaps a good starting point would be to deploy just the Mailet API jar file. It doesn't have such troublesome dependencies and is probably the most important dependency for external projects that want to integrate with James.
> 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
[jira] Closed: (JAMES-792) James artifacts in the Maven repository
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin closed JAMES-792.
---------------------------------------
Resolution: Fixed
I think that this has been resolved by the factoring out of the mailet stuff into separate products.
For example:
http://james.apache.org/mailet/api/ has been released
http://james.apache.org/mailet/base/ is being released
More releases are expected in due course
> 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
[jira] Updated: (JAMES-792) James artifacts in the Maven repository
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ 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
[jira] Commented: (JAMES-792) James artifacts in the Maven
repository
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ 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:
cornerstone-socket-impl-2.1-patched.jar
cornerstone-datasources-impl-2.1-patched.jar
bcmail-jdk14-workaround-129.jar
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