[
https://issues.apache.org/jira/browse/MRELEASE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-1041.
------------------------------------
Assignee: Robert Scholte
Resolution: Duplicate
> releaseProfiles paremeter has no effect
> ---------------------------------------
>
> Key: MRELEASE-1041
> URL: https://issues.apache.org/jira/browse/MRELEASE-1041
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 3.0.0-M1
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Java version: 1.8.0_181, vendor: Oracle Corporation
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
> Reporter: Simon Zilliken
> Assignee: Robert Scholte
> Priority: Major
>
> We select a repository to be used in the deploy-goal via a
> {{deploy.repository}} variable, which is set to the production repository
> when we release a library. Following the maven-release-plugin documentation
> we configured it like this:
> {code:java}
> <build>
> <plugin>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <releaseProfiles>release</releaseProfiles>
> </configuration>
> </plugin>
> </build>
> <profiles>
> <profile>
> <id>release</id>
> <properties>
> <deploy.repository>prod.mvn</deploy.repository>
> </properties>
> </profile>
> </profile>{code}
> This doesn't work with version 3.0.0-M1. {{help:show-profiles}} shows that
> the release-profile is not activated.
> After downgrading to maven-release-plugin v 2.5.3 it works as expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
