[
https://issues.apache.org/jira/browse/BUILDR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622299#action_12622299
]
Assaf Arkin commented on BUILDR-131:
------------------------------------
Hash and String are just two different representations of the same thing:
http://incubator.apache.org/buildr/artifacts.html#specifying_artifacts
Hash exists because in many places it's more convenient to work with them, and
eventually strings are broken up into their component parts, but the two
representations are kept consistent, otherwise you lose information. The API
specifically allows to convert from one to the other and back.
> allow metadata in artifact definition
> -------------------------------------
>
> Key: BUILDR-131
> URL: https://issues.apache.org/jira/browse/BUILDR-131
> Project: Buildr
> Issue Type: Improvement
> Components: Dependency management
> Affects Versions: 1.3.2
> Reporter: Ittay Dror
> Fix For: 1.3.3
>
> Attachments: artifact.patch
>
>
> Buildr allows to define artifacts as string ('group:id:type:version'), but
> also as a hash. The benefit I can see in using a hash is that it allows
> adding keys that are used by plugins when appropriate (metadata). However,
> Buildr always sanitizes the hash, so all metadata is lost
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
