commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Parent POM and automatic module name
Date Tue, 09 Jan 2018 00:27:18 GMT
On 8 January 2018 at 23:14, Jörg Schaible <joerg.schaible@gmx.de> wrote:
> Am Mon, 08 Jan 2018 00:48:08 +0000 schrieb sebb:
>
>> On 8 January 2018 at 00:25, Jörg Schaible <joerg.schaible@gmx.de> wrote:
>
> [snip]
>
>>>> The component poms I checked all include a comment like "Temporary
>>>> fix, remove this after this has implemented in parent pom". As these
>>>> comments are not true anymore I will remove those I find.
>>>
>>> It is possible to define a profile in parent and trigger it as opt-in
>>> based on the existence of a file.
>>>
>>> Do we have any precedence for triggering profiles based on file
>>> existence in commons? Typical name patterns used are:
>>>  - profile/<name> - profiles/<name>
>>>  - <name>.profile
>>
>> Yes, e.g. jacoco
>
> Found it:
>
>  - src/site/resources/profile.<name>
>
> However the location for these profile files does not make sense in general. And definitely
not for a profile
> adding the module name :-/
>
> Alternatives? Common location for such a profile activation?

src/site/resources was chosen because Jacoco is used for the site build.
I don't think such files should should be moved.

But by all means find somewhere else for new profile triggers.

> Cheers,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message