buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Assaf Arkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-44) Project#packages selector improvement
Date Mon, 11 Feb 2008 21:40:08 GMT

    [ https://issues.apache.org/jira/browse/BUILDR-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567824#action_12567824
] 

Assaf Arkin commented on BUILDR-44:
-----------------------------------

Added BUILDR-47 to deal with the clean task.

I'm actually warming up to the idea that only the default JARs include target/classes.

> 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.


Mime
View raw message