[
https://issues.apache.org/jira/browse/BUILDR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988983#comment-12988983
]
John Shahid commented on BUILDR-486:
------------------------------------
I don't know if this issue is resolved already or not. In any case, I've been
working on an extension that take care of generating a pom that has
dependencies as well as resolve dependencies transitively (for runtime/test
classpaths). It supports version conflict resolution using the dependency depth
in the graph, exclusions (similar to exclusions in maven) and adding custom
sections to the generated pom. Instead of duplicating the effort, we can merge
the extensions in Buildr. The extension is on github
(https://github.com/jvshahid/buildr-dependency-extensions).
> 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, BUILDR-486_2.patch, btest.zip
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
