[GRADLE-931] SourceSet not serializable Created: 05/May/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Hans Dockter Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: Zip Archive gradlegwt.zip     Text File output.txt    

 Description   

I got the following bug report via email:

I've was messing about trying to write a build for a GWT sample today
and ran into an internal gradle error along the way, due to a
serialization problem of some kind.

I've attached the project and gradle debug output. I was running with a
build from the latest source.

------------------------------------------------------------
Gradle 0.9-20100406003019+0100
------------------------------------------------------------

Gradle buildtime: Tuesday, April 6, 2010 12:30:19 AM BST

Test cases are attached.



 Comments   
Comment by Hans Dockter [ 24/Jun/10 ]

I'm not sure whether this should be fixed. In general you want to pick the relevant properties from a source set for your input properties. But may be our task inputs should become source set aware.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

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