You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2010/12/03 19:36:12 UTC
[jira] Updated: (BUILDR-486) Buildr-generated poms should include
dependencies
[ https://issues.apache.org/jira/browse/BUILDR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated BUILDR-486:
------------------------------------
Attachment: BUILDR-486.patch
Hi guys,
please find attached a patch for this issue. It add the following functionality:
* artifacts are now dependency-aware. Dependencies can be set, or, if unset, can be loaded from a maven pom if available in the local repo.
* dependencies are serialized in pom_xml
* artifacts have a new dependency getter called "with_dependencies". This returns the artifact itself including its dependencies. This is useful in scenarios like compile.with artifact("saxon:saxon:jar:8.4").with_dependencies
* packaging tasks set the dependencies of the created artifact. By default, the dependencies are get from compile.dependencies but can be overridden via package(:jar).with(:dependencies =>[artifact("saxon:saxon:jar:8.4")])
Would be great if someone could review the patch.
Thanks,
Tammo
> Buildr-generated poms should include dependencies
> -------------------------------------------------
>
> Key: BUILDR-486
> URL: https://issues.apache.org/jira/browse/BUILDR-486
> Project: Buildr
> Issue Type: Improvement
> Components: Dependency management
> Affects Versions: 1.4.1
> Reporter: Alex Boisvert
> Priority: Minor
> Fix For: Wish List
>
> Attachments: BUILDR-486.patch
>
>
> To quote a personal email I received:
> " I just realized that buildr-created poms have zero dependencies. Wtf?
> That's kind of the point of publishing a pom. :-)"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.