buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Boisvert <alex.boisv...@gmail.com>
Subject Re: Default Scope of Dependencies
Date Fri, 02 Aug 2013 23:02:27 GMT
Makes sense to me.  Will fix when I get to back to a computer.

On Friday, August 2, 2013, Ingo Schmidt wrote:

> Hi all,
>
> I have a question about the default scope of dependencies in buildr.
> According to http://maven.apache.org/**guides/introduction/**
> introduction-to-dependency-**mechanism.html<http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html>the
compile scope is the default, if no scope is specified.
> However, if I run this code in buildr:
>
>     pom = POM.load("pom.xml")
>     puts pom.dependencies(:scopes=>"**compile").inspect
>
> it won't print anything, unless I explicitly specify the scope in the POM
> file.
> Any reason why that is so? Could it not very easily be fixed by adding
> this:
>
> { :scope=>"compile" }.merge(hash)
>
> to the method pom_to_hash in pom.rb file, like it is already done for the
> type, if none was specified?
>
> Anything speaking against that?
>
> Cheers, Ingo =;->
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message