Refactoring a component should work correctly provided you use the
"Refactor -> WO Component..." function to do it. I wrote the code in
wolips to do it, it works for me, I do it all the time.
On 20/01/2009, at 8:10 AM, Ray Kiddy wrote:
>
> I have filed bugs in JIRA about this. See http://issues.objectstyle.org/jira/browse/WOL-927
> . I provide links, in that bug, to the dozen or so other bugs that
> relate to this ball or yarn.
I don't see anything in there that relates directly to this issue. Can
you be more specific.
> The only way I have found to do this is:
>
> 1 - In eclipse, make a new component with the new name and then quit
> eclipse.
> 2 - Go to Terminal and copy and replace, and rename, the old
> component's api file, java file and the files inside the wo
> directory to the new location, overwriting those files.
> 3 - Launch eclipse and delete the WOComponent that you do not want.
>
> Be sure to make a copy of your entire project before you do this, as
> there are lots of ways to screw this up. And remember to replace the
> class name in your java and others places which you will find out
> about when you launch and get a run-time exception.
This shouldn't be necessary unless perhaps you are using a really,
really old version of wolips.
> Sucks, doesn't it? But this is literally the only way to do it that
> I have found that does not cause problems. One could theoretically
> do all of these changes in eclipse. It is tempting to try. But when
> you mess up, and you will occasionally mess up, eclipse will never
> give you back what you had. You may end up tearing down and re-
> building the whole project. So, really, I have found it is not worth
> it to try to do this in eclipse.
That's what revision control is for. You do use revision control?
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia (GMT+10) Ph: +61 419 729 806
This archive was generated by hypermail 2.0.0 : Mon Jan 19 2009 - 17:54:22 EST