[GRADLE-530] New Jar task always included classes found in 'classesDir' Created: 25/Jun/09  Updated: 04/Jan/13  Resolved: 15/Jul/09

Status: Resolved
Project: Gradle
Affects Version/s: 0.6
Fix Version/s: 0.7

Type: Bug
Reporter: Donal McNamee Assignee: Adam Murdoch
Resolution: Fixed Votes: 0


 Description   

Creating a new task of type 'Jar' will always jar-up the classes in 'classesDir' as well as those specified in the 'FileSet' directive:

(e.g.)
Running the following task with the '-d' flag:

task jarServiceFacade(type: Jar, dependsOn: compileServiceFacade) {
baseName = 'ias_ta_common_service_facade'
fileSet(dir: servicesFacadeClassesDir) {
include("ie/vhi/ias/ta/common/services/facade/**")
}

produces:

  • Creating archive: jarServiceFacade
  • fileset: Setup scanner in dir C:\workspace\Core\branches\TEMP_gradle\TA\ias_ta_common\build\classes with patternSet { includes: [] excludes: [] }
  • fileset: Setup scanner in dir C:\workspace\Core\branches\TEMP_gradle\TA\ias_ta_common\build\facade-classes with patternSet { includes: [ie/vhi/ias/ta/common/services/facade/**] excludes: [] }

This can be worked around by setting 'resourceCollections = []'

See thread: http://article.gmane.org/gmane.comp.programming.tools.gradle.user/1908


Generated at Wed Jun 30 11:32:27 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.