You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Brian Demers (JIRA)" <ji...@apache.org> on 2019/05/01 19:47:00 UTC
[jira] [Commented] (SHIRO-686) Use sha512 for release source
checksum
[ https://issues.apache.org/jira/browse/SHIRO-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831216#comment-16831216 ]
Brian Demers commented on SHIRO-686:
------------------------------------
Maven _should_ be merging the profiles together (which i'm guessing which is why `apache-release` was used in the shiro pom)
Maybe there something in the profile activation that is preventing this?
> Use sha512 for release source checksum
> --------------------------------------
>
> Key: SHIRO-686
> URL: https://issues.apache.org/jira/browse/SHIRO-686
> Project: Shiro
> Issue Type: Improvement
> Reporter: Francois Papon
> Assignee: Francois Papon
> Priority: Major
> Fix For: 1.5.0
>
>
> When performing the release source, we are using the "apache-release" profile define in the root pom.xml. However, the Apache pom parent include a profile with the same name wich is in charge to define the checksum algorithm to use.
> We have to rename the profile from "apache-release" to "release" in the pom parent and using
> {code:java}
> -Pdocs,apache-release,release{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)