You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2010/09/18 10:30:32 UTC
[jira] Commented: (BUILDR-335) excluding libraries from war is
confusing
[ https://issues.apache.org/jira/browse/BUILDR-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910917#action_12910917 ]
Hudson commented on BUILDR-335:
-------------------------------
Integrated in Buildr-ci-build #121 (See [https://hudson.apache.org/hudson/job/Buildr-ci-build/121/])
BUILDR-335 follow up: excluding libraries from war is confusing
> excluding libraries from war is confusing
> -----------------------------------------
>
> Key: BUILDR-335
> URL: https://issues.apache.org/jira/browse/BUILDR-335
> Project: Buildr
> Issue Type: Wish
> Affects Versions: 1.3.5
> Reporter: Ittay Dror
> Assignee: Antoine Toulme
> Fix For: 1.4.2
>
>
> the confusion is from how ArchiveTask excludes files, but manifests itself in wars.
> when i create a war package, it automatically adds all compile dependencies as libs. then during preparation it adds them with
> path('WEB-INF/lib').include Buildr.artifacts(@libs)
> now say i have a library foo.jar which i want to exclude.
> these do not work:
> war.exclude('**/foo.jar')
> war.path('WEB-INF/lib').exclude('foo.jar')
> only this works:
> war.path('WEB-INF/lib').exclude('**/foo.jar')
> knowing that this is the way is not intuitive an required me to dig through the code of archive.rb
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.