As I said, it all really boils down to the situation. There are a lot
of factors to consider when decided if its beneficial to use Eclipse
RCP, nature of the project, number of programmers, methodology of the
shop, design of the app, etc.
Eclipse RCP brings with it a set of ready-made components, design and
methodologies to use. More importantly, it is what I like to think of
as the "geek standard". And 10,000 geeks can't be wrong :).
>From the sounds of it however, your project is a one man job, probably
not a large (note: relatively used of course) project and you wouldn't
be envisioning much revisions, updates, redesign etc? In this case, I
definately would not use Eclipse RCP, but fire off the gui yourself
using Swing/SWT and go from there. HOWEVER, if the project is expected
to grow, or you are planning for that possibility, you may want to bite
the bullet and go with Eclipse RCP now. Extra time spent now, saves
tonnes more down the road.
As for what Eclipse RCP brings to the table, it brings nothing special
at unless you use the features. :) i.e. what is sense of having an
update system if you don't plan on releasing any updates.