[MAGNOLIA-4131] Activation doesn't work in integration tests Created: 16/Mar/12  Updated: 25/May/12  Resolved: 24/May/12

Status: Closed
Project: Magnolia
Component/s: activation, integration tests
Affects Version/s: 4.5
Fix Version/s: 4.5.3

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-3912 Jetty is failing because of increased... Closed
is depended upon by MAGNOLIA-4072 Provide script for testing of activat... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Comments   
Comment by Jan Haderka [ 02/Apr/12 ]

due to jetty issue with long headers. Once this issue is fixed activationTest.groovy in integration tests needs to be reactivated.

Comment by Jan Haderka [ 25/Apr/12 ]

it is possible to set custom length for headers. see http://jira.codehaus.org/browse/JETTY-336 (last comment)
And it's also possible to provide custom jetty.xml location http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin

Comment by Robert Šiška [ 24/May/12 ]

Add execution of activationTest.groovy script to POM.

Generated at Mon Feb 12 03:52:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.