[
https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9277:
------------------------------------
If I before said that deploy only should always be in started mode
then I'm stupid - I only remember deploy only mode having the problem of not being
able to be started - it just sat there and you had to manually invoke publish.
This is not true. The deploy only server had an automatic-success start method, and you
demanded, for your demos, that this was unacceptable and that it must start in
"started" mode at all times since it's only purpose is to deploy. You said
it hurt your demos to have to explain why you create a deploy only server, and then
"start" something that doesn't actually "start". You then directed
me to open a jira and change it. This was the jira:
https://issues.jboss.org/browse/JBIDE-8671
And honestly your point back then was completely valid. If a deploy-only server's only
job is to deploy, then it should begin in state 'started' and always be deploying,
and if the user does not want to deploy, then he should disable automatic publishing for
that server. But, as a deploy-only server is most-often used to deploy, it should default
to automatic publishing, and it can only do that when started.
I'm still not exactly sure what you want, or if what you want is possible. You
basically want two separate functions: having start/stop "connect or
disconnect", or having start/stop "actually start or stop" a server.
However having a start/stop who's only job is to "connect or disconnect"
basically just means publish or not publish... which is the exact same thing as turning
off automatic publishing for that server... no?
If I'm wrong I'd love to hear more thoughts on it, but for now I'm still
baffled as to what exactly you're looking for.
AS adapter does not enable polling when start/shutdown commands are
disabled
----------------------------------------------------------------------------
Key: JBIDE-9277
URL:
https://issues.jboss.org/browse/JBIDE-9277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Fix For: 3.3.0.M3
See my
[
comment|https://issues.jboss.org/browse/JBIDE-9093?focusedCommentId=12610...]
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira