[GRADLE-1247] If a build is run after an update in the build.gradle script, we get the following error message: (java.lang.UnsupportedOperationException: Build file '[...]/build.gradle' should not contain a package statement) Created: 07/Dec/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9-rc-3
Fix Version/s: None

Type: Bug
Reporter: Narcisa Pantilimon Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: Zip Archive gradle bug.zip     Text File stack trace.txt    

 Description   

It appears that this problem is caused by the usage of the fully qualified name of a custom plugin in 'apply plugin' statement or by importing a class.

If Gradle finds the source code for the classes imported or applied as plugins in build.gradle script, it will generate the AST tree for those classes and will complain about the existence of the 'package' statement:
java.lang.UnsupportedOperationException: Build file '[...]/build.gradle' should not contain a package statement
(see the full stack trace log file attached to this bug)

In order to reproduce this bug, follow these steps:

  • unpack the 'gradle bug.zip';
  • set the 'uploadArchivesRepositoryURL' to a valid URL;
  • run the script from MyUtils folder (it will upload an artifact with the attached sources);
  • run the script from MyClient

The bug reproduces only when the script from MyClient is modified and after that, executed. If you run the script again, without any change, it will successfully execute.

 Comments   
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:50:41 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.