History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CARGO-277
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Vincent Massol
Reporter: Ryan Sonnek
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Cargo

maven2 plugin: can't set container timeout

Created: 23/Feb/06 04:50 PM   Updated: 30/Mar/06 04:25 AM
Component/s: Maven2
Affects Version/s: 0.1-maven2
Fix Version/s: 0.2-maven2

Time Tracking:
Not Specified


 Description  « Hide
with the 0.7 release of the cargo plugin, I have been unable to set the timeout for the container. The default time is 1 min, and this is far too short for my server. I've searched through loads of examples, and i have yet to find documentation on what the maven2 plugin exposes for cargo properties.

I realize the default timeout has been increased to 2 min (http://jira.codehaus.org/browse/CARGO-273), but I need to customize this with the maven2 configuration.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Vincent Massol - 24/Feb/06 09:03 AM
Fixed and redeployed. Thanks.

Ryan Sonnek - 24/Feb/06 11:01 AM
please update the wiki (http://cargo.codehaus.org/Maven2+plugin) with this new information as well. It's too easy for this to get lost without this documentation.

Vincent Massol - 24/Feb/06 11:07 AM
Thanks Ryan. This is a good idea. Do you think you could help us and do this?

Our web site is a wiki after all! You simply need to go that page and click on the "Edit" link in the bottom right corner.

Thanks again for your help.


Ryan Sonnek - 24/Feb/06 11:48 AM
Done!

I didn't know that the site was actually a confluence instance.


Vincent Massol - 06/Mar/06 12:14 PM
Reopen to correct the affects field

Vincent Massol - 06/Mar/06 12:15 PM
Fixed the affects field

Vincent Massol - 06/Mar/06 12:16 PM
Fixed the affects field