Repository: buildr Updated Branches: refs/heads/master 547a38d74 -> fa4750b70
BUILDR-565: resources are not included in the war if defined after package call Added a paragraph to the website explaining the importance of the order of the instructions when defining a build, providing the example given in the bug. Project: http://git-wip-us.apache.org/repos/asf/buildr/repo Commit: http://git-wip-us.apache.org/repos/asf/buildr/commit/fa4750b7 Tree: http://git-wip-us.apache.org/repos/asf/buildr/tree/fa4750b7 Diff: http://git-wip-us.apache.org/repos/asf/buildr/diff/fa4750b7 Branch: refs/heads/master Commit: fa4750b70c40398bf528daa79ef0c1931405eff6 Parents: 547a38d Author: Antoine Toulme <[email protected]> Authored: Thu May 19 23:21:02 2016 -0700 Committer: Antoine Toulme <[email protected]> Committed: Thu May 19 23:21:04 2016 -0700 ---------------------------------------------------------------------- CHANGELOG | 1 + doc/projects.textile | 13 +++++++++++++ 2 files changed, 14 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/buildr/blob/fa4750b7/CHANGELOG ---------------------------------------------------------------------- diff --git a/CHANGELOG b/CHANGELOG index fb15405..f5b4b2a 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -13,6 +13,7 @@ * Fixed: BUILDR-207 remove 'Skipping tests' messages * Added: BUILDR-703 release: allow THIS_VERSION to be defined in another file * Fixed: BUILDR-674 Artifacts with bundle extension cannot be downloaded by Buildr +* Fixed: BUILDR-565 resources are not included in the war if defined after package call 1.4.25 (2016-04-18) * Change: BUILDR-712 Update jruby-openssl dependency version or support a range of versions http://git-wip-us.apache.org/repos/asf/buildr/blob/fa4750b7/doc/projects.textile ---------------------------------------------------------------------- diff --git a/doc/projects.textile b/doc/projects.textile index 6f8ad30..3418075 100644 --- a/doc/projects.textile +++ b/doc/projects.textile @@ -64,6 +64,19 @@ A project definition requires four pieces of information: the project name, grou Everything else depends on what that particular project is building. And it all goes inside the project definition block, the piece of code that comes between @define <name> .. do@ and @end@. +h2(#instructions_order). Order is important +When defining your project, the order in which you place instructions matter. + +For example, the project below will not pick up resources because they are defined after the package instruction. + +{% highlight ruby %} +define 'testwar' do +project.version = 1.0 +package(:war) +project.resources.from(_('src/main/java')).exclude('*.java') +end +{% endhighlight ruby %} + h2(#dir_structure). The Directory Structure
