You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2013/09/28 01:22:03 UTC
[jira] [Updated] (BUILDR-674) Common error in Maven Repository
causes problems with Buildr
[ https://issues.apache.org/jira/browse/BUILDR-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Donald updated BUILDR-674:
--------------------------------
Fix Version/s: 1.4.13
> Common error in Maven Repository causes problems with Buildr
> ------------------------------------------------------------
>
> Key: BUILDR-674
> URL: https://issues.apache.org/jira/browse/BUILDR-674
> Project: Buildr
> Issue Type: Bug
> Environment: Windows 7
> Reporter: Colbert Philippe
> Fix For: 1.4.13
>
>
> I used Maven for the longest time on projects. Maven could download all the artifacts needed for my current project. I decided to upgrade to Buildr. I first noticed that Buildr could not download all the artifacts that Maven could, even using the same Maven Repositories. I noticed that most of these discrepancies are caused by errors in the artifact coordinates. Sometimes on the repository, the format of the artifact will bt 'bundle' instead of 'jar'. I have fixed that on a few artifacts.
> However, if the artifact as many dependencies, that causes a major problem with Buildr.
> Try to download ActiveMQ artifact with Buildr. It gives you this coordinates which will not download.
> 'org.apache.activemq:activemq-core:bundle:5.7.0'
> You have to fix the format bundle for jar then it downloads.
> 'org.apache.activemq:activemq-core:jar:5.7.0'
> But the dependency resolution fails following the download, which is probably caused by a symbolic mismatch internally.
> You should press the maven repository to fix all their 'bundle' mistakes. And while we are at it, why doesn't somebody test all the artifact downloads available in Buildr ? It should be done!
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira