The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Sat, 17 Apr 2004 7:27 AM
Changes:
assignee changed from Cactus Developers Mailing List to Vincent Massol
description changed from The cactus plugin offers a property named
cactus.port. This property contains
the port to which it should connect to start the tests.
Chaging the cactus.port to 8880 does not change the URL being invoked by the plugin.
I can provide a patch that solves this issue, provided you give me a path to the
sources I have to patch. to The cactus plugin offers a property named cactus.port.
This property contains
the port to which it should connect to start the tests.
Chaging the cactus.port to 8880 does not change the URL being invoked by the plugin.
I can provide a patch that solves this issue, provided you give me a path to the
sources I have to patch.
environment changed from Operating System: Other
Platform: All to Operating System: Other
Platform: All
priority changed to Blocker
Fix Version changed to 1.6
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-86?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-86
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-86
Summary: jboss port is not changed if cactus.port is used
Type: Bug
Status: Open
Priority: Blocker
Project: Cactus
Components:
Maven Integration
Fix Fors:
1.6
Versions:
unspecified
Assignee: Vincent Massol
Reporter: Stephane Nicoll
Created: Thu, 8 Jan 2004 12:43 PM
Updated: Sat, 17 Apr 2004 7:27 AM
Environment: Operating System: Other
Platform: All
Description:
The cactus plugin offers a property named cactus.port. This property contains
the port to which it should connect to start the tests.
Chaging the cactus.port to 8880 does not change the URL being invoked by the plugin.
I can provide a patch that solves this issue, provided you give me a path to the
sources I have to patch.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
