You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Stephen Haberman (JIRA)" <ji...@apache.org> on 2011/01/29 06:14:44 UTC
[jira] Updated: (BUILDR-565) resources are not included in the war
if defined after package call
[ https://issues.apache.org/jira/browse/BUILDR-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Haberman updated BUILDR-565:
------------------------------------
Attachment: resources-skipped.zip
The attached project reproduces the error.
> resources are not included in the war if defined after package call
> -------------------------------------------------------------------
>
> Key: BUILDR-565
> URL: https://issues.apache.org/jira/browse/BUILDR-565
> Project: Buildr
> Issue Type: Bug
> Components: Packaging
> Affects Versions: 1.4.4
> Reporter: Stephen Haberman
> Attachments: resources-skipped.zip
>
>
> I have the issue done to the order of the buildfile instructions. E.g. this order:
> define 'testwar' do
> project.version = 1.0
> package(:war)
> project.resources.from(_('src/main/java')).exclude('*.java')
> end
> With no existing src/main/resources directory means project.resources is nil when package(:war) is called.
> If the custom resources call (project.resources.from...) is put before the package(:war) command, then resources is no longer nill, and they end up in the war's classes directory just fine.
> This is a boundary case bordering on user error--not having a src/main/resources, and defining my own resources after calling package, but I was under the impression the declarative nature of the package/project.resources lines insinuated order was not important.
> Given I can just reorder the lines, this isn't a big deal, but still filling the bug in case there is a way to make it more user-error proof.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.