9:04 a.m.
Brian Stansberry created AS7-5578:
-------------------------------------
Summary: Revisit handling of scanner-controlled deployments in the console
Key: AS7-5578
URL: https://issues.jboss.org/browse/AS7-5578
Project: Application Server 7
Issue Type: Sub-task
Components: Console
Reporter: Brian Stansberry
Assignee: Heiko Braun
Fix For: 7.2.0.CR1
The parent issue is resolved, meaning the problem of undeploying a scanner-controlled
deployment via the CLI or console just resulting in the next scan run deploying it again
is fixed. So, the console handling of such deployments should be revisited to see if the
console user should be allowed to do more things.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:02 a.m.
[
https://issues.jboss.org/browse/AS7-5578?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-5578:
----------------------------------
can you elaborate?
Revisit handling of scanner-controlled deployments in the console
-----------------------------------------------------------------
Key: AS7-5578
URL: https://issues.jboss.org/browse/AS7-5578
Project: Application Server 7
Issue Type: Sub-task
Components: Console
Reporter: Brian Stansberry
Assignee: Heiko Braun
Fix For: 7.2.0.CR1
The parent issue is resolved, meaning the problem of undeploying a scanner-controlled
deployment via the CLI or console just resulting in the next scan run deploying it again
is fixed. So, the console handling of such deployments should be revisited to see if the
console user should be allowed to do more things.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 a.m.
[
https://issues.jboss.org/browse/AS7-5578?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-5578.
-----------------------------------
Fix Version/s: (was: 7.2.0.CR1)
Resolution: Out of Date
Never mind; this was filed based on a memory of how the console worked at one point, and I
see the console in master now longer works this way.
At one point, the console wouldn't let you undeploy or remove filesystem deployments
because the scanner would just go and redeploy them on the next scan run. The patch for
the parent issue fixed that problem. But now I see the current console already lets you
undeploy/remove.
Revisit handling of scanner-controlled deployments in the console
-----------------------------------------------------------------
Key: AS7-5578
URL: https://issues.jboss.org/browse/AS7-5578
Project: Application Server 7
Issue Type: Sub-task
Components: Console
Reporter: Brian Stansberry
Assignee: Heiko Braun
The parent issue is resolved, meaning the problem of undeploying a scanner-controlled
deployment via the CLI or console just resulting in the next scan run deploying it again
is fixed. So, the console handling of such deployments should be revisited to see if the
console user should be allowed to do more things.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 a.m.
[
https://issues.jboss.org/browse/AS7-5578?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry edited comment on AS7-5578 at 10/12/12 12:19 PM:
------------------------------------------------------------------
Never mind; this was filed based on a memory of how the console worked at one point, and I
see the console in master no longer works this way.
At one point, the console wouldn't let you undeploy or remove filesystem deployments
because the scanner would just go and redeploy them on the next scan run. The patch for
the parent issue fixed that problem. But now I see the current console already lets you
undeploy/remove.
was (Author: brian.stansberry):
Never mind; this was filed based on a memory of how the console worked at one point,
and I see the console in master now longer works this way.
At one point, the console wouldn't let you undeploy or remove filesystem deployments
because the scanner would just go and redeploy them on the next scan run. The patch for
the parent issue fixed that problem. But now I see the current console already lets you
undeploy/remove.
Revisit handling of scanner-controlled deployments in the console
-----------------------------------------------------------------
Key: AS7-5578
URL: https://issues.jboss.org/browse/AS7-5578
Project: Application Server 7
Issue Type: Sub-task
Components: Console
Reporter: Brian Stansberry
Assignee: Heiko Braun
The parent issue is resolved, meaning the problem of undeploying a scanner-controlled
deployment via the CLI or console just resulting in the next scan run deploying it again
is fixed. So, the console handling of such deployments should be revisited to see if the
console user should be allowed to do more things.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4469
days inactive
4493
days old
3 comments
2 participants
participants (2)
-
Brian Stansberry (JIRA) -
Heiko Braun (JIRA)