Gradle - plugin with id 'com.liferay.settings.plugin' not found

[David Knol, modifié il y a 7 années.]

Hi,
I've done some changes in 'dynamic-data-mapping-web'. I want to compile and deploy it, so I'm running gradle compile. Unfortunately, I am getting error:

FAILURE: Build failed with an exception.

* Where:
Settings file '...\liferay-ce-portal-src-7.0-ga3\modules\apps\forms-and-workflow\dynamic-data-mapping\settings.gradle' line: 15

* What went wrong:
A problem occurred evaluating settings 'dynamic-data-mapping'.
> Plugin with id 'com.liferay.settings.plugin' not found.

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.GradleScriptException: A problem occurred evaluating settings 'dynamic-data-mapping'.
        at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93)
        at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:177)
        at org.gradle.configuration.DefaultScriptTarget.addConfiguration(DefaultScriptTarget.java:74)
        at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:182)
        at org.gradle.initialization.ScriptEvaluatingSettingsProcessor.applySettingsScript(ScriptEvaluatingSettingsProcessor.java:72)
        at org.gradle.initialization.ScriptEvaluatingSettingsProcessor.process(ScriptEvaluatingSettingsProcessor.java:62)
        at org.gradle.initialization.PropertiesLoadingSettingsProcessor.process(PropertiesLoadingSettingsProcessor.java:37)
        at org.gradle.initialization.NotifyingSettingsProcessor$1.create(NotifyingSettingsProcessor.java:42)
        at org.gradle.initialization.NotifyingSettingsProcessor$1.create(NotifyingSettingsProcessor.java:39)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
        at org.gradle.initialization.NotifyingSettingsProcessor.process(NotifyingSettingsProcessor.java:39)
        at org.gradle.initialization.SettingsHandler.findSettingsAndLoadIfAppropriate(SettingsHandler.java:90)
        at org.gradle.initialization.SettingsHandler.findAndLoadSettings(SettingsHandler.java:47)
        at org.gradle.initialization.NotifyingSettingsLoader.findAndLoadSettings(NotifyingSettingsLoader.java:33)
        at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:118)
        at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
        at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:98)
        at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:92)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:63)
        at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:92)
        at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:83)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:99)
        at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
        at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:48)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30)
        at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:81)
        at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:46)
        at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:51)
        at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:28)
        at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
        at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:239)
        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:212)
        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:205)
        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
        at org.gradle.launcher.Main.doAction(Main.java:33)
        at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:55)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:36)
        at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
Caused by: org.gradle.api.plugins.UnknownPluginException: Plugin with id 'com.liferay.settings.plugin' not found.
        at org.gradle.api.internal.plugins.DefaultPluginManager.apply(DefaultPluginManager.java:110)
        at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.applyType(DefaultObjectConfigurationAction.java:113)
        at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.access$200(DefaultObjectConfigurationAction.java:36)
        at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction$3.run(DefaultObjectConfigurationAction.java:80)
        at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.execute(DefaultObjectConfigurationAction.java:136)
        at org.gradle.groovy.scripts.DefaultScript.apply(DefaultScript.java:111)
        at org.gradle.api.Script$apply$0.callCurrent(Unknown Source)
        at settings_eyyo1goxzon6a1thasx7kujcb.run(C:\Praca\LIERAY_SOURCE\liferay-ce-portal-src-7.0-ga3\modules\apps\forms-and-workflow\dynamic-data-mapping\settings.gradle:15)
        at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:91)
        ... 45 more

Any ideas what's wrong and how to fix it? My dynamic-data-mapping/settings.gradle file:

buildscript {
	dependencies {
		classpath group: "com.liferay", name: "com.liferay.gradle.plugins", version: "latest.release"
	}

	repositories {
		mavenLocal()

		maven {
			url "https://cdn.lfrs.sl/repository.liferay.com/nexus/content/groups/public"
		}
	}
}

apply plugin: "com.liferay.settings.plugin"

Thanks in advance!

[David H Nebinger, modifié il y a 7 années.]

I have not been successful trying to compile individual modules from the source folder, I usually have to build the whole thing and that seems to work.

That said, you should not be doing this. This kind of thing is difficult to support and maintain and gets you off of the standard Liferahy release process.

If you have a necessary change, try submitting as a community contribution.

[David Knol, modifié il y a 7 années.]

Thanks for reply. What I'm trying to do is to create custom DDM type. To make it works, I assume I have to register it in:

/portal-master/modules/apps/forms-and-workflow/dynamic-data-mapping/dynamic-data-mapping-web/src/main/resources/META-INF/resources/js/main.js

and

/portal-master/modules/apps/forms-and-workflow/dynamic-data-lists/dynamic-data-lists-web/src/main/resources/META-INF/resources/js/main.js 

Is that correct? That's why I have to rebuild the module.

[David H Nebinger, modifié il y a 7 années.]

Oh, no, not at all. To create a custom type you just need to build as a module. They are separate simple modules.

Check out the dynamic-data-mapping-type-* modules. They are self contained and should be able to satisfy your requirements.

[David Knol, modifié il y a 7 années.]

Ok, can you redirect me to some examples? I need to create a custom DDM type which I want to use in a new structure. I've already created a new module, based on existing 'dynamic-data-mapping-type-select'. Unfortunately I am not seeing that module in new structure form..

[David H Nebinger, modifié il y a 7 années.]

So you need to check your bundle that it is starting correctly.

All of the examples I'd point you to are the other dynamic-data-mapping-type-* modules.

Those guys register as type handlers for ddm, so if yours starts it should display also.

[David Knol, modifié il y a 7 années.]

I've took another generic DDM type - text. I've took all files from sources and changed all 'text' names to another. After deploying there's info in the log, that the bundle has been started. Unfortunately there's no new type in new structure form. What may be wrong? Any hints?

[David H Nebinger, modifié il y a 7 années.]

Can you share what you've done? I'm guessing that there may be something missed...

If you search the whole Liferay source for "dynamic-data-mapping-type-text" you'll find that the only reference is in the ddm-type-text module itself. There are no references anywhere else indicating that it is being pulled in from anywhere specific. That's the whole indicator that you just need to add a new module and it should work.

[David Knol, modifié il y a 7 années.]

Would be great if you could help me. I've took sources of dynamic-data-mapping-type-select from modules/apps/forms-and-workflow/dynamic-data-mapping and created a new project based on them. Basically, I've renamed all files and references to "select" type. For example, here's NewTypeDDMFormFieldType.java (path in my project: src/main/java/com/liferay/dynamic/data/mapping/type/newType/internal):

@Component(
		immediate = true,
		property = {
			"ddm.form.field.type.icon=list",
			"ddm.form.field.type.js.class.name=Liferay.DDM.Field.NewType",
			"ddm.form.field.type.js.module=liferay-ddm-form-field-newType",
			"ddm.form.field.type.label=newType-field-type-label",
			"ddm.form.field.type.name=newType"
		},
		service = DDMFormFieldType.class
	)
public class NewTypeDDMFormFieldType extends BaseDDMFormFieldType{
	
	@Override
	public Class<!--? extends DDMFormFieldTypeSettings-->
		getDDMFormFieldTypeSettings() {

		return NewTypeDDMFormFieldTypeSettings.class;
	}

	@Override
	public String getName() {
		return "newType";
	}
}

Here's my bundle configuration:

Bundle-Name: Liferay Dynamic Data Mapping Type NewType
Bundle-SymbolicName: com.liferay.dynamic.data.mapping.type.newType
Bundle-Version: 1.0.0

If I understand correctly, after deploying that module it should be visible in Liferay. Unfortunately, there's no new type in a structure creation form. What I'm doing wrong?

[David Knol, modifié il y a 7 années.]

Ok, I can see that my new type is visible in the new form page. But what I'm trying to achieve is to add new type to structure form. How can I do this?

[Boris Hamm, modifié il y a 7 années.]

Hey David,
were you able to add a new type to stuctures?
I am trying to do the same but it only seems to work for web forms and not for ddl structures.
Any help appreciated!

[Alexandru Georgescu, modifié il y a 6 années.]

I had the same problem trying to build the portal-security-ldap plugin and it worked if I ran gradle like this:

../gradlew :apps:foundation:portal-security:portal-security-ldap:deploy

From SOURCES_ROOT/modules

If I run gradlew directly from the ..portal-security/portal-security-ldap folder I get the exception you mentioned.