[
https://issues.apache.org/jira/browse/BUILDR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433979#comment-15433979
]
Trejkaz commented on BUILDR-486:
--------------------------------
I have overnight done some further investigation of my own and it seems like
replacing this:
{code}
d.is_a?(Artifact)
{code}
with this:
{code}
d.is_a?(Artifact) || d.is_a?(ActsAsArtifact)
{code}
Made the additional dependencies show up for my project.
It was then showing three of every dependency, which I think was my fault - I
changed this:
{code}
compile.with projects('util')
{code}
To this:
{code}
compile.with project('util').package(:jar)
{code}
And then only one showed up, presumably because projects('util') includes the
javadoc and sources jars as well as the one I wanted.
> 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
> Assignee: Antoine Toulme
> Fix For: 1.5
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
