Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Windows
Using HCL VersionVault build tools with Java
The build behavior of Java tools causes various problems for clearmake and omake. Understand the problems and some possible solutions to resolve them.
Using javac with clearmake or omake
You can use the javac compiler with clearmake or omake.

Managing change and releases
Learn how to manage change and release in the product.
- Managing software projects
- Workflow for creating projects
- Workflow for making baselines
- Workflow for recommending baselines
- Guide to building software on Linux and UNIX
- Guide to building software on Windows
  - VersionVault build concepts
    HCL VersionVault supports makefile based building of software systems and provides a software build environment closely resembling that of the make program.
  - Derived objects and configuration records
    Learn about derived objects and configuration records.
  - Pointers on using HCL VersionVault build tools
    Learn about how to use VersionVault build tools.
  - Working with DOs and configuration records
    You can perform operations on derived objects and configuration records.
  - clearmake makefiles and BOS files
    The HCL VersionVault build program, clearmake, can process makefiles.
  - Using clearmake compatibility modes
    clearmake is designed for compatibility with existing make programs, which minimizes the changes you need to make to your makefiles.
  - Using HCL VersionVault to build C++ programs
    Understand the guidelines and instructions to use the VersionVault build utilities, omake and clearmake, in C++ development environments such as Microsoft Visual C++. You will learn how the makefile fragment works and also present alternate possibilities for working around the problems.
  - Using HCL VersionVault build tools with Java
    The build behavior of Java tools causes various problems for clearmake and omake. Understand the problems and some possible solutions to resolve them.
    - Using make tools with javac
      You can use make tools with the javac compiler.
    - Using javac with clearmake or omake
      You can use the javac compiler with clearmake or omake.
      - HCL VersionVault build problems with javac
        HCL VersionVault problems with Java builds relate to conflicts between the dependency analysis of clearmake or omake and javac.
      - Using the clearmake makefile special target
        The .JAVAC target enables clearmake to use heuristics on audits of Java builds to accurately infer .class dependencies.
      - Unsupported builds
        clearmake does not support the use of the .JAVAC target with non-audited or parallel builds.
      - Makefile requirements for .JAVAC
        Makefile has some requirements when used with the .JAVAC special target.
      - Using the javaclasses built-in macro
        The $(javaclasses) function can be used to generate a list of .class targets, from existing .java files. The function takes one or two path arguments.
      - Deriving class dependencies
        clearmake stores or records the derived class dependencies.
      - Storing class dependencies
        Learn how clearmake stores or records the derived class dependencies.
      - Java cyclic class dependencies
        When clearmake detects a new .class dependency cycle, it marks the targets as being part of a target group.
      - Using .class.dep files
        clearmake uses the .class.dep file.
      - Dependencies and DO reuse/winkin
        Always delete the .class.dep files and .class files together. Avoid deleting only one of these types of files while leaving the other type.
      - Effects of nested classes
        Understand the effects of the nested classes.
      - .JAVAC in BOS files
        Learn more about the .JAVAC target.
      - .SIBLINGS_AFFECT_REUSE
        Understand the siblings DOs when using .JAVAC.
    - Building Java applications successfully without .JAVAC
      Learn how to build java applications without .JAVAC.
    - Java compilers and case-sensitivity issues
      Most Java compilers require that the case of file names exactly match the case of the class names in the Java source.
    - Auditing Ant builds
      Jakarta Ant is an open-sourced build tool for Java.
  - Setting up a parallel build
    Learn the process to set up and run parallel builds.

Using javac with clearmake or omake

You can use the javac compiler with clearmake or omake.

There are additional benefits of using clearmake or omake instead of make, especially given the building behavior of javac. clearmake and omake are better at determining when a rebuild is required than are the Java tools, with or without make.

When using dynamic views, clearmake or omake detects the following rebuild cases that javac does not:

Selection of an older version of a .java file. Because the rebuild decision is based on an older/newer comparison, javac does not detect that a rebuild is necessary.
Note: Clock skew between hosts can cause similar time stamp problems outside HCL VersionVault.
Change of the javac command line. If the command-line options used to build a .class file have changed since the last build, clearmake or omake rebuilds the .class file. For example, if you add the -g option to direct the compiler to rebuild with debugging information, you must invoke the compiler on all your .java files to ensure that they are rebuilt to contain the debugging information.
Manual winkin of a .class file that is out of sync with, but newer than, the corresponding .java source selected by the view. Because the rebuild decision is based on an older/newer comparison, javac does not detect that a rebuild is necessary.

However, some problems might arise when using HCL VersionVault build tools to perform Java builds.