[
https://issues.apache.org/jira/browse/BUILDR-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Assaf Arkin resolved BUILDR-25.
-------------------------------
Resolution: Won't Fix
Fix Version/s: 1.2.10
Assignee: Assaf Arkin
> Buildr is not getting the dependencies of dependent artifacts
> -------------------------------------------------------------
>
> Key: BUILDR-25
> URL: https://issues.apache.org/jira/browse/BUILDR-25
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Reporter: K. Adam Christensen
> Assignee: Assaf Arkin
> Fix For: 1.2.10
>
>
> Using Buildr to manage dependencies can be less reliable than using Maven in
> some cases. Take for instance the following:
> In a pom, I have the following XML:
> ------------------------------------------------------------------------------
> <dependency>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-impl</artifactId>
> <version>2.0.3</version>
> </dependency>
> <dependency>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-xjc</artifactId>
> <version>2.0.3</version>
> </dependency>
> ------------------------------------------------------------------------------
> Then in my buildfile I have:
> ------------------------------------------------------------------------------
> XJC = [com.sun.xml.bind:jaxb-impl:jar:2.0.3',
> 'com.sun.xml.bind:jaxb-xjc:jar:2.0.3']
> compile.with XJC
> ------------------------------------------------------------------------------
> When you examine the classpath for maven it includes other jars like
> "activation.jar", "jaxb-api", "jsr173_api" and downloads them, while Buildr
> just includes "jaxb-xjc" and "jaxb-impl".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
