You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/10/26 13:24:59 UTC
[jira] [Created] (SLING-6190) More gracefully deal with non
existing natures during project import
Konrad Windszus created SLING-6190:
--------------------------------------
Summary: More gracefully deal with non existing natures during project import
Key: SLING-6190
URL: https://issues.apache.org/jira/browse/SLING-6190
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.1.0
Reporter: Konrad Windszus
Fix For: Sling Eclipse IDE 1.1.2
The project configurator from SLING-3100 fails in case a nature is not available. E.g. with this stack trace in case
{code}
WARNING: org.eclipse.core.resources code=568 Problems encountered while setting project description.
at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1255)
at org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator.addNatures(ContentPackageProjectConfigurator.java:115)
at org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator.access$1(ContentPackageProjectConfigurator.java:103)
at org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator$WtpProjectConfigurer.configure(ContentPackageProjectConfigurator.java:139)
at org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator.configure(ContentPackageProjectConfigurator.java:91)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
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.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
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.embedder.MavenImpl.execute(MavenImpl.java:1355)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
...
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
WARNING: org.eclipse.core.resources code=35 Nature does not exist: org.eclipse.wst.jsdt.core.jsNature.
{code}
We should deal more gracefully with missing natures (which are not enforced at all by Sling IDE e.g. through required bundles)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)