Including tests in releases ( was: Release Apache Sling Scripting Sightly JS Use Provider 1.0.4)

[Robert Munteanu <ro...@apache.org>]

Hi Radu,

On Thu, Apr 9, 2015 at 7:46 PM, Radu Cotescu <ra...@apache.org> wrote:
>
> The repository contains:
> org.apache.sling.scripting.sightly.js.provider-1.0.4
> org.apache.sling.scripting.sightly.testing-content-1.0.4
> org.apache.sling.scripting.sightly.testing-1.0.4

Out of curiosity, why do you include tests in releases? We typically
don't release them as they are executed as part of the reactor builds
anyway.

Not that it matters or it costs, but you made me curious :-)

Thanks,

Robert

Re: Including tests in releases ( was: Release Apache Sling Scripting Sightly JS Use Provider 1.0.4)

[Robert Munteanu <ro...@apache.org>]

On Fri, Apr 10, 2015 at 1:16 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Hi,
>
> On Fri, Apr 10, 2015 at 11:39 AM, Radu Cotescu <ra...@apache.org> wrote:
>> ...If my memory serves me well I think I took this decision after a private
>> discussion with Bertrand where he advised to me release these artifacts as
>> well...
>
> Yes, I usually release the tests module as well - if our grandchildren
> want to rebuild and validate a specific version of a Sling module 50
> years from now, they will need them ;-)
>

Thanks to both of you for the information, quite useful.

Cheers,

Robert

Re: Including tests in releases ( was: Release Apache Sling Scripting Sightly JS Use Provider 1.0.4)

[Bertrand Delacretaz <bd...@apache.org>]

Hi,

On Fri, Apr 10, 2015 at 11:39 AM, Radu Cotescu <ra...@apache.org> wrote:
> ...If my memory serves me well I think I took this decision after a private
> discussion with Bertrand where he advised to me release these artifacts as
> well...

Yes, I usually release the tests module as well - if our grandchildren
want to rebuild and validate a specific version of a Sling module 50
years from now, they will need them ;-)

-Bertrand

Re: Including tests in releases ( was: Release Apache Sling Scripting Sightly JS Use Provider 1.0.4)

[Radu Cotescu <ra...@apache.org>]

Hi Robert,

If my memory serves me well I think I took this decision after a private
discussion with Bertrand where he advised to me release these artifacts as
well.

I'd argue that releasing the tests artifacts helps tracking down bugs
easier, as tests are extended every time we fix something. Otherwise, if
you try to prove that a bug exists on a release using SNAPSHOT tests
artifacts you might actually run tests for something that's not in that
released main artifact. Does this sound reasonable?

Cheers,
Radu

On Fri, 10 Apr 2015 at 11:04 Robert Munteanu <ro...@apache.org> wrote:

> Hi Radu,
>
> On Thu, Apr 9, 2015 at 7:46 PM, Radu Cotescu <ra...@apache.org> wrote:
> >
> > The repository contains:
> > org.apache.sling.scripting.sightly.js.provider-1.0.4
> > org.apache.sling.scripting.sightly.testing-content-1.0.4
> > org.apache.sling.scripting.sightly.testing-1.0.4
>
> Out of curiosity, why do you include tests in releases? We typically
> don't release them as they are executed as part of the reactor builds
> anyway.
>
> Not that it matters or it costs, but you made me curious :-)
>
> Thanks,
>
> Robert
>