Re: output/classes/* as CLASSES in PB.project

From: logan.allre..onvergys.com
Date: Thu Jan 27 2005 - 10:26:31 EST

  • Next message: christian mühlethaler: "change signatures for fields and methods"

    I have seen this happen as well, where the PB.project gets class files from
    the build directory listed as source files. It happened only
    intermittently, so I was never able to get a good test case for it.
    However, I was beginning to be suspicious that it only occurred after a
    search (as my search results would include files in the build directory). I
    noticed in the latest version of Eclipse, that when you do a search, there
    is now a checkbox to exclude derived files in your search, so maybe this
    was indeed the problem.

    WinXP Pro
    Eclipse 3.0.1
    WOLips 1.1.0.102RC3

    Logan Allred

                                                                                                                                                     
                          Kaj Hejer
                          <kaj.heje..sit.u To: Ulrich Köster <ulric..bjectstyle.org>
                          io.no> cc: WOProject List <woproject-de..bjectstyle.org>
                                                   Subject: Re: output/classes/* as CLASSES in PB.project
                          01/27/2005 01:40
                          AM
                                                                                                                                                     
                                                                                                                                                     

    Hi!

    I have checked with some of other ppl here at the University of Oslo
    using eclipse and WOLips and they too see this issue. This goes for
    both osx and windows users.

    Today I installed wolips 1.1.0.105 and I see this issue with this
    version too.

    It seems that wolips include .class-files from the directory "output"
    in PB.project when that directory exists in the projectdiectory.

    -Kaj :)

    On 3. jan 2005, at 20.09, Kaj Hejer wrote:

    > Some more info...
    >
    > The directory output/classes is created when I build the project with
    > ant from the commandline. When developling I'm using incremental
    > builder in eclipse.
    >
    > When I delete the output directory and then update the PB.project file
    > the output/classes/*.class stuff is not included (which is not so
    > strange since the files isn't there :)
    >
    > When I then build the project again from the commendline and the
    > output-directory is created I get the output/classes/*.class stuff
    > back again when updating PB.project.
    >
    >
    > -Kaj :)
    >
    >
    >
    >
    > On 3. jan 2005, at 19.12, Ulrich Köster wrote:
    >
    >> Moin Kaj,
    >>
    >> can't reproduce it. Neither with 3.0.2 nor with 3.1M4.
    >>
    >> Did you try to "Update PB.project" from the projects context menu?
    >>
    >> Uli
    >> Am 03.01.2005 um 17:40 schrieb Kaj Hejer:
    >>
    >>> Hi!
    >>>
    >>> I get all my classes (output/classes/*) included in as CLASSES in
    >>> PB.project
    >>>
    >>> I'm using the latest WOLips from cvs (1.1.0.96) and eclipse 3.0.1.
    >>>
    >>> kajh$ cat classes.include.patternset
    >>> **/*.class
    >>> *.properties
    >>>
    >>> kajh$ cat classes.exclude.patternset
    >>> build.properties
    >>>
    >>>
    >>> Any ideas how I make WOLips not include all the files from
    >>> output/classes/* in the PB.project file?
    >>>
    >>>
    >>> -Kaj :)
    >>>
    >>
    >



    This archive was generated by hypermail 2.0.0 : Thu Jan 27 2005 - 10:20:37 EST