[
https://issues.apache.org/jira/browse/JAMES-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242126#comment-13242126
]
Stefano Bagnara commented on JAMES-1396:
----------------------------------------
I can't make sense of this.
http://mail-archives.apache.org/mod_mbox/james-server-user/201101.mbox/%[email protected]%3E
We removed mailetpackages/matcherpackages directives in order to be able to
support OSGi and now we move around mailets because we don't have anymore the
mailetpackages/matcherpackages but we don't care about OSGi anymore.
If we don't want to support OSGi then we should bring back
mailetpackages/matcherpackages and remove OSGi descriptors from our manifest
files.
We already have this "package" exposed by mailets/standard artifact and by
james-server/mailets artifact: and both of them already export the same
package. With this change we make that issue bigger.
I won't veto this, but please think twice at what is the direction. If we have
the issue of And/Or matchers, do we think that every james user will have to
put his mailets/matcher in the org.apache.james.transport package or accept to
repeat the full package everytime?
> Move composite matchers to standard package
> -------------------------------------------
>
> Key: JAMES-1396
> URL: https://issues.apache.org/jira/browse/JAMES-1396
> Project: JAMES Server
> Issue Type: Improvement
> Components: Matchers/Mailets (bundled)
> Reporter: TzeKai Lee
> Attachments: move_composite.patch
>
>
> move And/Or/Xor/Not
> from org.apache.james.mailetcontainer.impl.matchers
> to org.apache.james.transport.matchers
> so we don't need type FQN in configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
