[jbosstools-issues] [JBoss JIRA] (JBIDE-20251) m2e exception occurs after importing freemarker editor plugin into eclipse workspace
Denis Golovin (JIRA)
issues at jboss.org
Thu Jul 9 20:59:02 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-20251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Golovin updated JBIDE-20251:
----------------------------------
Summary: m2e exception occurs after importing freemarker editor plugin into eclipse workspace (was: m2e exception after importing freemarker editor plugin into eclipse workspace)
> m2e exception occurs after importing freemarker editor plugin into eclipse workspace
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-20251
> URL: https://issues.jboss.org/browse/JBIDE-20251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Denis Golovin
>
> Right after freemarker imported into workspace, m2e builder throws exception:
> {code}!ENTRY org.eclipse.core.resources 4 75 2015-07-09 17:41:50.488
> !MESSAGE Errors occurred during the build.
> !SUBENTRY 1 org.eclipse.m2e.core 4 75 2015-07-09 17:41:50.488
> !MESSAGE Errors running builder 'Maven Project Builder' on project 'org.jboss.ide.eclipse.freemarker'.
> !STACK 0
> java.lang.IllegalArgumentException: Path must include project and resource name: /org.jboss.ide.eclipse.freemarker
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2069)
> at org.eclipse.core.internal.resources.Container.getFolder(Container.java:201)
> at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.refreshResources(MavenBuilderImpl.java:246)
> at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:175)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> 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:86)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> which happens because freemarker dependency jar is placet in project root. Moving to sub-folder lib solves the issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list