[GRADLE-1131] processResource.doLast is skipped prematurely Created: 25/Aug/10  Updated: 04/Jan/13  Resolved: 06/Sep/10

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Kallin Nagelberg Assignee: Hans Dockter
Resolution: Not A Bug Votes: 0


 Description   

processResources.doLast is skipped when there are no resources. The message in INFO log is:

'Main resources does not contain any files.'

I wanted to prepare some additional custom resources after that phase, but my closure is never invoked. I think that the doLast closure should apply even if the main processResources task is deemed to be skippable.



 Comments   
Comment by Hans Dockter [ 06/Sep/10 ]

I think this is not a bug. It is rather a configuration issue. You have two options:

1.) Don't add an action via doLast. Instead use the API of the processResources task (type Copy) to add your custom resource processing. Whether this approach works for you depends on what you need to do. The Copy task offers a lot of options for filtering and stuff like that.

2.) Leave the doLast action in place. Use the API to describe the input/output model. This is not described yet in the user's guide. Have a look at this thread: http://markmail.org/message/tiru6jpl642a4euf

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