[
https://issues.apache.org/jira/browse/BUILDR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622320#action_12622320
]
Victor Hugo Borja commented on BUILDR-131:
------------------------------------------
As I see it, artifacts are just a way of pointing to files in maven
repositories, let's keep them simple.
So if you need to add metadata on artifacts, you could add it to the jar's
manifest.
OSGi bundles are more advanced than maven artifacts in that they allow the user
to add more information about the bundle, again those details are stored on the
jar's manifest. OSGi support is planned for a future Buildr release.
> 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.
