[
https://issues.apache.org/jira/browse/BUILDR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ittay Dror updated BUILDR-131:
------------------------------
Description:
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
was:
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
verifies that a hash contains just the keys it knows, by using
rake_check_options. I wish that this check will be removed.
Attached a patch that does that
> 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.
