You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/12/09 03:55:00 UTC
[jira] [Commented] (MENFORCER-322) requireProfileIdsExist triggers
if profile is defined at parent
[ https://issues.apache.org/jira/browse/MENFORCER-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713850#comment-16713850 ]
ASF GitHub Bot commented on MENFORCER-322:
------------------------------------------
belingueres opened a new pull request #46: [MENFORCER-322] - requireProfileIdsExist triggers if profile is defined at parent
URL: https://github.com/apache/maven-enforcer/pull/46
Fixed iterating over parent poms. Added IT.
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MENFORCER) filed
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line and body.
- [x] Format the pull request title like `[MENFORCER-XXX] - Fixes bug in ApproximateQuantiles`,
where you replace `MENFORCER-XXX` with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
- [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> requireProfileIdsExist triggers if profile is defined at parent
> ---------------------------------------------------------------
>
> Key: MENFORCER-322
> URL: https://issues.apache.org/jira/browse/MENFORCER-322
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
> Affects Versions: 3.0.0-M2
> Reporter: Andre Schulz
> Priority: Major
>
> If a profile is defined at a parent POM the maven-enforcer-plugin fails the build if requireProfileIdsExist is used.
> Transitive profiles should be also respected, since they are used during build.
> Example:
> profile from parent: RUN
> profile from self: DEV
> build parameters: -P RUN,DEV
> {code:java}
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireProfileIdsExist faile
> d with message:
> The requested profile doesn't exist: RUN
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)