[
https://issues.apache.org/jira/browse/BUILDR-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645580#action_12645580
]
Ittay Dror commented on BUILDR-206:
-----------------------------------
so transitive is a complex replacement to 'project.packages'?
> transitive method does not work for projects
> --------------------------------------------
>
> Key: BUILDR-206
> URL: https://issues.apache.org/jira/browse/BUILDR-206
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.3.2
> Reporter: Ittay Dror
> Fix For: 1.3.4
>
>
> when passing a Project object to #transitive it matches the Project clause in
> 'case' , it then calls itself recursively with the packages of the project.
> these fall in the 'when Rake::Task' clause. If they are "spec" packages, the
> method again recursively calls itself. this time the clause is
> /([^:]+:){2,4}/ which then tries to load the pom from the repository. there's
> no reason why there will be a pom there. if the packages are 'file'
> packages, they are used as-is.
> in both cases, there is no transitivity of dependencies.
> suggestion:
> * add :project attribute to package tasks
> * in Rake::Task clause, if the artifact responds to :project, then call
> recursively with the project
> * in Project clause, add the packages to the result set and call recursively
> with spec.compile.dependencies (which can then be artifacts or packages)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
