[
https://issues.apache.org/jira/browse/BUILDR-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Victor Hugo Borja closed BUILDR-44.
-----------------------------------
Resolution: Won't Fix
I fully agree with what you say on teaching people how to use basic Ruby
idioms, so I'm clossing this issue.
>>Why don't we change this so Buildr does the right thing:
>>a) Add clean method to ArchiveTask, so you can do package(:jar,
>>:classifier=>'addons').clean.include(whatever) (This was asked for before)
>>b) Identify patterns of usage. For example, if classifier is hardly ever
>>used for the main JAR, why not change >>package_as_jar so it doesn't include
>>anything by default when specifying a classifier?
I'd prefer the first option.
> 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.
