[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3767) allow single click publish

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12505307#action_12505307 ] 

Rob Stryker commented on JBIDE-3767:
------------------------------------

>> First, why are you in need of full publish ? The content should be publishing on every save anyway 

Full publish is there in case (god forbid) the deployment is messed up and needs to be completely republished.  It's basically a shortcut to removing the module and then re-adding the module. Instead of just updating the changes, it would update the entire module. Some users find this valuable. I know I do. 

>> with you running in archive mode touch of jboss-esb.xml not needed since the archive it self is being updated.
If you're running in archive mode, sure touching the xml is not necessary. If you're not running in archive mode, it is necessary. Therefore, we touch the xml file. I am not sure why this is a problem? When should we *not* be touching the xml file? Are there a specific class of changes that we shouldn't be updating the xml file for? This seems like a different issue altogether. 

>>    - New Custom Actions do not seem to publish 
This seems very vague. Are the files not copied into the deployment, or is the runtime not recognizing them?

>> Sometimes updates to jboss-esb.xml publish at inopportune times, 
This is just how it works. If you don't want automatic publishing, then turn it off.  I'm trying to get upstream to accept a new option for autopublish to only go on BUILD events rather than save events, but upstream is SLOW AS BALLS at integrating or approving my patch and it angers me. 

>> So even with the bug fixed concerning classes not being deployed properly for some having a shortcut key or direct clickable button for both publish and incremental publish seems to me very valid. 

I still fail to see how having an icon in the view for "full publish" is much better than right-clicking the module and selecting full publish. Let's analyze this a bit. 

First, let's discuss hotkeys. There are two options with hotkeys. A hotkey with a selection, and a hotkey without a selection. 

A hotkey without a selection is, quite frankly, not doable at all. The reason is because many workspaces have several servers, and each server may have several modules. This hotkey would have absolutely no idea which server you want to target, and more importantly which module under that server you want to FULL PUBLISH.  If there are 5 servers and each has 3 child modules, I have no idea what this FULL PUBLISH hotkey should do without a selection. Sorry. We need a selection. 

A hotkey with a selection, however, is exactly as much work as the current UI / flow is. In order to select the proper module, you'd need to open the server view, expand it, and select the proper child module.  This is all done using the mouse.  In the current workflow, you then keep your hand on the mouse, right-click that module, and select FULL PUBLISH.  In the suggested workflow, you then remove your hand from the mouse, place it on the keyboard, and enter a most-likely complex hotkey (all the simple ones are taken). I and many studies have found that when the first half of a workflow involves the mouse, you should maintain the second half using the mouse if it's just one or two more clicks, especially when it looks like the user will immediately put their hand right back on the mouse after executing that hotkey (to then switch to an editor or other view). 

The other option is of course a button at the top of the view for full publish. But there are several problems with this. First, those buttons all must subclass ServerAction, and unfortunately ServerAction *only* accepts IServer objects, not the child modules. What this means is you wouldn't be able to FULL PUBLISH a single module, but only a server (which would full publish ALL modules deployed to it). I've suggested, again, patches upstream to allow the regular publish icon to work for IModule objects, but upstream enjoys ignoring me. 

However, even if we could get a "Full Publish" button at the top of the view, it suffers from the same problems the hotkey does. The user would still need to activate the Server view, expand their chosen server, and select their module. The only difference, again, is that with a button at the top, the user would single-click the module, then single-click the button.  In the current workflow, the user right-clicks the module, then single clicks Full Publish.  Both of these involve two clicks.

The only things I can imagine doing to cut down on clicks (hotkey, magic button) have no way of knowing which module you want to fully publish. The only way to clue these in is via selection, and once you've gone through the trouble of selecting the module, the hotkey and publish button provide no click-count benefit vs the right-click followed by Full Publish. 

I'm not sure what you'd want me to do that could possibly speed this up. Every case requires a selection. 


> allow single click publish
> --------------------------
>
>                 Key: JBIDE-3767
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3767
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>    Affects Versions: 3.0.0.GA
>            Reporter: arne anka
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 3.1.0.CR2
>
>
> to publish incremental or full, several clicks are necessary:
> expand server -> select project -> select menu entry -> click.
> eve if the project is preselected, right click -> select entry -> click is still required.
> it would be nice, if those task could be solved by a single clik -- like the "publish to server" icon, which could be active even if a project is selected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira