Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <5955C49C.9020902@gmail.com>
Date: Thu, 29 Jun 2017 22:25:16 -0500
From: Timothy Nodine <timgnodine@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: dev@activemq.apache.org
Subject: Re: [HELP] maven build smoke-test bootstrapping.
References: <595551E4.1040608@gmail.com> <CAKF+bsq31s7cNrp-m4zbsMJ_sCz7j9DV9-+DOzzXBUs3iprUGg@mail.gmail.com>
In-Reply-To: <CAKF+bsq31s7cNrp-m4zbsMJ_sCz7j9DV9-+DOzzXBUs3iprUGg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Fri, 30 Jun 2017 03:25:28 -0000

Are the smoke tests not supposed to be under the root directory during a 
build?

Clebert Suconic wrote:
> You have to first build the project at the root.
>
> The smoke tests needs the distribution built.  It is a smoke test hence it
> acts on the servers directly.
>
> On Thu, Jun 29, 2017 at 3:16 PM Timothy Nodine <timgnodine@gmail.com> wrote:
>
>   
>> I attempted a maven build from scratch and it failed; I got the
>> following error message in the smoke tests:
>>
>> [ERROR] Could not locate suitable Artemis.home on either [directory
>> redacted] or [directory redacted]
>> [ERROR] Use the binary distribution or build the distribution before
>> running the examples
>>
>> In other words, the build failed because it had not already succeeded.
>>
>> This is easy enough to fix by itself, by building with tests disabled
>> and then building again with tests enabled.
>>
>> However, it hints that, if I use a workaround, the smoke tests will not
>> function correctly inside maven. They will test the previous build
>> instead of the current build.
>>
>> Can I get some clarity on how I should use the smoke tests?
>>
>>
>> (Version - 2.2.0-SNAPSHOT taken on June 20)
>>
>>