4 Replies Latest reply on Oct 20, 2009 2:22 PM by Rob Stryker

    Where is a "clear" button?

    Piotr Sobczyk Newbie

      Despite I have JBossTools installed I still use standard "Servers View" more often that "JBoss Server View". Why? Because it has very useful "clear" button that just removes the application from AS and deploys it again - something that programmer need more often that restarting AS.

      I know I can do it from "JBoss Server View" deleting application in "Explore" window and redeploying it by using Add/Remove option but it takes a lot more time and clicking!

      Why the heck was "Clear" button not derived from standard "Servers" view like other buttons? And what is "Publish" button for? It seems that most of time it does just nothing.

        • 1. Re: Where is a
          Rob Stryker Master

          Hmm... I'm not sure when they added 'clean' so I don't think it was there when I 'forked', but honestly, the history of the JBoss Servers View was that it was a Common Navigator based view. At the time of the fork, the official "Servers View" was not common navigator based but was rather a static view that could not be added to at all.

          I later contributed a large base of code back to eclipse to convert their view to an extensible Common Navigator based view.

          In all honesty what I *should* be working on now is removing the JBoss Servers View entirely and adding the extra actions which we have to their view. But I can add the clean action to my view temporarily until I get around to removing the JBoss Servers View entirely =] I should make some JIRAs for myself.

          • 2. Re: Where is a
            Rob Stryker Master

            As for what "publish" does, some people run with the automatic publishing NOT enabled. This means when they make changes to their workspace, they do NOT publish the changes right away. These users love being in control of when the publish occurs, and prefer to have the button there to do it.

            What the "publish" button does is initiate an incremental publish. If you already have automatic publishing turned on, then clicking the publish button likely won't do anything because by the time you click it, an automatic publish has probably already happened and the workspace is already in sync with the publish folder.

            But for users who don't have automatic publishing turned on, clicking publish initiates this incremental change. So if you change 10 files with auto-publish turned off, you'll see nothing changes in your deploy folder, but the "resynchronize" is shown in the view, showing you they are not in sync right then.

            Then you click publish, and those 10 files are published =]

            • 3. re: where is a
              Piotr Sobczyk Newbie

              Rob, thanks for thorough answer, now I understand why "clean" button is not here.

              But I can add the clean action to my view temporarily until I get around to removing the JBoss Servers View entirely =]


              It would be really cool! :)

              As for what "publish" does, some people run with the automatic publishing NOT enabled. This means when they make changes to their workspace, they do NOT publish the changes right away. These users love being in control of when the publish occurs, and prefer to have the button there to do it.


              Hey, I didn't know about this! I will also switch for manual publishing, because system slowing down for several seconds every time I save is very irritating. I wish I knew about such option earlier but anyways good to know. And would id be hard to make JBoss Tools deploy application automatically when it's "dirty" (not synchronized with AS) and user wants to launch as opposed to everytime he saves it?


              • 4. Re: Where is a
                Rob Stryker Master

                We have a bug opened on eclipse webtools / servertools to add automatic publish on BUILD events.

                I do not think they will accept the idea of automatic publishing on LAUNCH. I don't think that fits in very well with the current options. Also it took a bit of fighting to get WTP to add the on-build so I think it would take even longer for on-launch!