[jira] [Commented] (SLING-6190) More gracefully deal with non existing natures during project import

2017-08-17 Thread Robert Munteanu (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130396#comment-16130396
 ] 

Robert Munteanu commented on SLING-6190:


Added missing import in manifest in [r1805284|https://svn.apache.org/r1805284]

> 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
>Assignee: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.2.0
>
>
> The project configurator from SLING-3100 fails in case a nature is not 
> available. E.g. with this stack trace in case JSDT is not available:
> {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.4.14#64029)

[jira] [Commented] (SLING-6190) More gracefully deal with non existing natures during project import

2016-10-26 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608456#comment-15608456
 ] 

Konrad Windszus commented on SLING-6190:


All existing natures can be listed via {{workspace.getNatureDescriptors()}} 
(http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2FresAdv_natures.htm).

> 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)