Compiere rebuild

oliver79
2006-09-03
2013-05-02
  • oliver79

    oliver79 - 2006-09-03

    Hi all:

    Having viewed this forum, and searched through the threads I'm still having great difficulty in importing and compiling compiere in Eclipse! I have downloaded compiere-all zip and imported into a new Eclipse project, however in the package view it displays hundreds of errors and warnings!

    Plus I'm unfamiliar with the following steps:

    Note that you need outside of Eclipse in the utils_dev directory

        * Copy script myDevEnvTemplate.bat/sh to
          myDevEnv.bat/sh
        * Modify script myDevEnv for your environment
        * Use RUN_build to build compiere.
        o Building Compiere with 1.5 will create
          warnings, but no errors.

    Could anyone provide assistance? Would greatly appreciate some input.

    Thanks

    Oliver

     
    • Igor Almeida

      Igor Almeida - 2006-09-06

      The steps below are used for compilation via console.

      * Copy script myDevEnvTemplate.bat/sh to 
      myDevEnv.bat/sh
      * Modify script myDevEnv for your environment
      * Use RUN_build to build compiere.
      o Building Compiere with 1.5 will create
      warnings, but no errors.

      In Eclipse or Netbeans, most of the error messages are related to not imported libraries. The ones I used are located mainly at 'compiere-all/lib', 'compiere-all/jboss/lib', 'compiere-all/tools/lib'

       
    • Dennis McRitchie

      Hi,

      Here's how I have imported a new Compiere release into Eclipse 3.0 in the past.

      1) Export the desired release from the SourceForge CVS repository.

      2) Build, install, and configure it using the usual scripts: RUN_build, RUN_install, and RUN_setup.

      3) If top-level .project and .classpath files do not exist in that release, use the most recent ones from a previous PSR release, from Red1's Compilo SourceForge project, or from user contributions on the Compiere development discussion group. Manually edit the <projects> section to remove any obsolete projects (missing first-level directories), and to add any new projects (new first-level directories with a .project file). Also give it a unique <name> and any <comment> desired.

      4) Start Eclipse

      5) When prompted for the workspace to use, create a new workspace for this project. Do not select "Use this as a default...", to make it easier to switch between PSR releases when starting Eclipse.

      6) Click on File | Import, then select "Existing Project into Workspace", click on Next, and browse to the directory containing the top-level .project file. Then click on Finish.

      7) Eclipse will then attempt to build the project and report errors in the Problems pane.

      8) Correct the errors due to missing jar files by clicking on Project | Properties. Click on Java Build Path, and use Add Jars and/or Add Class Folder as needed.

      9) If any errors are due to XML validation, then it may be due to the MyEclipse plug-in's Validation Builder (see Project | Properties | Builders; there only needs to be only Java Builder there). To remove the XML validation errors, right-click on the project name in the Navigator pane, then click on MyEclipse | Remove All Validation Markers. (You may also want to close Eclipse, and manually edit the top-level .project file to remove the MyEclipse validator builder from the <buildSpec> section.)

      10) To remove most of the CVS-related warnings, right-click on the project name in the Navigator pane, then click on Team | Share Project. There select CVS as the repository provider, enter the CVS connection credentials, and click Finish.

      11) To remove unused import warnings, click on Window | Preferences | Java | Compiler | Unused Code, and set "Unused imports" to "Ignore".

      12) To clear out obsolete errors and warnings and rebuild the project, click on Project | Clean.

      13) There should now only be a handful of "resource is a duplicate" warnings. To remove these, use the Problems panel's Filters tool (its icon is on the right-hand side of the title bar containing the Problems tab). Select Where description does not contain "resource is a duplicate", and click OK.

      14) Exit and restart Eclipse, and you should see no Problems, and can begin working.

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks