maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Smith (JIRA)" <>
Subject [jira] (MNG-5671) Profile in settings.xml does not activate modules
Date Fri, 01 Aug 2014 16:38:10 GMT


Christopher Smith commented on MNG-5671:

This behavior may be by design. If that's the case, for preserving build portability, then
it would be helpful to explicitly log at {{INFO}} that {{profile}} stanzas are being skipped
because the profile source isn't privileged enough.

> Profile in settings.xml does not activate modules 
> --------------------------------------------------
>                 Key: MNG-5671
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Profiles, Reactor and workspace
>    Affects Versions: 3.1.1
>            Reporter: Christopher Smith
> I have a multi-module setup where one "sandbox" module should only be built in development
and not on the CI server, so I moved that module to a {{profile}} stanza in the parent POM.
I also added that {{sandbox}} profile to my {{.m2/settings.xml}}, active by default.
> When I run any goals (including {{help:active-profiles}}, {{dependency:resolve}}, and
{{compile}}), the {{sandbox}} profile is listed as active ({{source: external}}), but the
reactor does not include the module in the build. If I explicitly specify the goal on the
command line using {{-P sandbox}}, the module is correctly included.
> (This behavior is visible on 3.1.1. I can't upgrade to 3.2 yet because of incompatibilities
with Jenkins, and none of the issues listed as fixed in the 3.2 series matched the behavior.)

This message was sent by Atlassian JIRA

View raw message