[JBoss JIRA] (TOOLSDOC-628) JBDS-IS 8.0.1 RN: QE and PM Review
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-628?page=com.atlassian.jira.plug... ]
Misha Ali edited comment on TOOLSDOC-628 at 4/14/15 9:53 PM:
-------------------------------------------------------------
Sorry about that, Andrej. I've fixed up the issues and removed the FUSETOOLS-956 issue. Please have a look now.
was (Author: mhusnain):
Sorry about that, Adrej. I've fixed up the issues and removed the FUSETOOLS-956 issue. Please have a look now.
> JBDS-IS 8.0.1 RN: QE and PM Review
> ----------------------------------
>
> Key: TOOLSDOC-628
> URL: https://issues.jboss.org/browse/TOOLSDOC-628
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Components: Release Notes
> Reporter: Misha Ali
> Assignee: Andrej Podhradsky
>
> Asked [~pleacu] and [~apodhrad] to have a look at the draft version of the Release Notes and provide feedback on any missing items or changes required.
> Waiting on Bob (or someone else) to confirm whether all BPMN2 1.1.2 issues should be included or if we need a subset.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-628) JBDS-IS 8.0.1 RN: QE and PM Review
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-628?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-628:
------------------------------------
Sorry about that, Adrej. I've fixed up the issues and removed the FUSETOOLS-956 issue. Please have a look now.
> JBDS-IS 8.0.1 RN: QE and PM Review
> ----------------------------------
>
> Key: TOOLSDOC-628
> URL: https://issues.jboss.org/browse/TOOLSDOC-628
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Components: Release Notes
> Reporter: Misha Ali
> Assignee: Andrej Podhradsky
>
> Asked [~pleacu] and [~apodhrad] to have a look at the draft version of the Release Notes and provide feedback on any missing items or changes required.
> Waiting on Bob (or someone else) to confirm whether all BPMN2 1.1.2 issues should be included or if we need a subset.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19590:
---------------------------------------
Sounds like a simplest possible solution. It also easy to explain in readme.
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3354:
-----------------------------------
I've remove the maven portlet feature from the installer, since it dragged portlet which dragged seam2.
Now the only seam components left in the installer are :
- org.jboss.tools.jsf.vpe.seam
- org.jboss.tools.cdi.seam.solder.core
> Seam 2 is still included in JBDS 9 Alpha1 installed from jar
> ------------------------------------------------------------
>
> Key: JBDS-3354
> URL: https://issues.jboss.org/browse/JBDS-3354
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, cdi, seam
> Affects Versions: 9.0.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
>
> It seems to me that we removed the wrong feature.
> This is JBDS 8.0.2:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116
> org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79
> {code}
> And this is JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:features rasp$ ls |grep seam
> org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3
> {code}
> When you look at plugins, it looks as follows:
> JBDS 8.0.2:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79
> org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar
> org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar
> org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar
> {code}
> JBDS 9.0.0.Alpha1 B11:
> {code}
> nattura:plugins rasp$ ls|grep seam
> org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3
> org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar
> org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar
> {code}
> For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19150) Failed while installing JPA 2.0
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19150?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-19150:
-------------------------------------
Rastislav, can you try again with latest JBT/JBDS build? I tried twice with an empty maven repo but couldn't reproduce.
Some changes I made in m2e-wtp 1.2 might have helped (http://git.eclipse.org/c/m2e-wtp/org.eclipse.m2e.wtp.jpa.git/commit/?id=d...)
> Failed while installing JPA 2.0
> -------------------------------
>
> Key: JBIDE-19150
> URL: https://issues.jboss.org/browse/JBIDE-19150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, maven, project-examples
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2.GA, EAP 6.1
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha2
>
> Attachments: JPA_error.png
>
>
> I got "Failed while installing JPA 2.0" error after I clicked on Finish when importing Java EE Web Project from central.
> I found 7 exceptions in error log
> {code}
> java.lang.reflect.InvocationTargetException
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:421)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> Caused by: org.eclipse.wst.common.project.facet.core.FacetedProjectFrameworkException: Failed while installing JPA 2.0.
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1507)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:154)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:109)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:250)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:163)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:109)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:133)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:789)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:719)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$5.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:109)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects(ProjectConfigurationManager.java:717)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:382)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4$1.call(ArchetypeExamplesWizardPage.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4.run(ArchetypeExamplesWizardPage.java:377)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:419)
> ... 1 more
> Caused by: java.lang.NullPointerException
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.defaultResourceLocation(JpaFacetInstallDelegate.java:123)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createPersistenceXml(JpaFacetInstallDelegate.java:107)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createProjectXml(JpaFacetInstallDelegate.java:100)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:61)
> at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:35)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
> ... 40 more
> {code}
> {code}
> java.lang.NullPointerException
> at org.eclipse.jst.jsf.facelet.core.internal.cm.attributevalues.TemplateWebPathType.getWebRoot(TemplateWebPathType.java:150)
> at org.eclipse.jst.jsf.taglibprocessing.attributevalues.WebPathType.validateFileRelativeToWebRoot(WebPathType.java:59)
> at org.eclipse.jst.jsf.taglibprocessing.attributevalues.WebPathType.isValidValue(WebPathType.java:48)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateNonELAttributeValue(AttributeValidatingStrategy.java:702)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.access$1(AttributeValidatingStrategy.java:672)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy$1.run(AttributeValidatingStrategy.java:186)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateAttributeValue(AttributeValidatingStrategy.java:168)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validate(AttributeValidatingStrategy.java:144)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateTag(XMLViewDefnValidator.java:99)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateRegions(XMLViewDefnValidator.java:177)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateView(XMLViewDefnValidator.java:134)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.DefaultFaceletValidationStrategy.doValidate(DefaultFaceletValidationStrategy.java:42)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.AbstractFaceletValidationStrategy.validateFile(AbstractFaceletValidationStrategy.java:96)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.HTMLValidator.validate(HTMLValidator.java:57)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:126)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:85)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:95)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:124)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:108)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}
> java.lang.NullPointerException
> at org.eclipse.jst.jsf.facelet.core.internal.cm.attributevalues.TemplateWebPathType.getWebRoot(TemplateWebPathType.java:150)
> at org.eclipse.jst.jsf.taglibprocessing.attributevalues.WebPathType.validateFileRelativeToWebRoot(WebPathType.java:59)
> at org.eclipse.jst.jsf.taglibprocessing.attributevalues.WebPathType.isValidValue(WebPathType.java:48)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateNonELAttributeValue(AttributeValidatingStrategy.java:702)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.access$1(AttributeValidatingStrategy.java:672)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy$1.run(AttributeValidatingStrategy.java:186)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateAttributeValue(AttributeValidatingStrategy.java:168)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validate(AttributeValidatingStrategy.java:144)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateTag(XMLViewDefnValidator.java:99)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateRegions(XMLViewDefnValidator.java:177)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateView(XMLViewDefnValidator.java:134)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.DefaultFaceletValidationStrategy.doValidate(DefaultFaceletValidationStrategy.java:42)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.AbstractFaceletValidationStrategy.validateFile(AbstractFaceletValidationStrategy.java:96)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.HTMLValidator.validate(HTMLValidator.java:57)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:126)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:85)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:95)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:124)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:108)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}
> java.lang.NullPointerException: No IModelProvider exists for project P/jboss-javaee6-webapp of version: null
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:101)
> at org.eclipse.jst.j2ee.model.ModelProviderManager.getModelProvider(ModelProviderManager.java:281)
> at org.eclipse.jst.jsf.core.jsfappconfig.ContextParamSpecifiedJSFAppConfigLocater.getModelObject(ContextParamSpecifiedJSFAppConfigLocater.java:76)
> at org.eclipse.jst.jsf.core.jsfappconfig.ContextParamSpecifiedJSFAppConfigLocater.startLocating(ContextParamSpecifiedJSFAppConfigLocater.java:51)
> at org.eclipse.jst.jsf.core.jsfappconfig.internal.AbstractJSFAppConfigManager$1.run(AbstractJSFAppConfigManager.java:143)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.jsf.core.jsfappconfig.internal.AbstractJSFAppConfigManager.startConfigLocaters(AbstractJSFAppConfigManager.java:137)
> at org.eclipse.jst.jsf.core.jsfappconfig.internal.AbstractJSFAppConfigManager.initialize(AbstractJSFAppConfigManager.java:116)
> at org.eclipse.jst.jsf.core.jsfappconfig.internal.AbstractJSFAppConfigManager.<init>(AbstractJSFAppConfigManager.java:92)
> at org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager.<init>(JSFAppConfigManager.java:40)
> at org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager.<init>(JSFAppConfigManager.java:39)
> at org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager$JSFAppConfigManagerFactory.createNewInstance(JSFAppConfigManager.java:163)
> at org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager$JSFAppConfigManagerFactory.createNewInstance(JSFAppConfigManager.java:1)
> at org.eclipse.jst.jsf.common.internal.resource.ResourceSingletonObjectManager.getInstance(ResourceSingletonObjectManager.java:90)
> at org.eclipse.jst.jsf.core.jsfappconfig.JSFAppConfigManager.getInstance(JSFAppConfigManager.java:53)
> at org.eclipse.jst.jsf.core.jsfappconfig.internal.DefaultJSFAppConfigManagerProviderStrategy$DefaultProvider.getInstance(DefaultJSFAppConfigManagerProviderStrategy.java:23)
> at org.eclipse.jst.jsf.core.jsfappconfig.internal.JSFAppConfigManagerFactory.createNewInstance(JSFAppConfigManagerFactory.java:60)
> at org.eclipse.jst.jsf.core.jsfappconfig.internal.JSFAppConfigManagerFactory.createNewInstance(JSFAppConfigManagerFactory.java:1)
> at org.eclipse.jst.jsf.common.internal.resource.ResourceSingletonObjectManager.getInstance(ResourceSingletonObjectManager.java:90)
> at org.eclipse.jst.jsf.core.jsfappconfig.internal.JSFAppConfigManagerFactory.getJSFAppConfigManagerInstance(JSFAppConfigManagerFactory.java:41)
> at org.eclipse.jst.jsf.designtime.symbols.DefaultBeanSymbolSourceProvider.getManagedBeanSymbols(DefaultBeanSymbolSourceProvider.java:124)
> at org.eclipse.jst.jsf.designtime.symbols.DefaultBeanSymbolSourceProvider.getSymbols(DefaultBeanSymbolSourceProvider.java:87)
> at org.eclipse.jst.jsf.designtime.symbols.DefaultBeanSymbolSourceProvider.getSymbol(DefaultBeanSymbolSourceProvider.java:104)
> at org.eclipse.jst.jsf.designtime.el.DefaultDTVariableResolver.resolveVariable(DefaultDTVariableResolver.java:86)
> at org.eclipse.jst.jsf.designtime.internal.symbols.ConfigBasedDTVariableResolver.resolveVariable(ConfigBasedDTVariableResolver.java:108)
> at org.eclipse.jst.jsf.designtime.resolver.SymbolContextResolver.getVariable(SymbolContextResolver.java:61)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.visit(ASTSemanticValidator.java:354)
> at org.eclipse.jst.jsp.core.internal.java.jspel.ASTValuePrefix.jjtAccept(ASTValuePrefix.java:28)
> at org.eclipse.jst.jsp.core.internal.java.jspel.SimpleNode.childrenAccept(SimpleNode.java:70)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.visit(ASTSemanticValidator.java:324)
> at org.eclipse.jst.jsp.core.internal.java.jspel.ASTValue.jjtAccept(ASTValue.java:28)
> at org.eclipse.jst.jsp.core.internal.java.jspel.SimpleNode.childrenAccept(SimpleNode.java:70)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.visit(ASTSemanticValidator.java:277)
> at org.eclipse.jst.jsp.core.internal.java.jspel.ASTUnaryExpression.jjtAccept(ASTUnaryExpression.java:28)
> at org.eclipse.jst.jsp.core.internal.java.jspel.SimpleNode.childrenAccept(SimpleNode.java:70)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.visit(ASTSemanticValidator.java:175)
> at org.eclipse.jst.jsp.core.internal.java.jspel.ASTExpression.jjtAccept(ASTExpression.java:28)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.validate(ASTSemanticValidator.java:109)
> at org.eclipse.jst.jsf.validation.internal.el.ELExpressionValidator.validateSemantics(ELExpressionValidator.java:183)
> at org.eclipse.jst.jsf.validation.internal.el.ELExpressionValidator.validateXMLNode(ELExpressionValidator.java:80)
> at org.eclipse.jst.jsf.designtime.symbols.JSFSymbolFactory.getValueTypeFromEL(JSFSymbolFactory.java:86)
> at org.eclipse.jst.jsf.designtime.symbols.JSFSymbolFactory.getValueTypeFromEL(JSFSymbolFactory.java:109)
> at org.eclipse.jst.jsf.designtime.symbols.DefaultDataTableSymbolFactory.createSymbolForDataTableValue(DefaultDataTableSymbolFactory.java:74)
> at org.eclipse.jst.jsf.designtime.internal.jsp.DataModelVariableFactory.createSymbolForDataTableValue(DataModelVariableFactory.java:55)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPDefaultSymbolFactory.handleHtmlTags(JSPDefaultSymbolFactory.java:132)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPDefaultSymbolFactory.handleSymbolCreation(JSPDefaultSymbolFactory.java:107)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPDefaultSymbolFactory.internalCreate(JSPDefaultSymbolFactory.java:73)
> at org.eclipse.jst.jsf.context.symbol.source.AbstractContextSymbolFactory.create(AbstractContextSymbolFactory.java:92)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.processSymbolContrib(JSPModelProcessor.java:553)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.processAttributes(JSPModelProcessor.java:524)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.recurseChildNodes(JSPModelProcessor.java:506)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.recurseChildNodes(JSPModelProcessor.java:507)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.recurseChildNodes(JSPModelProcessor.java:507)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.refreshInternal(JSPModelProcessor.java:492)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.access$3(JSPModelProcessor.java:474)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor$RefreshRunnable.run(JSPModelProcessor.java:447)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.runOnCurrentThread(JSPModelProcessor.java:411)
> at org.eclipse.jst.jsf.designtime.internal.jsp.JSPModelProcessor.refresh(JSPModelProcessor.java:363)
> at org.eclipse.jst.jsf.designtime.internal.symbols.JSPTagVariableSymbolSourceProvider.getSymbols(JSPTagVariableSymbolSourceProvider.java:62)
> at org.eclipse.jst.jsf.designtime.context.DTJSPExternalContext.doGetMapForScope(DTJSPExternalContext.java:87)
> at org.eclipse.jst.jsf.designtime.context.AbstractDTExternalContext.getMapForScope(AbstractDTExternalContext.java:46)
> at org.eclipse.jst.jsf.designtime.context.AbstractDTExternalContext.getRequestMap(AbstractDTExternalContext.java:64)
> at org.eclipse.jst.jsf.designtime.el.DefaultDTVariableResolver.resolveVariable(DefaultDTVariableResolver.java:67)
> at org.eclipse.jst.jsf.designtime.internal.symbols.ConfigBasedDTVariableResolver.resolveVariable(ConfigBasedDTVariableResolver.java:108)
> at org.eclipse.jst.jsf.designtime.resolver.SymbolContextResolver.getVariable(SymbolContextResolver.java:61)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.visit(ASTSemanticValidator.java:354)
> at org.eclipse.jst.jsp.core.internal.java.jspel.ASTValuePrefix.jjtAccept(ASTValuePrefix.java:28)
> at org.eclipse.jst.jsp.core.internal.java.jspel.SimpleNode.childrenAccept(SimpleNode.java:70)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.visit(ASTSemanticValidator.java:324)
> at org.eclipse.jst.jsp.core.internal.java.jspel.ASTValue.jjtAccept(ASTValue.java:28)
> at org.eclipse.jst.jsp.core.internal.java.jspel.SimpleNode.childrenAccept(SimpleNode.java:70)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.visit(ASTSemanticValidator.java:277)
> at org.eclipse.jst.jsp.core.internal.java.jspel.ASTUnaryExpression.jjtAccept(ASTUnaryExpression.java:28)
> at org.eclipse.jst.jsp.core.internal.java.jspel.SimpleNode.childrenAccept(SimpleNode.java:70)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.visit(ASTSemanticValidator.java:175)
> at org.eclipse.jst.jsp.core.internal.java.jspel.ASTExpression.jjtAccept(ASTExpression.java:28)
> at org.eclipse.jst.jsf.validation.internal.el.ASTSemanticValidator.validate(ASTSemanticValidator.java:109)
> at org.eclipse.jst.jsf.validation.internal.el.ELExpressionValidator.validateSemantics(ELExpressionValidator.java:183)
> at org.eclipse.jst.jsf.validation.internal.el.ELExpressionValidator.validateXMLNode(ELExpressionValidator.java:80)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateELExpression(AttributeValidatingStrategy.java:367)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.checkIfELAndValidate(AttributeValidatingStrategy.java:275)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.access$0(AttributeValidatingStrategy.java:192)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy$1.run(AttributeValidatingStrategy.java:184)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateAttributeValue(AttributeValidatingStrategy.java:168)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validate(AttributeValidatingStrategy.java:144)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateTag(XMLViewDefnValidator.java:99)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateRegions(XMLViewDefnValidator.java:177)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateView(XMLViewDefnValidator.java:134)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.DefaultFaceletValidationStrategy.doValidate(DefaultFaceletValidationStrategy.java:42)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.AbstractFaceletValidationStrategy.validateFile(AbstractFaceletValidationStrategy.java:96)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.HTMLValidator.validate(HTMLValidator.java:57)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:126)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:85)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:95)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:124)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:108)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}
> java.lang.NullPointerException
> at org.eclipse.jst.jsf.facelet.core.internal.cm.attributevalues.TemplateWebPathType.getWebRoot(TemplateWebPathType.java:150)
> at org.eclipse.jst.jsf.taglibprocessing.attributevalues.WebPathType.validateFileRelativeToWebRoot(WebPathType.java:59)
> at org.eclipse.jst.jsf.taglibprocessing.attributevalues.WebPathType.isValidValue(WebPathType.java:48)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateNonELAttributeValue(AttributeValidatingStrategy.java:702)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.access$1(AttributeValidatingStrategy.java:672)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy$1.run(AttributeValidatingStrategy.java:186)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateAttributeValue(AttributeValidatingStrategy.java:168)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validate(AttributeValidatingStrategy.java:144)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateTag(XMLViewDefnValidator.java:99)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateRegions(XMLViewDefnValidator.java:177)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateView(XMLViewDefnValidator.java:134)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.DefaultFaceletValidationStrategy.doValidate(DefaultFaceletValidationStrategy.java:42)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.AbstractFaceletValidationStrategy.validateFile(AbstractFaceletValidationStrategy.java:96)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.HTMLValidator.validate(HTMLValidator.java:57)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:783)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:126)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:85)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:95)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:124)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:108)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}
> java.lang.NullPointerException
> at org.eclipse.jst.jsf.facelet.core.internal.cm.attributevalues.TemplateWebPathType.getWebRoot(TemplateWebPathType.java:150)
> at org.eclipse.jst.jsf.taglibprocessing.attributevalues.WebPathType.validateFileRelativeToWebRoot(WebPathType.java:59)
> at org.eclipse.jst.jsf.taglibprocessing.attributevalues.WebPathType.isValidValue(WebPathType.java:48)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateNonELAttributeValue(AttributeValidatingStrategy.java:702)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.access$1(AttributeValidatingStrategy.java:672)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy$1.run(AttributeValidatingStrategy.java:186)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateAttributeValue(AttributeValidatingStrategy.java:168)
> at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validate(AttributeValidatingStrategy.java:144)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateTag(XMLViewDefnValidator.java:99)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateRegions(XMLViewDefnValidator.java:177)
> at org.eclipse.jst.jsf.validation.internal.XMLViewDefnValidator.validateView(XMLViewDefnValidator.java:134)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.DefaultFaceletValidationStrategy.doValidate(DefaultFaceletValidationStrategy.java:42)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.AbstractFaceletValidationStrategy.validateFile(AbstractFaceletValidationStrategy.java:96)
> at org.eclipse.jst.jsf.facelet.ui.internal.validation.HTMLValidator.validate(HTMLValidator.java:57)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:783)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:126)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:85)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:95)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:124)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:108)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}
> java.lang.NullPointerException
> at org.eclipse.m2e.core.project.MavenUpdateRequest.addPomFile(MavenUpdateRequest.java:83)
> at org.eclipse.m2e.core.project.MavenUpdateRequest.<init>(MavenUpdateRequest.java:60)
> at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:76)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> I've reproduced the issue 3 times on OSX but not with 100% success
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18348) Add support for WildFly 9
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18348?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18348:
-------------------------------------
Stumbled on the same issue today. Also, we need to keep in mind Wildfly comes with a web (aka light) version (~27MB). It's properly detected as such (WILDFLY-WEB), but the server is not created automatically, as Martin described.
> Add support for WildFly 9
> -------------------------
>
> Key: JBIDE-18348
> URL: https://issues.jboss.org/browse/JBIDE-18348
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
>
> Now that WildFly 9.0.0.Alpha1 is out, we need to make sure it works properly with JBT/JBDS.
> I played with it a little, tried to start/stop, deploy a project and so far I haven't seen any issue.
> Other than the one expected that is - when you add the server, you get a warning that the runtime version doesn't match - it detected 9, but 8 is expected. We need to deal with this somehow.
> Runtime detection doesn't work. It find the server (although with a strange Type of "WILDFLY-FULL"), but doesn't actually add it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3018) Install screen moves to bottom left corner of the screen
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3018?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3018:
--------------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #2 April 2015 (was: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015)
> Install screen moves to bottom left corner of the screen
> --------------------------------------------------------
>
> Key: JBDS-3018
> URL: https://issues.jboss.org/browse/JBDS-3018
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 7.1.1.GA
> Environment: java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> OSX 10.9.2
> One monitor
> No additional software for windows management
> Reporter: Arun Gupta
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 8.x, 9.0.x
>
> Attachments: Screen Shot 2014-04-21 at 9.07.53 PM.png
>
>
> I started the install as
> java -jar ~/Downloads/jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar
> Install screen (step 1 of 9) popped up in the middle and then right away went in the bottom left corner of the screen as shown in attachment.
> This does not seem right.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3012) JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3012?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3012:
--------------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #2 April 2015 (was: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015)
> JBDS 7.1.1 installer contains jars signed by GTECyberTrust, which may not be installed on all linux systems
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3012
> URL: https://issues.jboss.org/browse/JBDS-3012
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, updatesite
> Affects Versions: 7.1.1.GA
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Fix For: 7.1.x
>
>
> We have jars in JBDS 7.1.1.GA which were signed using GTECyberTrust. Some linux installs do not include this root cert, so when installing, p2 rejects the cert:
> {code}One or more certificates rejected. Cannot proceed with installation.{code}
> Full details: https://community.jboss.org/message/866868
> *Platform details:*
> {code}
> Debian Jessie 64 bit
> $ uname -a:
> Linux Name 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 GNU/Linux
> $ java -version
> java version "1.7.0_51"
> OpenJDK Runtime Environment (IcedTea 2.4.5) (7u51-2.4.5-2)
> OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
> {code}
> Note that Debian 8.0 "Jessie" is not yet released nor has a date for release been announced [0]. The latest stable Debian [1] is 7.4 "Wheezy", released on Feb 8, 2014. [2] The description for "testing" releases like Jessie is "Security updates are irregular and unreliable." [3] So... I don't think we support this OS yet. :)
> [0] http://www.debian.org/releases/jessie/
> [1] http://www.debian.org/releases/
> [2] http://www.debian.org/releases/wheezy/
> [3] https://release.debian.org/
> *Steps to repro on the above platform:*
> 1. Downloaded jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar
> 2. Ran java -jar jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar stuck to the defaults and clicked thru
> 3. Install failed with an error re certificates not being trusted
> 4. Log message in ~/jbdevstudio/studio/p2/director/configuration/1396752621141.log as follows:
> !ENTRY org.eclipse.equinox.p2.engine 8 0 2014-04-06 08:21:42.061
> !MESSAGE One or more certificates rejected. Cannot proceed with installation.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17696:
----------------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #2 April 2015 (was: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015)
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Assignee: Denis Golovin
> Fix For: 4.3.0.Alpha2
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2635:
--------------------------------
Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #3 May 2015 (was: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015)
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 9.0.0.Alpha2
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18950:
-----------------------------------
Sprint: Sprint #1 April 2015 (was: Sprint #2 April 2015)
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Artifact: [combo]
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Class name: [text]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name
> | - Name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [table editor with 'Property name' and 'Field name' columns]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18398) Shebang for Node.js is not supported
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18398?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-18398:
-----------------------------------------
Shebang will be supported by JSDT since WTP 3.7M7, see:
[Bug 462283 - JavaScript Editor complains on Shebang (#!) lines|https://bugs.eclipse.org/bugs/show_bug.cgi?id=462283]
> Shebang for Node.js is not supported
> -------------------------------------
>
> Key: JBIDE-18398
> URL: https://issues.jboss.org/browse/JBIDE-18398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1
> Reporter: Karel Piwko
> Assignee: Victor Rubezhny
> Fix For: 4.3.x
>
>
> Shebang in javascript file is reported by IDE as an error.
> {code}
> #!/usr/bin/env node
> /* jshint laxbreak:true */
> var util = require('util');
> var fs = require('fs');
> var prompt = require('prompt');
> {code}
> shows marker (x) with following text on line 1:
> Multiple markers at this line
> - Syntax error on tokens, delete these tokens
> - Syntax error on token "Invalid Regular Expression Options", no accurate correction
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19536:
----------------------------------------
[~rawagner] can you reproduce it manually? Maybe your bot test environment is responsible for that loop.
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta1
>
> Attachments: cdi_jstack
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19536:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta1
>
> Attachments: cdi_jstack
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19446) Completion proposal computers implementations should check content type before doing other computations
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19446?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19446:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Completion proposal computers implementations should check content type before doing other computations
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19446
> URL: https://issues.jboss.org/browse/JBIDE-19446
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: batch, cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta1
>
>
> BeansXmlCompletionProposalComputer should do computations only for beans.xml.
> BatchJobCompletionProposalComputer should do computations only for batch job xml.
> These computers are registered for different content types because Eclipse may bind any matching content type to file, including any xml content type. Implementation should start with the check if current xml file is relevant.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18997) Editor for batch.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18997?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18997:
-----------------------------------
Parent: (was: JBIDE-18857)
Issue Type: Feature Request (was: Sub-task)
> Editor for batch.xml
> --------------------
>
> Key: JBIDE-18997
> URL: https://issues.jboss.org/browse/JBIDE-18997
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.3.x
>
>
> It is a very simple xml:
> {code}
> <batch-artifacts xmlns="http://xmlns.jcp.org/xml/ns/javaee">
> <ref id="<reference-name>" class="<impl-class-name>" />
> </batch-artifacts>
> {code}
> that can be easily managed in a text editor, but for our tool completeness we may provide a Tree+Source editor for it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18996) Support batch.xml in Batch project model
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18996?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18996:
-----------------------------------
Parent: (was: JBIDE-18857)
Issue Type: Feature Request (was: Sub-task)
> Support batch.xml in Batch project model
> ----------------------------------------
>
> Key: JBIDE-18996
> URL: https://issues.jboss.org/browse/JBIDE-18996
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.x
>
>
> Default loading of batch artifacts described by JSR-352 is provided by batch.xml:
> {code}
> <batch-artifacts xmlns="http://xmlns.jcp.org/xml/ns/javaee">
> <ref id="<reference-name>" class="<impl-class-name>" />
> </batch-artifacts>
> {code}
> Batch implementations may define specific loaders and probably most popular is going to be the use of javax.inject.Named annotation.
> For the completeness, we have better to support the default way as well.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18950:
-----------------------------------
Sprint: Sprint #2 April 2015
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Artifact: [combo]
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Class name: [text]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name
> | - Name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [table editor with 'Property name' and 'Field name' columns]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18950:
-----------------------------------
Parent: (was: JBIDE-18857)
Issue Type: Feature Request (was: Sub-task)
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Artifact: [combo]
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Class name: [text]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name
> | - Name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [table editor with 'Property name' and 'Field name' columns]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-13904) Minor UI issues in "Configure Repositories" wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13904?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-13904 at 4/14/15 6:42 PM:
--------------------------------------------------------------
So I finally applied the fix to master, even though OSX still has the issue (JBIDE-19593). But I guess having Windows and Linux working is better than nothing.
was (Author: fbricon):
So I finally applied the fix to master, even though OSX still has the issue. But I guess having Windows and Linux working is better than nothing.
> Minor UI issues in "Configure Repositories" wizard
> --------------------------------------------------
>
> Key: JBIDE-13904
> URL: https://issues.jboss.org/browse/JBIDE-13904
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Minor
> Labels: uxp
> Fix For: 4.3.0.Alpha2
>
>
> In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
> * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels
> * Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-13904) Minor UI issues in "Configure Repositories" wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13904?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-13904:
-----------------------------------
Assignee: Snjezana Peco (was: Fred Bricon)
> Minor UI issues in "Configure Repositories" wizard
> --------------------------------------------------
>
> Key: JBIDE-13904
> URL: https://issues.jboss.org/browse/JBIDE-13904
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: uxp
> Fix For: 4.3.0.Alpha2
>
>
> In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
> * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels
> * Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18950:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> New Batch Artifact wizard
> -------------------------
>
> Key: JBIDE-18950
> URL: https://issues.jboss.org/browse/JBIDE-18950
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> There are about 20 artifacts in Java EE Batch:
> Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener.
> We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden).
> 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods);
> 2. Reference name should be provided for each artifact. There are 3 options:
> - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named;
> - META-INF/batch.xml
> - by default, when first 2 options failed reference name is tried as the qualified class name.
> 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact:
> {code}
> @Inject @BatchProperty(name="property1") String property;
> @Inject @BatchProperty String property2;
> {code}
> Thus, the wizard will have inputs as follows:
> - Artifact: [combo]
> - Source folder: [as in New Java Class wizard]
> - Package: [as in New Java Class wizard]
> - Class name: [text]
> - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled)
> - Reference name: (block of inputs)
> | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name
> | - Name: [text] (for first 2 options filled with default value; for the last option disabled)
> - Properties: [table editor with 'Property name' and 'Field name' columns]
> Some more inputs may be inherited from New Java Class wizard, if default values are not enough.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19593) Minor UI issues in "Configure Repositories" wizard on OSX
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19593?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19593:
--------------------------------
Description:
On OSX, In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
* The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels.
This was fixed for Windows/Linux in 4.3.0.Alpha2
was:
In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
* The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels
* Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml.
> Minor UI issues in "Configure Repositories" wizard on OSX
> ---------------------------------------------------------
>
> Key: JBIDE-19593
> URL: https://issues.jboss.org/browse/JBIDE-19593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Minor
> Labels: uxp
> Fix For: 4.3.x
>
>
> On OSX, In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
> * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels.
> This was fixed for Windows/Linux in 4.3.0.Alpha2
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19593) Minor UI issues in "Configure Repositories" wizard on OSX
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19593?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19593:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Alpha2)
> Minor UI issues in "Configure Repositories" wizard on OSX
> ---------------------------------------------------------
>
> Key: JBIDE-19593
> URL: https://issues.jboss.org/browse/JBIDE-19593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Minor
> Labels: uxp
> Fix For: 4.3.x
>
>
> On OSX, In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
> * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels.
> This was fixed for Windows/Linux in 4.3.0.Alpha2
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19593) Minor UI issues in "Configure Repositories" wizard on OSX
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19593?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-19593:
-----------------------------------
Assignee: (was: Fred Bricon)
> Minor UI issues in "Configure Repositories" wizard on OSX
> ---------------------------------------------------------
>
> Key: JBIDE-19593
> URL: https://issues.jboss.org/browse/JBIDE-19593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Reporter: Fred Bricon
> Priority: Minor
> Labels: uxp
> Fix For: 4.3.x
>
>
> On OSX, In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
> * The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels.
> This was fixed for Windows/Linux in 4.3.0.Alpha2
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19593) Minor UI issues in "Configure Repositories" wizard on OSX
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-19593:
-----------------------------------
Summary: Minor UI issues in "Configure Repositories" wizard on OSX
Key: JBIDE-19593
URL: https://issues.jboss.org/browse/JBIDE-19593
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Fred Bricon
Assignee: Fred Bricon
Priority: Minor
Fix For: 4.3.0.Alpha2
In the Window > Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories...
* The repo viewer should have a horizontal scroller, since adding the (inactive) suffix can make a pretty long label and you have to resize the whole dialog to be able to read the labels
* Edit a repo, switching the profile activation status : it reorders the repositories/profiles in settings.xml.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19281) Tern error when opening a jsp file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19281?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19281:
-----------------------------------
Sprint: Sprint #1 April 2015
> Tern error when opening a jsp file
> ----------------------------------
>
> Key: JBIDE-19281
> URL: https://issues.jboss.org/browse/JBIDE-19281
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.3.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.3.0.Alpha2
>
> Attachments: tern-error.png
>
>
> I was just verying something in master for Rob and hit this issue:
> I created a dynamic web project, then a jsp file. Once the jsp was opened in Eclipse, I got this error popup immediately:
> !tern-error.png!
> This was in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2015-01-29 17:04:14.678
> !MESSAGE An internal error occurred during: "Refresh tern project job".
> !STACK 0
> java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/dynproj2
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134)
> at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333)
> at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85)
> at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:298)
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:118)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2251)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1347)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1401)
> at tern.eclipse.ide.internal.core.builder.TernBuilder.addTernBuilder(TernBuilder.java:231)
> at tern.eclipse.ide.internal.core.resources.IDETernProject.doLoad(IDETernProject.java:186)
> at tern.resources.TernProject.load(TernProject.java:332)
> at tern.eclipse.ide.internal.core.resources.RefreshTernProjectJob.runInWorkspace(RefreshTernProjectJob.java:49)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This was JBT nightly from today (2015/01/29) from http://download.jboss.org/jbosstools/updates/nightly/mars/ on top of Eclipse Mars M4. On top of that, I had one server PR of Rob's installed, but that shouldn't have any effect.
> My platform is OS X 10.10 Yosemite, running Oracle JDK 1.7.
> I realize this is master and it might be a known issue, but better to be safe :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18968) IllegalArgumentException: "Argument not valid" occurs every time central is opened
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18968?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18968:
--------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> IllegalArgumentException: "Argument not valid" occurs every time central is opened
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-18968
> URL: https://issues.jboss.org/browse/JBIDE-18968
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.2.1.Final
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
>
> {code}java.lang.IllegalArgumentException: Argument not valid
> at org.eclipse.swt.SWT.error(SWT.java:4422)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.graphics.Image.init(Image.java:1294)
> at org.eclipse.swt.graphics.Image.<init>(Image.java:200)
> at org.eclipse.ui.forms.widgets.Section.onPaint(Section.java:344)
> at org.eclipse.ui.forms.widgets.ExpandableComposite$1.paintControl(ExpandableComposite.java:561)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:230)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Control.gtk_draw(Control.java:3174)
> at org.eclipse.swt.widgets.Canvas.gtk_draw(Canvas.java:171)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2060)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5513)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4668)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9106)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._gdk_window_process_all_updates(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gdk_window_process_all_updates(OS.java:5946)
> at org.eclipse.swt.widgets.Display.update(Display.java:4621)
> at org.eclipse.swt.widgets.Display.runDeferredLayouts(Display.java:3825)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3396)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19590:
---------------------------------------------
i've been wondering if we could have an eclipse project import set for each module that defines which to import.
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3285:
-------------------------------------------
difference between hide and fix ? fix it - that users not having m2e installed will be able to use it, hide it - stll broken ;)
Sounds like .project importer should block out sub dirs too somehow (different jira/issues)
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3285:
--------------------------------------
What's the difference between hide and fix?
Explanation is that the classes/ folder contains META-INF/MANIFEST.MF (which is currently detected as a PDE plugin - that's something to improve, but that's another topic), so the PDE detector applies.
However, when you have the Maven detector, it first detects your project as a Maven project, and it also computes a list of directories to exclude from analysis. In the case of Maven, it's the target/ folder. So the import framework just know that it doesn't have to get into the target/ folder in that case, and does try to import its content.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17591:
----------------------------------------
Sprint: Sprint to Beta3 Release (was: Sprint to Beta3 Release, Sprint #2 April 2015)
> org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
> ---------------------------------------------------------------
>
> Key: JBIDE-17591
> URL: https://issues.jboss.org/browse/JBIDE-17591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks
> Reporter: Denis Golovin
> Assignee: Daniel Azarov
> Fix For: 4.3.x
>
> Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt
>
>
> {code}junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen edited comment on JBDS-3285 at 4/14/15 3:49 PM:
--------------------------------------------------------------------
Looking at fred's .zip file this definitely should not result in 2 projects created - the .project file in the root should make everything else below not relevant unless there is another clear project "marker".
And osgi/pde should not think if it finds a manifest.mf is enough to create a project - it should also find some .java source.
So even without ordering the current configurators are not great and will fail if users don't have m2e loaded etc to catch this case (for example).
I still think we should add it into alpha2 but we definitely must improve this API for beta1 since these are things we already knew about back in november and we got plenty of usecases now.
was (Author: maxandersen):
Looking at fred's .zip file this definitely should not result in 2 projects created - the .project file in the root should make everything else below not relevant unless there is another clear project "marker".
And osgi/pde should not think if it finds a manifest.mf is enough to create a project - it should also find some .java source.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3285:
-------------------------------------------
Looking at fred's .zip file this definitely should not result in 2 projects created - the .project file in the root should make everything else below not relevant unless there is another clear project "marker".
And osgi/pde should not think if it finds a manifest.mf is enough to create a project - it should also find some .java source.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19259) JSF or HTML5 support choosing issues
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19259?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-19259:
-------------------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> JSF or HTML5 support choosing issues
> ------------------------------------
>
> Key: JBIDE-19259
> URL: https://issues.jboss.org/browse/JBIDE-19259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.3.0.Alpha1
> Environment: Fedora 20 GNOME 64 bit, Open JDK 7, Alpha2-v20150212-0919-B9496
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Beta1
>
>
> # GKT2 + xulrunner loaded + JSF support enabled: HTML5 page not rendered - visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport
> # VPE Preference page should contain checkbox with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again"
> # When support is changed page is opened and then Eclipse is restarted it would look better if page won't be opened before Eclipse is restarted. Page should be opened after restart
> # With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works.
> # Confusing scenario #1:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Open .html page
> ## Restart Eclipse
> ## Close .html page
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed. It's confusing to ask this when page is closed.
> # Confusing scenario #2:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Restart Eclipse
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19360) JSF or HTML5 Support: don't show dialog for the first opened page
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19360?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-19360:
-------------------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> JSF or HTML5 Support: don't show dialog for the first opened page
> -----------------------------------------------------------------
>
> Key: JBIDE-19360
> URL: https://issues.jboss.org/browse/JBIDE-19360
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Affects Versions: 4.3.0.Alpha1
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Beta1
>
>
> Confusing scenario #2:
> * Set HTML5 support
> * Open .xhtml page and say "Stay with HTML5"
> * Restart Eclipse
> ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3200:
-------------------------------------------
the related bugzillas might give some pointers.
> Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-3200
> URL: https://issues.jboss.org/browse/JBDS-3200
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, upstream
> Affects Versions: 8.0.0.GA
> Environment: Mac OS X 10.10, JDK 1.8.0
> Reporter: Manuel Blechschmidt
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png
>
>
> Hello,
> I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here:
> https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014...
> Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store.
> {panel}
> "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer.
> Your security preferences allow installation of only app from the Mac App Store and identified developers.
> {panel}
> Right click on the file and then selecting open gives me the opportunity to ignore this warning.
> Nevertheless it might happen that users don't know this solution.
> Hope that helps
> Manuel
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3285:
-------------------------------------------
For me .project is obvious to be the one with the lowest priority, but high certainty it can import.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3285:
-------------------------------------------
Michael, we discussed this a tons of times - we need to solve this. And we've discussed many times solutions for it.
Please stop thinking you can handle this with a very basic simple API and UI.
The suggestions made for a long time is no where near old legacy system.
And exactly because Gradle and Maven can both be there we *must* handle this somehow.
"And if a Maven project doesn't define a JavaScript plugin, does that make that we shouldn't enable JSDT on a given webapp which includes many JavaScript files? If we have Bower and Maven, which one should have priority? Should we also define some "work together" rules? Where would they be defined?"
Maven would have priority to do the import and jsdt and bower could particiapte in addiitonal configuration.
"assume things have to work together" - you just described your self issues that don't work togheter.
The legacy import provided *no* such behavior and required users to manually do things - in this we would only ask if the priorities ended up in something conflicting. So if no issues = it just gets imported.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19505) Angular Code Assist doesn't work for jboss-kitchensink-angularjs app
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19505?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19505:
----------------------------------------
We need to document this case. Why it's not working.
> Angular Code Assist doesn't work for jboss-kitchensink-angularjs app
> --------------------------------------------------------------------
>
> Key: JBIDE-19505
> URL: https://issues.jboss.org/browse/JBIDE-19505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, Linux
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.3.0.Alpha2
>
>
> 1. Import jboss-kitchensink-angularjs from JBoss Central
> 2. Open partials/home.html page
> 3. Open Angular Explorer and lind modules > MemberService > MembersCtrl to controler
> 4. Find this line {code}<li ng-repeat="message in errorMessages">{{message}}</li>{code} and invoke Code Assist for {{m
> ERROR: Code Assist doesn't contain proposal for message variable
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19281) Tern error when opening a jsp file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19281?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19281:
----------------------------------------
Will be fixed by JBIDE-19592
> Tern error when opening a jsp file
> ----------------------------------
>
> Key: JBIDE-19281
> URL: https://issues.jboss.org/browse/JBIDE-19281
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.3.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.3.0.Alpha2
>
> Attachments: tern-error.png
>
>
> I was just verying something in master for Rob and hit this issue:
> I created a dynamic web project, then a jsp file. Once the jsp was opened in Eclipse, I got this error popup immediately:
> !tern-error.png!
> This was in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2015-01-29 17:04:14.678
> !MESSAGE An internal error occurred during: "Refresh tern project job".
> !STACK 0
> java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/dynproj2
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134)
> at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333)
> at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85)
> at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:298)
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:118)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2251)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1347)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1401)
> at tern.eclipse.ide.internal.core.builder.TernBuilder.addTernBuilder(TernBuilder.java:231)
> at tern.eclipse.ide.internal.core.resources.IDETernProject.doLoad(IDETernProject.java:186)
> at tern.resources.TernProject.load(TernProject.java:332)
> at tern.eclipse.ide.internal.core.resources.RefreshTernProjectJob.runInWorkspace(RefreshTernProjectJob.java:49)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This was JBT nightly from today (2015/01/29) from http://download.jboss.org/jbosstools/updates/nightly/mars/ on top of Eclipse Mars M4. On top of that, I had one server PR of Rob's installed, but that shouldn't have any effect.
> My platform is OS X 10.10 Yosemite, running Oracle JDK 1.7.
> I realize this is master and it might be a known issue, but better to be safe :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3285:
--------------------------------------
About import-me, I believe it works much better if you have the Maven configurator available (see latest version of PR ).
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Pavol Srna updated JBDS-3404:
-----------------------------
Fix Version/s: 9.0.0.Alpha2
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3285:
--------------------------------------
There is no clear priorities between frameworks/technologies/languages/buildtools.... Examples: Why would Gradle have priority over Maven, or vice-versa? And if a Maven project doesn't define a JavaScript plugin, does that make that we shouldn't enable JSDT on a given webapp which includes many JavaScript files? If we have Bower and Maven, which one should have priority? Should we also define some "work together" rules? Where would they be defined?
Dealing with priorities require every configurator to be aware of all other configurators in order to define priorities/compatibilities...
I've thought about it while designing the API, and I came to the conclusion that priorities are a quite complex and weak workaround for things don't work together. It's IMO more scalable to just assume that things have to work together.
About giving choice to the user about which configurator to use, this is already what the "legacy" import wizard has done for so many years. The less choice we give to user, the more useful is this tool.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3285:
-----------------------------------
I think there's a fundamental flaw in the easymport API : there's no configurator sort per priority. Each configurator should declare a weight/priority, so all of them could be sorted, then the first configurator (highest priority) that applies do its thing.
So then you can have :
Maven > PDE > generic project (.project) > projectless folder
If we had, say Gradle and Maven having the same priority, and both pom.xml and build.gradle are found, the UI should show the conflicting configurators and let the user decide how to import the project.
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3285:
------------------------------
Attachment: import-me.zip
Unzip import-me.zip and import project folder. 2 projects will be created import-me and classes
> Easy Import of non-eclipse projects
> -----------------------------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.0.Alpha2
>
> Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-19473.
------------------------------------
Resolution: Done
I updated the jbosstools-discovery_master job to update traditional nightly location for discovery catalog:
{code}
. ${WORKSPACE}/sources/publish/rsync.sh -s ${WORKSPACE}/sources/jbosstools/org.jboss.tools.central.discovery/target/discovery-site \
-t discovery/nightly/core/master
{code}
I'm still not sure whether it's a good idea or not... But at least, I could test the latest catalog, and verify that it's now loading again. The actual issue was indeed the typos in the plugin.xml
> Central can't load Discovery catalog
> ------------------------------------
>
> Key: JBIDE-19473
> URL: https://issues.jboss.org/browse/JBIDE-19473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found.
> The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content.
> Log says
> {quote}
> !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223
> !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar
> {quote}
> I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3367) Offline update from 8.0.x fails in installing FeedHenry
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3367?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3367:
-------------------------------------
It probably happened because of cordovasim features weren't included into p2 repository.
Another possibility is updating 4.2.x stream from p2 built out of 4.3.x where cordovasim namespace were changed to remove .vpe. part.
> Offline update from 8.0.x fails in installing FeedHenry
> -------------------------------------------------------
>
> Key: JBDS-3367
> URL: https://issues.jboss.org/browse/JBDS-3367
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 8.1.0.Beta1
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Updating from 8.0.0, 8.0.1 and 8.0.2 from the update zip causes the following error:
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85)
> Missing requirement: org.jboss.tools.feedhenry.ui 1.0.0.Beta1-v20150225-2159-B85 requires 'bundle org.jboss.tools.vpe.cordovasim.eclipse 3.6.2' but it could not be found
> Cannot satisfy dependency:
> From: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85)
> To: org.jboss.tools.feedhenry.ui [1.0.0.Beta1-v20150225-2159-B85]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19527) [FeedHenry] UnknownHostException should be handled in UI/wizard and displayed to user with an error message
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19527?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-19527.
----------------------------------
Resolution: Done
> [FeedHenry] UnknownHostException should be handled in UI/wizard and displayed to user with an error message
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19527
> URL: https://issues.jboss.org/browse/JBIDE-19527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.3.CR1
> Reporter: Pavol Srna
> Assignee: Gorkem Ercan
> Fix For: 4.3.0.Alpha2
>
>
> {code}
> org.jboss.tools.feedhenry.ui.model.FeedHenryException: Error occured while communicating with the FeedHenry server
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.doAPICall(FeedHenry.java:102)
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.listProjects(FeedHenry.java:44)
> at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector.prepareInput(FeedHenryApplicationSelector.java:220)
> at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector.access$0(FeedHenryApplicationSelector.java:208)
> at org.jboss.tools.feedhenry.ui.internal.FeedHenryApplicationSelector$1.run(FeedHenryApplicationSelector.java:109)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> Caused by: java.net.UnknownHostException: aerogear-t.sandbox.feedhenry.cz: nodename nor servname provided, or not known
> at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
> at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901)
> at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1293)
> at java.net.InetAddress.getAllByName0(InetAddress.java:1246)
> at java.net.InetAddress.getAllByName(InetAddress.java:1162)
> at java.net.InetAddress.getAllByName(InetAddress.java:1098)
> at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
> at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:259)
> at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:159)
> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
> at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
> at org.jboss.tools.feedhenry.ui.model.FeedHenry.doAPICall(FeedHenry.java:84)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19582) eclipse freezes after first start
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19582?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19582:
--------------------------------------
Assignee: Denis Golovin (was: Rob Stryker)
Assigning to [~dgolovin] for further investigation.
> eclipse freezes after first start
> ---------------------------------
>
> Key: JBIDE-19582
> URL: https://issues.jboss.org/browse/JBIDE-19582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.0.Alpha2
> Environment: Mac OS X Yosemite 10.10.1, Java 1.7
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
> {code}Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode):
> "Attach Listener" daemon prio=5 tid=0x00000001021be800 nid=0x108bf runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Provisioning Event Dispatcher" daemon prio=5 tid=0x00000008e07a4000 nid=0xe24b in Object.wait() [0x00000008e2400000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Worker-5" prio=5 tid=0x00000001020b0000 nid=0xc803 in Object.wait() [0x00000008e2676000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188)
> - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52)
> "Worker-3" prio=5 tid=0x0000000101b68000 nid=0xc613 in Object.wait() [0x00000008e166d000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188)
> - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52)
> "EventAdmin Async Event Dispatcher Thread" daemon prio=5 tid=0x000000010138c800 nid=0x8c2b in Object.wait() [0x00000008e0ed3000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:200)
> - locked <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4754)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> "Timer-0" daemon prio=5 tid=0x00000008e05d9000 nid=0x653b runnable [0x00000008e0dcf000]
> java.lang.Thread.State: RUNNABLE
> at java.util.regex.Pattern$BnM.optimize(Pattern.java:5334)
> at java.util.regex.Pattern.compile(Pattern.java:1678)
> at java.util.regex.Pattern.<init>(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:82)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:66)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.<init>(MonitoredHostProvider.java:59)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:214)
> at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:143)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:507)
> - locked <0x0000000112421e68> (a org.jboss.tools.common.jdt.debug.tools.internal.Tools)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:517)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> "[ThreadPool Manager] - Idle Thread" daemon prio=5 tid=0x00000001008f8000 nid=0x8b5f in Object.wait() [0x00000008e0b65000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106)
> - locked <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor)
> "Java indexing" daemon prio=5 tid=0x0000000100a09800 nid=0xb867 in Object.wait() [0x00000008dfd0f000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:382)
> - locked <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager)
> at java.lang.Thread.run(Thread.java:722)
> "Bundle File Closer" daemon prio=5 tid=0x00000008e01a6000 nid=0xb78b in Object.wait() [0x00000008df592000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "EMF Reference Cleaner" daemon prio=5 tid=0x00000001010d1800 nid=0x9503 in Object.wait() [0x00000008df3de000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at org.eclipse.emf.common.util.CommonUtil$1ReferenceClearingQueuePollingThread.run(CommonUtil.java:70)
> "Worker-JM" prio=5 tid=0x0000000100a66000 nid=0x932b in Object.wait() [0x00000008df99d000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939c88> (a java.util.ArrayList)
> at org.eclipse.core.internal.jobs.InternalWorker.run(InternalWorker.java:59)
> - locked <0x0000000112939c88> (a java.util.ArrayList)
> "[Timer] - Main Queue Handler" daemon prio=5 tid=0x0000000101271800 nid=0x9027 in Object.wait() [0x00000008df868000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939e18> (a java.lang.Object)
> at org.eclipse.equinox.internal.util.impl.tpt.timer.TimerImpl.run(TimerImpl.java:141)
> - locked <0x0000000112939e18> (a java.lang.Object)
> at java.lang.Thread.run(Thread.java:722)
> "Start Level: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x000000010115d000 nid=0x8f03 in Object.wait() [0x00000008df2db000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Framework Event Dispatcher: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x0000000100a96000 nid=0x8d0f in Object.wait() [0x00000008df1d8000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Active Thread: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" prio=5 tid=0x0000000100a2f800 nid=0x8e07 waiting on condition [0x00000008dedff000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0000000112523618> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> "Service Thread" daemon prio=5 tid=0x00000001010a5000 nid=0x5b03 runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread1" daemon prio=5 tid=0x00000001010a4000 nid=0x5a03 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread0" daemon prio=5 tid=0x000000010109f800 nid=0x5907 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Signal Dispatcher" daemon prio=5 tid=0x0000000100851000 nid=0x570f runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Finalizer" daemon prio=5 tid=0x0000000101092000 nid=0x5503 in Object.wait() [0x00000008db873000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:177)
> "Reference Handler" daemon prio=5 tid=0x000000010108b800 nid=0x5403 in Object.wait() [0x00000008db770000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000001125353b0> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:503)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
> - locked <0x00000001125353b0> (a java.lang.ref.Reference$Lock)
> "main" prio=5 tid=0x000000010200b800 nid=0x130f runnable [0x00007fff5fbfc000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.core.commands.common.HandleObject.hashCode(HandleObject.java:137)
> at org.eclipse.core.internal.commands.util.Util.hashCode(Util.java:266)
> at org.eclipse.core.commands.ParameterizedCommand.hashCode(ParameterizedCommand.java:615)
> at java.util.HashMap.hash(HashMap.java:351)
> at java.util.HashMap.getEntry(HashMap.java:443)
> at java.util.HashMap.get(HashMap.java:405)
> at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor(BindingManager.java:1161)
> at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor1(BindingManager.java:1210)
> at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1275)
> at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1265)
> at org.eclipse.jface.action.ExternalActionManager$CommandCallback.getAcceleratorText(ExternalActionManager.java:323)
> at org.eclipse.jface.action.ActionContributionItem.update(ActionContributionItem.java:907)
> at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859)
> at org.eclipse.jface.action.SubMenuManager.update(SubMenuManager.java:343)
> at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859)
> at org.eclipse.ui.internal.Workbench.updateActiveWorkbenchWindowMenuManager(Workbench.java:3373)
> at org.eclipse.ui.internal.Workbench.access$0(Workbench.java:3359)
> at org.eclipse.ui.internal.Workbench$1.bindingManagerChanged(Workbench.java:3354)
> at org.eclipse.jface.bindings.BindingManager.fireBindingManagerChanged(BindingManager.java:901)
> at org.eclipse.jface.bindings.BindingManager.setActiveBindings(BindingManager.java:2178)
> at org.eclipse.jface.bindings.BindingManager.recomputeBindings(BindingManager.java:1743)
> at org.eclipse.jface.bindings.BindingManager.contextManagerChanged(BindingManager.java:690)
> at org.eclipse.core.commands.contexts.ContextManager.fireContextManagerChanged(ContextManager.java:165)
> at org.eclipse.core.commands.contexts.ContextManager.setActiveContextIds(ContextManager.java:295)
> at org.eclipse.e4.ui.services.ContextServiceAddon$1.changed(ContextServiceAddon.java:47)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:333)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:347)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:191)
> at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener$3.widgetDisposed(ShellActivationListener.java:182)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1471)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1308)
> at org.eclipse.swt.widgets.Control.release(Control.java:2867)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
> at org.eclipse.jface.window.Window.close(Window.java:334)
> at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:990)
> at org.eclipse.jface.dialogs.MessageDialog.buttonPressed(MessageDialog.java:204)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:330)
> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:360)
> at org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:455)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.showDialog(RemoteJavaApplicationLaunchShortcut.java:186)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.access$2(RemoteJavaApplicationLaunchShortcut.java:183)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut$1$2.run(RemoteJavaApplicationLaunchShortcut.java:116)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> - locked <0x000000011293a5a8> (a org.eclipse.swt.widgets.RunnableLock)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> "VM Thread" prio=5 tid=0x000000010200c000 nid=0x5303 runnable
> "GC task thread#0 (ParallelGC)" prio=5 tid=0x0000000100832000 nid=0x4f03 runnable
> "GC task thread#1 (ParallelGC)" prio=5 tid=0x0000000101054800 nid=0x5003 runnable
> "GC task thread#2 (ParallelGC)" prio=5 tid=0x000000010104f800 nid=0x5103 runnable
> "GC task thread#3 (ParallelGC)" prio=5 tid=0x000000010105d800 nid=0x5203 runnable
> "VM Periodic Task Thread" prio=5 tid=0x0000000100851800 nid=0x5c03 waiting on condition
> JNI global references: 911{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19181) correct naming of internal packages so that they're consistent across all openshift plugins
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19181?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-19181:
----------------------------------------
Assignee: Andre Dietisheim
> correct naming of internal packages so that they're consistent across all openshift plugins
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-19181
> URL: https://issues.jboss.org/browse/JBIDE-19181
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.0.Alpha2
>
>
> Internal packages across the openshift plugins are non-consistent:
> ex.
> org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal
> org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal
> the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins.
> For reference, here's the official Eclipse documentation on the topic: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages
> {quote}
> org.eclipse.jdt.internal.core.compiler - Correct usage
> org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name.
> org.eclipse.core.internal.resources - Correct usage
> org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse.
> org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19582) eclipse freezes after first start
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19582?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19582:
---------------------------------------
Actual problem is
{code}
!ENTRY org.eclipse.ui.workbench 4 2 2015-04-13 16:56:46.818
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!STACK 0
java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:272)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:588)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:540)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:527)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:402)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at org.eclipse.ui.internal.progress.ProgressAnimationItem.finished(ProgressAnimationItem.java:431)
at org.eclipse.ui.internal.progress.FinishedJobs.add(FinishedJobs.java:201)
at org.eclipse.ui.internal.progress.FinishedJobs.access$3(FinishedJobs.java:177)
at org.eclipse.ui.internal.progress.FinishedJobs$1.removeJob(FinishedJobs.java:98)
at org.eclipse.ui.internal.progress.ProgressManager.removeJobInfo(ProgressManager.java:795)
at org.eclipse.ui.internal.progress.ProgressManager$2.done(ProgressManager.java:463)
at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:102)
at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
{code}
and it could be related to problem about eclipse not asking about workspace location and changes related to OS X launcher.
> eclipse freezes after first start
> ---------------------------------
>
> Key: JBIDE-19582
> URL: https://issues.jboss.org/browse/JBIDE-19582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.0.Alpha2
> Environment: Mac OS X Yosemite 10.10.1, Java 1.7
> Reporter: Denis Golovin
> Assignee: Rob Stryker
>
> {code}Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode):
> "Attach Listener" daemon prio=5 tid=0x00000001021be800 nid=0x108bf runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Provisioning Event Dispatcher" daemon prio=5 tid=0x00000008e07a4000 nid=0xe24b in Object.wait() [0x00000008e2400000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Worker-5" prio=5 tid=0x00000001020b0000 nid=0xc803 in Object.wait() [0x00000008e2676000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188)
> - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52)
> "Worker-3" prio=5 tid=0x0000000101b68000 nid=0xc613 in Object.wait() [0x00000008e166d000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188)
> - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52)
> "EventAdmin Async Event Dispatcher Thread" daemon prio=5 tid=0x000000010138c800 nid=0x8c2b in Object.wait() [0x00000008e0ed3000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:200)
> - locked <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4754)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> "Timer-0" daemon prio=5 tid=0x00000008e05d9000 nid=0x653b runnable [0x00000008e0dcf000]
> java.lang.Thread.State: RUNNABLE
> at java.util.regex.Pattern$BnM.optimize(Pattern.java:5334)
> at java.util.regex.Pattern.compile(Pattern.java:1678)
> at java.util.regex.Pattern.<init>(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:82)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:66)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.<init>(MonitoredHostProvider.java:59)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:214)
> at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:143)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:507)
> - locked <0x0000000112421e68> (a org.jboss.tools.common.jdt.debug.tools.internal.Tools)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:517)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> "[ThreadPool Manager] - Idle Thread" daemon prio=5 tid=0x00000001008f8000 nid=0x8b5f in Object.wait() [0x00000008e0b65000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106)
> - locked <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor)
> "Java indexing" daemon prio=5 tid=0x0000000100a09800 nid=0xb867 in Object.wait() [0x00000008dfd0f000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:382)
> - locked <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager)
> at java.lang.Thread.run(Thread.java:722)
> "Bundle File Closer" daemon prio=5 tid=0x00000008e01a6000 nid=0xb78b in Object.wait() [0x00000008df592000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "EMF Reference Cleaner" daemon prio=5 tid=0x00000001010d1800 nid=0x9503 in Object.wait() [0x00000008df3de000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at org.eclipse.emf.common.util.CommonUtil$1ReferenceClearingQueuePollingThread.run(CommonUtil.java:70)
> "Worker-JM" prio=5 tid=0x0000000100a66000 nid=0x932b in Object.wait() [0x00000008df99d000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939c88> (a java.util.ArrayList)
> at org.eclipse.core.internal.jobs.InternalWorker.run(InternalWorker.java:59)
> - locked <0x0000000112939c88> (a java.util.ArrayList)
> "[Timer] - Main Queue Handler" daemon prio=5 tid=0x0000000101271800 nid=0x9027 in Object.wait() [0x00000008df868000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939e18> (a java.lang.Object)
> at org.eclipse.equinox.internal.util.impl.tpt.timer.TimerImpl.run(TimerImpl.java:141)
> - locked <0x0000000112939e18> (a java.lang.Object)
> at java.lang.Thread.run(Thread.java:722)
> "Start Level: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x000000010115d000 nid=0x8f03 in Object.wait() [0x00000008df2db000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Framework Event Dispatcher: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x0000000100a96000 nid=0x8d0f in Object.wait() [0x00000008df1d8000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Active Thread: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" prio=5 tid=0x0000000100a2f800 nid=0x8e07 waiting on condition [0x00000008dedff000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0000000112523618> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> "Service Thread" daemon prio=5 tid=0x00000001010a5000 nid=0x5b03 runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread1" daemon prio=5 tid=0x00000001010a4000 nid=0x5a03 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread0" daemon prio=5 tid=0x000000010109f800 nid=0x5907 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Signal Dispatcher" daemon prio=5 tid=0x0000000100851000 nid=0x570f runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Finalizer" daemon prio=5 tid=0x0000000101092000 nid=0x5503 in Object.wait() [0x00000008db873000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:177)
> "Reference Handler" daemon prio=5 tid=0x000000010108b800 nid=0x5403 in Object.wait() [0x00000008db770000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000001125353b0> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:503)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
> - locked <0x00000001125353b0> (a java.lang.ref.Reference$Lock)
> "main" prio=5 tid=0x000000010200b800 nid=0x130f runnable [0x00007fff5fbfc000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.core.commands.common.HandleObject.hashCode(HandleObject.java:137)
> at org.eclipse.core.internal.commands.util.Util.hashCode(Util.java:266)
> at org.eclipse.core.commands.ParameterizedCommand.hashCode(ParameterizedCommand.java:615)
> at java.util.HashMap.hash(HashMap.java:351)
> at java.util.HashMap.getEntry(HashMap.java:443)
> at java.util.HashMap.get(HashMap.java:405)
> at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor(BindingManager.java:1161)
> at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor1(BindingManager.java:1210)
> at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1275)
> at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1265)
> at org.eclipse.jface.action.ExternalActionManager$CommandCallback.getAcceleratorText(ExternalActionManager.java:323)
> at org.eclipse.jface.action.ActionContributionItem.update(ActionContributionItem.java:907)
> at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859)
> at org.eclipse.jface.action.SubMenuManager.update(SubMenuManager.java:343)
> at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859)
> at org.eclipse.ui.internal.Workbench.updateActiveWorkbenchWindowMenuManager(Workbench.java:3373)
> at org.eclipse.ui.internal.Workbench.access$0(Workbench.java:3359)
> at org.eclipse.ui.internal.Workbench$1.bindingManagerChanged(Workbench.java:3354)
> at org.eclipse.jface.bindings.BindingManager.fireBindingManagerChanged(BindingManager.java:901)
> at org.eclipse.jface.bindings.BindingManager.setActiveBindings(BindingManager.java:2178)
> at org.eclipse.jface.bindings.BindingManager.recomputeBindings(BindingManager.java:1743)
> at org.eclipse.jface.bindings.BindingManager.contextManagerChanged(BindingManager.java:690)
> at org.eclipse.core.commands.contexts.ContextManager.fireContextManagerChanged(ContextManager.java:165)
> at org.eclipse.core.commands.contexts.ContextManager.setActiveContextIds(ContextManager.java:295)
> at org.eclipse.e4.ui.services.ContextServiceAddon$1.changed(ContextServiceAddon.java:47)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:333)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:347)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:191)
> at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener$3.widgetDisposed(ShellActivationListener.java:182)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1471)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1308)
> at org.eclipse.swt.widgets.Control.release(Control.java:2867)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
> at org.eclipse.jface.window.Window.close(Window.java:334)
> at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:990)
> at org.eclipse.jface.dialogs.MessageDialog.buttonPressed(MessageDialog.java:204)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:330)
> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:360)
> at org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:455)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.showDialog(RemoteJavaApplicationLaunchShortcut.java:186)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.access$2(RemoteJavaApplicationLaunchShortcut.java:183)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut$1$2.run(RemoteJavaApplicationLaunchShortcut.java:116)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> - locked <0x000000011293a5a8> (a org.eclipse.swt.widgets.RunnableLock)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> "VM Thread" prio=5 tid=0x000000010200c000 nid=0x5303 runnable
> "GC task thread#0 (ParallelGC)" prio=5 tid=0x0000000100832000 nid=0x4f03 runnable
> "GC task thread#1 (ParallelGC)" prio=5 tid=0x0000000101054800 nid=0x5003 runnable
> "GC task thread#2 (ParallelGC)" prio=5 tid=0x000000010104f800 nid=0x5103 runnable
> "GC task thread#3 (ParallelGC)" prio=5 tid=0x000000010105d800 nid=0x5203 runnable
> "VM Periodic Task Thread" prio=5 tid=0x0000000100851800 nid=0x5c03 waiting on condition
> JNI global references: 911{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19582) eclipse freezes after first start
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19582?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19582:
---------------------------------------
Sorry for the noise, could be my fault by clicking randomly in frozen eclipse window.
> eclipse freezes after first start
> ---------------------------------
>
> Key: JBIDE-19582
> URL: https://issues.jboss.org/browse/JBIDE-19582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.0.Alpha2
> Environment: Mac OS X Yosemite 10.10.1, Java 1.7
> Reporter: Denis Golovin
> Assignee: Rob Stryker
>
> {code}Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode):
> "Attach Listener" daemon prio=5 tid=0x00000001021be800 nid=0x108bf runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Provisioning Event Dispatcher" daemon prio=5 tid=0x00000008e07a4000 nid=0xe24b in Object.wait() [0x00000008e2400000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x0000000110c92a38> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Worker-5" prio=5 tid=0x00000001020b0000 nid=0xc803 in Object.wait() [0x00000008e2676000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188)
> - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52)
> "Worker-3" prio=5 tid=0x0000000101b68000 nid=0xc613 in Object.wait() [0x00000008e166d000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188)
> - locked <0x000000010e554da0> (a org.eclipse.core.internal.jobs.WorkerPool)
> at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:52)
> "EventAdmin Async Event Dispatcher Thread" daemon prio=5 tid=0x000000010138c800 nid=0x8c2b in Object.wait() [0x00000008e0ed3000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:200)
> - locked <0x0000000112bee7a0> (a org.eclipse.swt.widgets.RunnableLock)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4754)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> "Timer-0" daemon prio=5 tid=0x00000008e05d9000 nid=0x653b runnable [0x00000008e0dcf000]
> java.lang.Thread.State: RUNNABLE
> at java.util.regex.Pattern$BnM.optimize(Pattern.java:5334)
> at java.util.regex.Pattern.compile(Pattern.java:1678)
> at java.util.regex.Pattern.<init>(Pattern.java:1337)
> at java.util.regex.Pattern.compile(Pattern.java:1022)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:82)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalVmManager.<init>(LocalVmManager.java:66)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.<init>(MonitoredHostProvider.java:59)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
> at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:214)
> at sun.jvmstat.monitor.MonitoredHost.getMonitoredHost(MonitoredHost.java:143)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:507)
> - locked <0x0000000112421e68> (a org.jboss.tools.common.jdt.debug.tools.internal.Tools)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:517)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> "[ThreadPool Manager] - Idle Thread" daemon prio=5 tid=0x00000001008f8000 nid=0x8b5f in Object.wait() [0x00000008e0b65000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106)
> - locked <0x0000000112938f10> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor)
> "Java indexing" daemon prio=5 tid=0x0000000100a09800 nid=0xb867 in Object.wait() [0x00000008dfd0f000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:382)
> - locked <0x0000000112939150> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager)
> at java.lang.Thread.run(Thread.java:722)
> "Bundle File Closer" daemon prio=5 tid=0x00000008e01a6000 nid=0xb78b in Object.wait() [0x00000008df592000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x00000001129398c0> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "EMF Reference Cleaner" daemon prio=5 tid=0x00000001010d1800 nid=0x9503 in Object.wait() [0x00000008df3de000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x000000010e755948> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at org.eclipse.emf.common.util.CommonUtil$1ReferenceClearingQueuePollingThread.run(CommonUtil.java:70)
> "Worker-JM" prio=5 tid=0x0000000100a66000 nid=0x932b in Object.wait() [0x00000008df99d000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939c88> (a java.util.ArrayList)
> at org.eclipse.core.internal.jobs.InternalWorker.run(InternalWorker.java:59)
> - locked <0x0000000112939c88> (a java.util.ArrayList)
> "[Timer] - Main Queue Handler" daemon prio=5 tid=0x0000000101271800 nid=0x9027 in Object.wait() [0x00000008df868000]
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112939e18> (a java.lang.Object)
> at org.eclipse.equinox.internal.util.impl.tpt.timer.TimerImpl.run(TimerImpl.java:141)
> - locked <0x0000000112939e18> (a java.lang.Object)
> at java.lang.Thread.run(Thread.java:722)
> "Start Level: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x000000010115d000 nid=0x8f03 in Object.wait() [0x00000008df2db000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x000000010e4d2a48> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Framework Event Dispatcher: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" daemon prio=5 tid=0x0000000100a96000 nid=0x8d0f in Object.wait() [0x00000008df1d8000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400)
> - locked <0x0000000110745200> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336)
> "Active Thread: Equinox Container: 805a2397-38e2-0014-1c4c-eba624b5c9fa" prio=5 tid=0x0000000100a2f800 nid=0x8e07 waiting on condition [0x00000008dedff000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0000000112523618> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090)
> at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
> at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> "Service Thread" daemon prio=5 tid=0x00000001010a5000 nid=0x5b03 runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread1" daemon prio=5 tid=0x00000001010a4000 nid=0x5a03 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "C2 CompilerThread0" daemon prio=5 tid=0x000000010109f800 nid=0x5907 waiting on condition [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Signal Dispatcher" daemon prio=5 tid=0x0000000100851000 nid=0x570f runnable [0x0000000000000000]
> java.lang.Thread.State: RUNNABLE
> "Finalizer" daemon prio=5 tid=0x0000000101092000 nid=0x5503 in Object.wait() [0x00000008db873000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
> - locked <0x0000000112535638> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:177)
> "Reference Handler" daemon prio=5 tid=0x000000010108b800 nid=0x5403 in Object.wait() [0x00000008db770000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000001125353b0> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:503)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
> - locked <0x00000001125353b0> (a java.lang.ref.Reference$Lock)
> "main" prio=5 tid=0x000000010200b800 nid=0x130f runnable [0x00007fff5fbfc000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.core.commands.common.HandleObject.hashCode(HandleObject.java:137)
> at org.eclipse.core.internal.commands.util.Util.hashCode(Util.java:266)
> at org.eclipse.core.commands.ParameterizedCommand.hashCode(ParameterizedCommand.java:615)
> at java.util.HashMap.hash(HashMap.java:351)
> at java.util.HashMap.getEntry(HashMap.java:443)
> at java.util.HashMap.get(HashMap.java:405)
> at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor(BindingManager.java:1161)
> at org.eclipse.jface.bindings.BindingManager.getActiveBindingsFor1(BindingManager.java:1210)
> at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1275)
> at org.eclipse.jface.bindings.BindingManager.getBestActiveBindingFor(BindingManager.java:1265)
> at org.eclipse.jface.action.ExternalActionManager$CommandCallback.getAcceleratorText(ExternalActionManager.java:323)
> at org.eclipse.jface.action.ActionContributionItem.update(ActionContributionItem.java:907)
> at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859)
> at org.eclipse.jface.action.SubMenuManager.update(SubMenuManager.java:343)
> at org.eclipse.jface.action.SubContributionItem.update(SubContributionItem.java:138)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:859)
> at org.eclipse.ui.internal.Workbench.updateActiveWorkbenchWindowMenuManager(Workbench.java:3373)
> at org.eclipse.ui.internal.Workbench.access$0(Workbench.java:3359)
> at org.eclipse.ui.internal.Workbench$1.bindingManagerChanged(Workbench.java:3354)
> at org.eclipse.jface.bindings.BindingManager.fireBindingManagerChanged(BindingManager.java:901)
> at org.eclipse.jface.bindings.BindingManager.setActiveBindings(BindingManager.java:2178)
> at org.eclipse.jface.bindings.BindingManager.recomputeBindings(BindingManager.java:1743)
> at org.eclipse.jface.bindings.BindingManager.contextManagerChanged(BindingManager.java:690)
> at org.eclipse.core.commands.contexts.ContextManager.fireContextManagerChanged(ContextManager.java:165)
> at org.eclipse.core.commands.contexts.ContextManager.setActiveContextIds(ContextManager.java:295)
> at org.eclipse.e4.ui.services.ContextServiceAddon$1.changed(ContextServiceAddon.java:47)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:110)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:333)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:347)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:191)
> at org.eclipse.e4.ui.internal.workbench.swt.ShellActivationListener$3.widgetDisposed(ShellActivationListener.java:182)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1471)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1308)
> at org.eclipse.swt.widgets.Control.release(Control.java:2867)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
> at org.eclipse.jface.window.Window.close(Window.java:334)
> at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:990)
> at org.eclipse.jface.dialogs.MessageDialog.buttonPressed(MessageDialog.java:204)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:330)
> at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:360)
> at org.eclipse.jface.dialogs.MessageDialog.openQuestion(MessageDialog.java:455)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.showDialog(RemoteJavaApplicationLaunchShortcut.java:186)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut.access$2(RemoteJavaApplicationLaunchShortcut.java:183)
> at org.jboss.tools.common.jdt.debug.ui.launching.RemoteJavaApplicationLaunchShortcut$1$2.run(RemoteJavaApplicationLaunchShortcut.java:116)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> - locked <0x000000011293a5a8> (a org.eclipse.swt.widgets.RunnableLock)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3997)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3674)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> "VM Thread" prio=5 tid=0x000000010200c000 nid=0x5303 runnable
> "GC task thread#0 (ParallelGC)" prio=5 tid=0x0000000100832000 nid=0x4f03 runnable
> "GC task thread#1 (ParallelGC)" prio=5 tid=0x0000000101054800 nid=0x5003 runnable
> "GC task thread#2 (ParallelGC)" prio=5 tid=0x000000010104f800 nid=0x5103 runnable
> "GC task thread#3 (ParallelGC)" prio=5 tid=0x000000010105d800 nid=0x5203 runnable
> "VM Periodic Task Thread" prio=5 tid=0x0000000100851800 nid=0x5c03 waiting on condition
> JNI global references: 911{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15714:
----------------------------------------
{quote}
this "angularjs ....try again" will onyl be shown in context {{| content assist so it wont show up everywhere, correct ?
{quote}
Yes.
> Dynamic content assist for AngularJS expressions in html files
> --------------------------------------------------------------
>
> Key: JBIDE-15714
> URL: https://issues.jboss.org/browse/JBIDE-15714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: Diagram.gliffy, firstTime.png, vpe.png, vpe2.gif
>
>
> Dynamic content assist works with projects which are mature enough not to fail in runtime.
> Open any html page with JBoss HTML Editor (AngularJS templates are *not* supported) where some controllers are available and try Ctrl+Space on any {{}}.
> The very first time the message saying the data is loading will be shown (this message will be shown only once per editor):
> !firstTime.png!
> Press enter or Ctrl+Space again to see AngularJS proposals (if available):
> !vpe2.gif!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-19590:
-------------------------------------
Summary: Update module's README.md files with information about dependencies to other modules
Key: JBIDE-19590
URL: https://issues.jboss.org/browse/JBIDE-19590
Project: Tools (JBoss Tools)
Issue Type: Task
Reporter: Denis Golovin
For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
1. Set up target platform in preferences
2. Import JBT module sources into workspace
3. Import required JBT module sources into worksapce
(1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19478) Add template filtering by tag
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19478?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19478 at 4/14/15 12:27 PM:
--------------------------------------------------------------------
[~jcantrill] Can you please explain in what UI element this is? Is this in the application wizard?
Can you please also link the issue that's related (ex. new application wizard if applicable), thanks.
Is it related to JBIDE-19009?
was (Author: adietish):
[~jcantrill] Can you please explain in what UI element this is? Is this in the application wizard?
Can you please also link the issue that's related (ex. new application wizard if applicable), thanks.
> Add template filtering by tag
> -----------------------------
>
> Key: JBIDE-19478
> URL: https://issues.jboss.org/browse/JBIDE-19478
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19476) Add label validation
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19476:
------------------------------------------
postponing to 4.3.0.Beta1, nothing that we have to finish for Alpha2
> Add label validation
> --------------------
>
> Key: JBIDE-19476
> URL: https://issues.jboss.org/browse/JBIDE-19476
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19476) Add label validation
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19476 at 4/14/15 12:27 PM:
--------------------------------------------------------------------
[~jcantrill]: This is part of JBIDE-19009, isnt it?
was (Author: adietish):
[~jcantrill]: This is part of JBIDE-19010, isnt it?
> Add label validation
> --------------------
>
> Key: JBIDE-19476
> URL: https://issues.jboss.org/browse/JBIDE-19476
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19001) As a user I want to create an Eclipse project from an OpenShift build config
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19001?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19001:
-------------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> As a user I want to create an Eclipse project from an OpenShift build config
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19001
> URL: https://issues.jboss.org/browse/JBIDE-19001
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.2.Final
> Reporter: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> This is the case where a user has added resources vi the CLI or console and wants to create an Eclipse project in order to start developing.
> * The Eclipse project nature will be of the appropriate type as inferred from the source.
> * Main focus is to correctly import java/maven projects or “General” project otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19001) As a user I want to create an Eclipse project from an OpenShift build config
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19001?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19001:
------------------------------------------
postponing to 4.3.0.Beta1, nothing that we have to finish for Alpha2
> As a user I want to create an Eclipse project from an OpenShift build config
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19001
> URL: https://issues.jboss.org/browse/JBIDE-19001
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.2.Final
> Reporter: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> This is the case where a user has added resources vi the CLI or console and wants to create an Eclipse project in order to start developing.
> * The Eclipse project nature will be of the appropriate type as inferred from the source.
> * Main focus is to correctly import java/maven projects or “General” project otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
