trafodion-codereview mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robertamarton <>
Subject [GitHub] incubator-trafodion pull request: [TRAFODION-1612] and [TRAFODION-...
Date Wed, 11 Nov 2015 01:46:09 GMT
GitHub user robertamarton opened a pull request:

    [TRAFODION-1612] and [TRAFODION-1613]


You can merge this pull request into a Git repository by running:

    $ git pull releaseb

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #168
commit 9070a6d79e7bd5a4552fb8e44666facf064ec5b3
Author: Roberta Marton <>
Date:   2015-11-02T18:55:28Z

    Merge TRAFODION-1569 Release package has missing and imcomplete files

commit 1ff1fa25264ea92d77950328d81a6eb9b3076ab0
Author: Roberta Marton <>
Date:   2015-11-11T01:40:44Z

    Trafodion-1612 and Trafodion-1613
    1612: Stop building HBase-trx for MAPR, due to instable Maven repository
    - removed mapr from the build_all step in the hbase_trx Makefile, we now create
      6 jar files instead of 7
    1613: build failing due to mismatched Maven downloads
    When building Trafodion from source objects, Maven is required.  It is not
    possible to download Maven from yum, instead it needs to be installed. There
    are a few problems related to how Maven is managed with Trafodion builds.
    - In many environments, Maven is already installed.  The check to see if Maven
      is already installed is commented out in This has been
    - Today, checks to see if mvn is installed, if not, it sets it to
      version 3.0.5 but we install 3.3.3. Changed the code to return an error:
      "ERROR unable to find mvn (MAVEN) in path" to inform the user that mvn needs
      to be added to the path before building. An error is also returned during
      the build (make) if mvn is not found in the path.
    - As part of the above change, it was noted that many of the tools were being
      set to the value of $TOOLSDIR when $TOOLSDIR may not be set.  Checks were
      added to see if the environment variable was already set. This allows
      someone to specify a different location for these tools as described in the
      additional build tools wiki page.
    - Changed the output returned in  BISON does not have to be in
      the path but needs to be specified correctly in the environment variable.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message