out-of-the-box build issues in trunk

[Anthony Penniston <ap...@pivotal.io>]

Hi,
Currently, we are having trouble building ambari out-of-the-box.
according to the developer documentation (
https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development) , we
first run:

mvn versions:set -DnewVersion=1.6.1

However, the version number set here, "1.6.1", fails the version regex in
the <package-version> and <package-release> elements.
So it is first necessary for us to change the regex so that alphanumerics
are optional at the end of the version number:

<regex>^([0-9]+)\.([0-9]+)\.([0-9]+)(\.|-).*</regex>
becomes
<regex>^([0-9]+)\.([0-9]+)\.([0-9]+)((\.|-).*)?</regex>
and
<regex>^([0-9]+)\.([0-9]+)\.([0-9]+)(\.|-)(([0-9]+)|(SNAPSHOT)).*</regex>
becomes
<regex>^([0-9]+)\.([0-9]+)\.([0-9]+)((\.|-)(([0-9]+)|(SNAPSHOT)).*)?</regex>

This allows the build to at least now succeed past the version regex.
However it then fails again on the Rat check. While concerning, currently
we are simply trying to get a build going, so we again modify the pom.xml
and add a wildcard exclusion to silence the rat:
<exclude>*.*</exclude>

sadly, the build is still failing (currently on pulling angular from git,
and other reasons we are investigating). We thought we'd try this mailing
list to report the initial build fails and their fixes, and ask why the
project is failing to build out-of-the-box on trunk? we tried both the repo
linked in the wiki and the github repo.

Re: out-of-the-box build issues in trunk

[Yusaku Sako <yu...@hortonworks.com>]

Hi Anthony,

Per the Wiki that you referred to [1], the version has to be a 4-digit
number (like 1.6.1.0).
Please try that and see if you still encounter issues.

[1] https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development

Thanks,
Yusaku

On Mon, Aug 18, 2014 at 11:06 AM, Anthony Penniston
<ap...@pivotal.io> wrote:
> Hi,
> Currently, we are having trouble building ambari out-of-the-box.
> according to the developer documentation (
> https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development) , we
> first run:
>
> mvn versions:set -DnewVersion=1.6.1
>
> However, the version number set here, "1.6.1", fails the version regex in
> the <package-version> and <package-release> elements.
> So it is first necessary for us to change the regex so that alphanumerics
> are optional at the end of the version number:
>
> <regex>^([0-9]+)\.([0-9]+)\.([0-9]+)(\.|-).*</regex>
> becomes
> <regex>^([0-9]+)\.([0-9]+)\.([0-9]+)((\.|-).*)?</regex>
> and
> <regex>^([0-9]+)\.([0-9]+)\.([0-9]+)(\.|-)(([0-9]+)|(SNAPSHOT)).*</regex>
> becomes
> <regex>^([0-9]+)\.([0-9]+)\.([0-9]+)((\.|-)(([0-9]+)|(SNAPSHOT)).*)?</regex>
>
> This allows the build to at least now succeed past the version regex.
> However it then fails again on the Rat check. While concerning, currently
> we are simply trying to get a build going, so we again modify the pom.xml
> and add a wildcard exclusion to silence the rat:
> <exclude>*.*</exclude>
>
> sadly, the build is still failing (currently on pulling angular from git,
> and other reasons we are investigating). We thought we'd try this mailing
> list to report the initial build fails and their fixes, and ask why the
> project is failing to build out-of-the-box on trunk? we tried both the repo
> linked in the wiki and the github repo.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.