Re: Project jar file is no longer build after update?!

From: Christian Mittendorf (christian.mittendor..reenet.de)
Date: Thu Aug 21 2003 - 12:43:25 EDT

  • Next message: Kaj Hejer: "eclipse 3.0 and wolips 1.0.6: Exception when trying to view Help"

    Hi Ulrich,

    I finally found the bug after I checked all your hints. But none of
    them was
    necessary for my case. Instead I had a look at the .project file and
    compared
    it to a newly created project.

    My old .project had this content:

    <?xml version="1.0" encoding="UTF-8"?>
    <projectDescription>
             <name>FNEventPaymentBackoffice</name>
             <comment></comment>
             <projects>
             </projects>
             <buildSpec>
                     <buildCommand>
                              
    <name>org.objectstyle.wolips.targetbuilder.targetbuilder</name>
                             <arguments>
                             </arguments>
                     </buildCommand>
                     <buildCommand>
                             <name>org.objectstyle.wolips.antbuilder</name>
                             <arguments>
                             </arguments>
                     </buildCommand>
             </buildSpec>
             <natures>
                     <nature>org.eclipse.jdt.core.javanature</nature>
                      
    <nature>org.objectstyle.wolips.targetbuilder.targetbuildernature</
    nature>
                      
    <nature>org.objectstyle.wolips.antapplicationnature</nature>
             </natures>
    </projectDescription>

    while the newly created project looked in the first buildCommand like
    this:

                                    <buildCommand>
                             <name>org.eclipse.jdt.core.javabuilder</name>
                             <arguments>
                             </arguments>
                     </buildCommand>

    I have actually no idea how I got this targetbuilder entry in my
    .project
    file but perhaps this might help or at least give some hints to the
    developers.
    Any idea?

    Well, after fixing my .project file by replacing the class name, the
    project
    is now compiling fine as it should.

    Thanks for the help anyway ;-)

    cu
    cm

    On Thursday, August 21, 2003, at 05:43 PM, Ulrich Köster wrote:

    > Hi Christian,
    >
    > 1. Make sure the JavaBuilder is enabled.
    > Window->Preferences->Workbench->Automatically perform build on
    > resource modification.
    > 2. In the project java properties make sure that the output folder is
    > bin.
    > 3. Take a look in the error list. May be the classpath is corrupt or
    > something like that. Are there any red entries?
    > 4. Is this an old project? Created with 1.0.0 or prior? Open the
    > project wolips properties page and click ok.
    >
    > Ulrich
    > On Donnerstag, 21. August 2003, at 17:05 Uhr, Christian Mittendorf
    > wrote:
    >
    >> Hello,
    >> back from my holidays I updated wolips. But I now have a problem with
    >> getting my
    >> classes compiled. I get my woa application, everything works fine.
    >> But my apps
    >> jar file within the Java Resources folder does only contain a
    >> Manifest file -
    >> nothing else. I use WOLips 1.0.6 and Eclipse 2.1.1.
    >>
    >> Even the bin folder in my project is empty. There are no class files.
    >>
    >> Can anybody give me a hint on were to search or what to change in my
    >> project to fix this problem?
    >>
    >> Thanks!
    >>
    >> cu
    >> cm
    >>
    >
    >

    This archive was generated by hypermail 2.0.0 : Thu Aug 21 2003 - 12:34:20 EDT