[GRADLE-87] Add alternative interface to Plugin that only works in single-project mode, otherwise causes build to fail Created: 05/May/08  Updated: 24/Jan/17  Resolved: 24/Jan/17

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

Type: Improvement
Reporter: Sixpack none the richer Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

For example:

package org.gradle.api.plugins

public interface SingleProjectBuildPlugin extends Plugin {}

Certain plugins should only be launched in single-project-build mode (potentially invoked by -u), for example a plugin that creates the default java project directory structure (for lazy developers only). If Gradle is in multi-project-build mode invoking such a plugin would cause the build to fail at configuration time.

In combination with GRADLE-86 this would result in:

gradle -u --use-plugins java-convention create

 Comments   
Comment by Hans Dockter [ 08/May/08 ]

Does the archetype functionality necessarily has to be single project?

Comment by Sixpack none the richer [ 09/May/08 ]

> Does the archetype functionality necessarily has to be single project?

That's open for discussion. I think it makes sense, otherwise you could inadvertently run archetypes on a multiproject build. I'm not sure how Maven deals with this.

Still, I think offering a forced single-project plugin mode makes sense in general, for those that prefer it.

Comment by Hans Dockter [ 09/May/08 ]

Definitely.

Beside this, one should be able to optionally confine archetype creation to one project.

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 [ 24/Jan/17 ]

This functionality can be handled by the plugin code if needed.

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