JAMES-2334 arbitrary name for each rabbit docker cluster container
In cluster environment, there is a relationship between rabbitmq nodename
suffix (domain part) and rabbitmq container hostname. If they are not the same,
rabbitmq docker cannot start.
- arbitrary rabbit docker name by adding an
[
https://issues.apache.org/jira/browse/JAMES-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit resolved JAMES-2572.
---
Resolution: Fixed
Fix Version/s: 3.2.0
[
https://issues.apache.org/jira/browse/JAMES-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2572.
-
> Build fails on test-ja
> --
>
> Key: JAMES-2572
>
[
https://issues.apache.org/jira/browse/JAMES-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661586#comment-16661586
]
Tellier Benoit commented on JAMES-2557:
---
https://github.com/linagora/james-project/pull/1818 solved
JAMES-2334 avoid starting many dockers rabbitmq while only need one
RabbitMQTest and each nested class invokes rabbitMQExtension.beforeAll()
for their own. This leads to starting one docker rabbit for each test class.
Some moments, there are 3 dockers rabbit are up.
This commit addresses this
JAMES-2572 Always produce the test-jars (MJRA-138)
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/db992816
Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/db992816
Diff:
JAMES-2334 better name for default rate limiter
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/bc6eb256
Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/bc6eb256
Diff:
JAMES-2334 user one rabbit cluster across whole cluster test
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/e7f28f0c
Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/e7f28f0c
Diff:
JAMES-2456 Add content type to Tika logs
We have many non-contextualized logs from Tika client failing to execute some
requests.
Having the content type included in the lgos should help to diagnose what is
happening.
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit:
JAMES-2557 Correct MailAddress equality support for nullSender
Comparing a nullSender address with a non null sender address was throwing.
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/ebb74946
Tree:
JAMES-2334 Relax rabbitmq docker wait strategy
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/b1035f3e
Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/b1035f3e
Diff:
Repository: james-project
Updated Branches:
refs/heads/master cfca550ac -> db9928165
JAMES-2557 MailAddress.nullSender() support for SenderIs* matchers
These matchers were throwing upon nullSenders.
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit:
JAMES-2334 Reuse rabbitmq cluster after each test
- update extension to reuse rabbit cluster and make each rabbit
leave cluster & restart after each test
- move extension to nested class level to optimize test executing time
(each class makes RabbitMQ cluster start one time -> 3 class = three
[
https://issues.apache.org/jira/browse/JAMES-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat updated JAMES-2572:
--
Description:
The build fails sometimes on test-jars dependencies.
Antoine Duprat created JAMES-2572:
-
Summary: Build fails on test-ja
Key: JAMES-2572
URL: https://issues.apache.org/jira/browse/JAMES-2572
Project: James Server
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/JAMES-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660388#comment-16660388
]
ASF GitHub Bot commented on JAMES-2516:
---
GitHub user athulyaraj opened a pull request:
[
https://issues.apache.org/jira/browse/JAMES-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660351#comment-16660351
]
ASF GitHub Bot commented on JAMES-2570:
---
Github user trantienduchn closed the pull request at:
[
https://issues.apache.org/jira/browse/JAMES-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660350#comment-16660350
]
ASF GitHub Bot commented on JAMES-2570:
---
Github user trantienduchn commented on the issue:
[
https://issues.apache.org/jira/browse/JAMES-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660347#comment-16660347
]
ASF GitHub Bot commented on JAMES-2570:
---
GitHub user trantienduchn opened a pull request:
[
https://issues.apache.org/jira/browse/JAMES-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Duprat updated JAMES-2571:
--
Description:
Deprecate HBase, as:
* this implementation needs upgrade of dependencies
* lot of
Antoine Duprat created JAMES-2571:
-
Summary: Deprecate HBase
Key: JAMES-2571
URL: https://issues.apache.org/jira/browse/JAMES-2571
Project: James Server
Issue Type: New Feature
Hi,
According with what has been said, and without enough hands, we are
going to deprecate the HBase implementation.
It will be done in the next release, 3.2.0, coming in a few weeks.
Cheers,
Antoine
Le 06/05/2018 à 08:31, Eric Charles a écrit :
Hi James Community,
We have just
Trần Tiến Đức created JAMES-2570:
Summary: Upgrade com.sparkjava:spark-core from 2.6.0 to 2.8.0
Key: JAMES-2570
URL: https://issues.apache.org/jira/browse/JAMES-2570
Project: James Server
23 matches
Mail list logo