[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

2007-05-03 Thread Donald Woods (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Woods updated GERONIMO-1285:
---

Fix Version/s: (was: 2.0-M5)
   2.0-M6

 Deployer does not list all modules that have been stopped
 -

 Key: GERONIMO-1285
 URL: https://issues.apache.org/jira/browse/GERONIMO-1285
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 1.0-M5
Reporter: Aaron Mulder
 Assigned To: Donald Woods
Priority: Critical
 Fix For: 2.0-M6

 Attachments: consoleprint1285.patch, deploytooloutput.patch


 When you, for example, stop the tomcat configuration, all the web apps 
 deployed to Tomcat are stopped too.  However, the deployer does not let you 
 know this.  It should list all modules that were stopped, just like it does 
 when starting.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

2006-12-06 Thread Rakesh Midha (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Rakesh Midha updated GERONIMO-1285:
---

Attachment: consoleprint1285.patch


Patch consoleprint1285.patch prints the same for console. It prints started, 
stopped, uninstalled and installed module names in console.



 Deployer does not list all modules that have been stopped
 -

 Key: GERONIMO-1285
 URL: http://issues.apache.org/jira/browse/GERONIMO-1285
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 1.0-M5
Reporter: Aaron Mulder
 Assigned To: Rakesh Midha
Priority: Critical
 Fix For: 2.0

 Attachments: consoleprint1285.patch, deploytooloutput.patch


 When you, for example, stop the tomcat configuration, all the web apps 
 deployed to Tomcat are stopped too.  However, the deployer does not let you 
 know this.  It should list all modules that were stopped, just like it does 
 when starting.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

2006-12-06 Thread Rakesh Midha (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Rakesh Midha updated GERONIMO-1285:
---

Assignee: (was: Rakesh Midha)


I did both the items I was thinking to do for this JIRA. Added patch for deploy 
tool as well as console to prnt all the module names stopped, started, 
uninstalled

Marking patch available, unassigning so that someone can review and commit

 Deployer does not list all modules that have been stopped
 -

 Key: GERONIMO-1285
 URL: http://issues.apache.org/jira/browse/GERONIMO-1285
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 1.0-M5
Reporter: Aaron Mulder
Priority: Critical
 Fix For: 2.0

 Attachments: consoleprint1285.patch, deploytooloutput.patch


 When you, for example, stop the tomcat configuration, all the web apps 
 deployed to Tomcat are stopped too.  However, the deployer does not let you 
 know this.  It should list all modules that were stopped, just like it does 
 when starting.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

2006-11-23 Thread Rakesh Midha (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Rakesh Midha updated GERONIMO-1285:
---

Attachment: deploytooloutput.patch


Attached patch to print child modules and patent modules with deploytool 
start/stop

 Deployer does not list all modules that have been stopped
 -

 Key: GERONIMO-1285
 URL: http://issues.apache.org/jira/browse/GERONIMO-1285
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment
Affects Versions: 1.0-M5
Reporter: Aaron Mulder
 Assigned To: Rakesh Midha
Priority: Critical
 Fix For: 2.0

 Attachments: deploytooloutput.patch


 When you, for example, stop the tomcat configuration, all the web apps 
 deployed to Tomcat are stopped too.  However, the deployer does not let you 
 know this.  It should list all modules that were stopped, just like it does 
 when starting.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

2006-06-30 Thread Aaron Mulder (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Aaron Mulder updated GERONIMO-1285:
---

Assign To: (was: Aaron Mulder)

 Deployer does not list all modules that have been stopped
 -

  Key: GERONIMO-1285
  URL: http://issues.apache.org/jira/browse/GERONIMO-1285
  Project: Geronimo
 Type: Bug
 Security: public(Regular issues) 
   Components: deployment
 Versions: 1.0-M5
 Reporter: Aaron Mulder
 Priority: Critical
  Fix For: Verification Required


 When you, for example, stop the tomcat configuration, all the web apps 
 deployed to Tomcat are stopped too.  However, the deployer does not let you 
 know this.  It should list all modules that were stopped, just like it does 
 when starting.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

2006-06-08 Thread Matt Hogstrom (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Matt Hogstrom updated GERONIMO-1285:


Fix Version: Verification Required
 (was: 1.1)

 Deployer does not list all modules that have been stopped
 -

  Key: GERONIMO-1285
  URL: http://issues.apache.org/jira/browse/GERONIMO-1285
  Project: Geronimo
 Type: Bug
 Security: public(Regular issues) 
   Components: deployment
 Versions: 1.0-M5
 Reporter: Aaron Mulder
 Assignee: Aaron Mulder
 Priority: Critical
  Fix For: Verification Required


 When you, for example, stop the tomcat configuration, all the web apps 
 deployed to Tomcat are stopped too.  However, the deployer does not let you 
 know this.  It should list all modules that were stopped, just like it does 
 when starting.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

2006-04-26 Thread Aaron Mulder (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Aaron Mulder updated GERONIMO-1285:
---

Fix Version: 1.1
 (was: 1.2)

Review status as of current 1.1 build

 Deployer does not list all modules that have been stopped
 -

  Key: GERONIMO-1285
  URL: http://issues.apache.org/jira/browse/GERONIMO-1285
  Project: Geronimo
 Type: Bug
 Security: public(Regular issues) 
   Components: deployment
 Versions: 1.0-M5
 Reporter: Aaron Mulder
 Assignee: Aaron Mulder
  Fix For: 1.1


 When you, for example, stop the tomcat configuration, all the web apps 
 deployed to Tomcat are stopped too.  However, the deployer does not let you 
 know this.  It should list all modules that were stopped, just like it does 
 when starting.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Updated: (GERONIMO-1285) Deployer does not list all modules that have been stopped

2005-12-10 Thread Aaron Mulder (JIRA)
 [ http://issues.apache.org/jira/browse/GERONIMO-1285?page=all ]

Aaron Mulder updated GERONIMO-1285:
---

Fix Version: 1.1
 (was: 1.0)

Seems like it would need a fairly extensive change for Configuration or Kernel 
calls to return a list of GBeans or Configurations that were stopped, so that 
the ConfigurationManagerImpl could return a list of Configurations that were 
stopped, so that the JSR-88 impl could list them in the progress object.

 Deployer does not list all modules that have been stopped
 -

  Key: GERONIMO-1285
  URL: http://issues.apache.org/jira/browse/GERONIMO-1285
  Project: Geronimo
 Type: Bug
   Components: deployment
 Versions: 1.0-M5
 Reporter: Aaron Mulder
 Assignee: Aaron Mulder
  Fix For: 1.1


 When you, for example, stop the tomcat configuration, all the web apps 
 deployed to Tomcat are stopped too.  However, the deployer does not let you 
 know this.  It should list all modules that were stopped, just like it does 
 when starting.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira