Re: possible bug in wolips with refactoring

From: Mike Schrag (mschra..dimension.com)
Date: Tue Sep 26 2006 - 11:04:00 EDT

  • Next message: Ulrich Köster: "Re: WO profiling w/Eclipse?"

    Hmm ... Back in the day (i.e. like month #2 of me working on wolips)
    I added refactoring support for setting the package name in right-
    click-on-project=>Properties=>WOLips Build=>Principal Class. I'm not
    sure where this data actually writes? Anyone happen to know if the
    value that appears here is read from build.properties or if they are
    different? I have never specifically done anything to update
    build.properties unless it is the backing store for that value. If
    they show different values for you, then I need to add explicit
    support for refactoring the build.properties file, probably. If they
    are both wrong, then refactoring that value has just been broken over
    time somehow.

    ms

    On Sep 26, 2006, at 10:01 AM, Markus Ruggiero wrote:

    > This is maybe a bug in WOLips? 2.0.0.3344
    >
    > create a WOApp, then create a package into which you move
    > Application.java. Eclipse correctly add the package statement to
    > the file and also build.properties reflects the package info for
    > the principal class. Later on decide to rename the package by doing
    > it with refactor->rename. Everything is fine eclipse wise, however
    > build.properties is not adjusted and still references the old
    > package name for Application.java
    >
    > Known issue?
    > ---markus---
    >
    > Don't miss my latest project at http://blindpromo.com
    >
    > Markus Ruggiero
    > rucotec consulting and technologies email
    > mailto:markus.ruggier..ucotec.ch
    > rucotec GmbH web http://www.rucotec.ch
    > Steinentorstrasse 8
    > 4051 Basel Mobile +41 (0)79 508 4701
    > Switzerland Phone/Fax +41 (0)61 271 4990
    >
    >



    This archive was generated by hypermail 2.0.0 : Tue Sep 26 2006 - 11:04:04 EDT