[
https://issues.apache.org/jira/browse/BUILDR-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969079#action_12969079
]
Tammo van Lessen commented on BUILDR-486:
-----------------------------------------
Alex, yep, it's just moved upward. I'll attach my playground project. The
circular dependency happens with GPG signing like described in the wiki.
The project first packages :jar, :javadoc, :sources and then:
packages.each { |pkg| GPG.sign_and_upload(pkg) }
GPG.sign_and_upload(package(:jar).pom)
With the "package.dependencies |= compile.dependencies" moved upwards I get the
circular dependency, using my first patch it works (but the .pom files don't
contain the dependencies).
RuntimeError : Circular dependency detected: TOP => upload => btest:upload =>
btest:http://vanto:t...@localhost:8081/nexus/content/repositories/releases/btest/btest/1.0.0/btest-1.0.0.pom.asc
=> C:/Users/vanto/.m2/repository/btest/btest/1.0.0/btest-1.0.0.pom.asc =>
C:/Users/vanto/.m2/repository/btest/btest/1.0.0/btest-1.0.0.pom.asc
> 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: btest.zip, 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.
