You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@buildr.apache.org by "Assaf Arkin (JIRA)" <ji...@apache.org> on 2008/09/25 23:21:44 UTC

[jira] Resolved: (BUILDR-131) allow metadata in artifact definition

     [ https://issues.apache.org/jira/browse/BUILDR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Assaf Arkin resolved BUILDR-131.
--------------------------------

    Resolution: Won't Fix

Delegated to forthcoming dependency management.

> 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
>
>
> 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.