[
https://issues.apache.org/jira/browse/BUILDR-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566746#action_12566746
]
Assaf Arkin commented on BUILDR-44:
-----------------------------------
Currently, if you want to get a specific package you can do:
project.package(:war)
project.package(:classifier=>'sources')
That's a fairly common use case. And if you have two of those you need, say
JAR and WAR, it's usually easier to call package twice than remember the
selector syntax. I'm not sure there's a clear use case for adding this
syntactic sugar.
> Project#packages selector improvement
> -------------------------------------
>
> Key: BUILDR-44
> URL: https://issues.apache.org/jira/browse/BUILDR-44
> Project: Buildr
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 1.3
> Reporter: Victor Hugo Borja
> Priority: Minor
> Fix For: 1.3
>
> Attachments:
> 0001-Project-packages-can-now-take-a-selectors-argument.patch
>
>
> Currently, the Project#packages method returns all the packages defined for a
> project. However it would be useful to provide a way to easily narrow
> returned packages without having the user(mainly ruby newcomers) to use the
> select ruby idiom
> project.packages.select { |p| p.type == :war }
> It would be nicer to have something like:
>
> project.packages(:type => :war) # actually comparing :war with the type
> attribute of each package
> project.packages(JarTask) # select all Jar kind packages
> For more advanced stuff, users may still need to provide a Proc/Method or
> select the full packages array the ruby way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
