[
https://issues.apache.org/jira/browse/OMID-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated OMID-308:
-----------------------------
Description:
The Phoenix project release script activates the _apache-release_ and _release_
profiles.
_apache-release_ is imported from the ASF parent pom, and _release_ is expected
contain the project-specific configurations. However, in omid, the release
profile is called _release_profile_ amd thus never gets activated.
We need to rename _release_profile_ to _release_ to get the intended behaviour.
Additionally, once we fix the profile name, maven fails because
maven-source-plugin is already activated in the ASF parent pom _apache-release_
profile, so we need to remove the duplicate plugin declaration from the profile.
was:
The Phoenix project release script activates the _apache-release_ and _release_
profiles.
_apache-release_ is imported from the ASF parent pom, and _release_ is
expected contain the project-specific configurations. However, in omid, the
release profile is called _release_profile_ amd thus never gets activated.
We need to rename _release_profile_ to _release_ to get the intended behaviour.
Additionally, once we fix the profile name, maven fails because
maven-source-plugin is already activated in the ASP parent pom apache-release
profile, so we need to remove the duplicate plugin declaration from the profile.
> Fix release maven profile
> -------------------------
>
> Key: OMID-308
> URL: https://issues.apache.org/jira/browse/OMID-308
> Project: Phoenix Omid
> Issue Type: Bug
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Blocker
>
> The Phoenix project release script activates the _apache-release_ and
> _release_ profiles.
> _apache-release_ is imported from the ASF parent pom, and _release_ is
> expected contain the project-specific configurations. However, in omid, the
> release profile is called _release_profile_ amd thus never gets activated.
> We need to rename _release_profile_ to _release_ to get the intended
> behaviour.
> Additionally, once we fix the profile name, maven fails because
> maven-source-plugin is already activated in the ASF parent pom
> _apache-release_ profile, so we need to remove the duplicate plugin
> declaration from the profile.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
