buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Donald (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (BUILDR-382) Packages with default spec are not always created correctly
Date Wed, 22 Jun 2011 10:11:09 GMT

     [ https://issues.apache.org/jira/browse/BUILDR-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Peter Donald closed BUILDR-382.
-------------------------------


> Packages with default spec are not always created correctly
> -----------------------------------------------------------
>
>                 Key: BUILDR-382
>                 URL: https://issues.apache.org/jira/browse/BUILDR-382
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.5
>            Reporter: Pepijn Van Eeckhoudt
>            Assignee: Alex Boisvert
>             Fix For: 1.4
>
>         Attachments: packaging.patch
>
>
> If two packages are created with only the type specified as parameter is possible for
only a single package to be created. For instance, when creating a :javadoc and a :zip package
in a single project; only the first package will be created. The bug is in package(*args)
and relates to the no_options flag. When this flag is true, the package is checked for incorrectly.
The attached patch adds a spec for this case and fixes a bug that was required to get the
spec to run.
> It is not clear to me why that no_options variant is needed in the first place. When
using
> package(:type => :javadoc) and package(:type => :zip) instead of package(:javadoc)
and package(:zip) everything works correctly. In my understanding the two are semantically
equivalent, yet due to this no_options flag they are treated differently.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message