Gordon Pettey created MNG-5856:
----------------------------------
Summary: property profile activation fails for non-uppercase
env.someThing
Key: MNG-5856
URL: https://issues.apache.org/jira/browse/MNG-5856
Project: Maven
Issue Type: Bug
Affects Versions: 3.2.5
Environment: Windows 7, affects both cmd and git 1.9.5 bash
Reporter: Gordon Pettey
I have three profiles. The first, no-ci, is activeByDefault. The other two are
bamboo activated by property env.bamboo_buildNumber and jenkins activated by
eng.BUILD_NUMBER. The jenkins profile activates as expected, but bamboo will
not activate in either git bash or cmd. Docs suggest Maven normalizes the
property name to all uppercase on Windows, but this is apparently not
happening. I have tried all-upper, -lower, and mixed case.
I am using the profiles to configure m-jar-p manifest entries to include build
names and numbers, as if they're all in the main configuration, the manifest
will include empty keys for whichever build system wasn't used, which might be
another bug. Archiver docs suggest missing properties are ignored, but that
apparently doesn't extend to unset environment variables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
