[jira] Updated: (BUILDR-335) excluding libraries from war is confusing

["Alex Boisvert (JIRA)" <ji...@apache.org>]

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

Alex Boisvert updated BUILDR-335:
---------------------------------

    Affects Version/s: 1.3.5
        Fix Version/s:     (was: 1.4)
                       1.4.1

At this point, I think this is better moved to 1.4.1.   I think it's going to require some non-trivial amount of code to fix and I wouldn't want to delay 1.4.0 further.

> 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
>             Fix For: 1.4.1
>
>
> 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.