[JBoss JIRA] (DROOLS-3236) Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"
7:50 a.m.
[
https://issues.jboss.org/browse/DROOLS-3236?page=com.atlassian.jira.plugi...
]
Matteo Mortari commented on DROOLS-3236:
----------------------------------------
My wild guess is that since 7.10.0.Final for some reason the kie-maven-plugin is passing
an empty-set (that {{goals = '[]'}}) as the execution information metadata to
Maven, hence m2eclipse is reporting the error.
I believe the line is:
https://github.com/eclipse/m2e-core/blob/c304dad55ce0f80d2cfcf75497280148...
The full error is:
{code:java}
ENTRY org.eclipse.core.resources 4 75 2018-11-05 14:19:41.206
!MESSAGE Errors occurred during the build.
!SUBENTRY 1 org.eclipse.m2e.core 4 75 2018-11-05 14:19:41.206
!MESSAGE Errors running builder 'Maven Project Builder' on project
'test-generateModel-kjararchetype'.
!STACK 0
java.lang.IllegalArgumentException: Missing parameter for pluginExecutionFilter. groupId,
artifactId, versionRange and goals must be specificed, but found: groupId =
'org.kie'
artifactId = 'kie-maven-plugin'
versionRange = '7.14.0-SNAPSHOT'
goals = '[]'
at
org.eclipse.m2e.core.internal.lifecyclemapping.model.PluginExecutionFilter.checkAllFieldsSet(PluginExecutionFilter.java:320)
at
org.eclipse.m2e.core.internal.lifecyclemapping.model.PluginExecutionFilter.match(PluginExecutionFilter.java:331)
at
org.eclipse.m2e.core.internal.lifecyclemapping.SimpleMappingMetadataSource.getPluginExecutionMetadata(SimpleMappingMetadataSource.java:79)
at
org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata0(LifecycleMappingFactory.java:599)
at
org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata(LifecycleMappingFactory.java:535)
at
org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata(LifecycleMappingFactory.java:249)
at
org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateLifecycleMapping(LifecycleMappingFactory.java:181)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupLifecycleMapping(ProjectRegistryManager.java:594)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refreshPhase2(ProjectRegistryManager.java:513)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$3.call(ProjectRegistryManager.java:492)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$3.call(ProjectRegistryManager.java:1)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:496)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:351)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:298)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:155)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:90)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:87)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:201)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:798)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:219)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:262)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:315)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:318)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:370)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:391)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:145)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
{code}
Unable to open KJAR project in eclipse due to "Missing parameter
for pluginExecutionFilter"
-------------------------------------------------------------------------------------------
Key: DROOLS-3236
URL: https://issues.jboss.org/browse/DROOLS-3236
Project: Drools
Issue Type: Bug
Components: tools
Affects Versions: 7.10.0.Final, 7.11.0.Final, 7.12.0.Final, 7.13.0.Final
Environment: Eclipse photon, Eclipse 2018 09, no special plugin
m2eclipse configured to do-not-manage/ignore any unknown plugin goal (easiest choice)
Reporter: Matteo Mortari
Assignee: Mario Fusco
Priority: Major
Attachments: image-2018-11-05-10-28-50-255.png
Since 7.10.0.Final the following error occurs when opening a KJAR project in Eclipse:
!image-2018-11-05-10-28-50-255.png!
Errors occurred during the build.
Errors running builder 'Maven Project Builder' on project '...'.
Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals
must be specificed, but found: groupId = 'org.kie'
artifactId = 'kie-maven-plugin'
versionRange = '7.10.0.Final'
goals = '[]'
Please notice kie-maven-plugin 7.9.0.Final and earlier do NOT exhibit this issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
2780
days inactive
2780
days old
0 comments
1 participants
participants (1)
-
Matteo Mortari (Jira)