Issue Details (XML | Word | Printable)

Key: MPAPPSERVER-7
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Peter Lynch
Reporter: Peter Lynch
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Maven 1.x AppServer Plugin

some properties do not play nice with maven console or reinvoked goals

Created: 25/Apr/04 02:22 PM   Updated: 25/Apr/04 04:27 PM  Due: 25/Apr/04
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Original Estimate: 2 hours
Original Estimate - 2 hours
Remaining Estimate: 2 hours
Remaining Estimate - 2 hours
Time Spent: Not Specified
Remaining Estimate - 2 hours


 Description  « Hide
A) maven appserver:install
1) start maven console in terminal A
2) at terminal A console, execute appserver:stop
Gives message like:
Maven has determined your <servername> appserver instance is
installed in directory <dirname> and not started using socket
<socketport> on host <appserver host>

3) execute maven appserver:start in terminal B, leaving console in A open
4) with appserver now started, execute appserver:stop in maven console again running in terminal A
5) message still says:
Gives message like:
Maven has determined your <servername> appserver instance is
installed in directory <dirname> and not started using socket
<socketport> on host <appserver host>

However server is now started.

This has to do with properties being set using ant the first time appserver:stop is called. Properties set by ant are not removable or resettable by design, so the solution is to set the properties via jelly.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Peter Lynch added a comment - 25/Apr/04 04:27 PM
Checking in plugin.jelly;
/home/cvs/maven-plugins/appserver/plugin.jelly,v <-- plugin.jelly
new revision: 1.9; previous revision: 1.8
done