January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10272) Automatically Start Forge When Eclipse Starts

by Koen Aers (Created) (JIRA)

Automatically Start Forge When Eclipse Starts --------------------------------------------- Key: JBIDE-10272 URL: https://issues.jboss.org/browse/JBIDE-10272 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 This feature needs to be controlled by a preference setting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] (JBIDE-10589) Cannot add JSF facet to a Web project

by Rafal Krzewski (Created) (JIRA)

Cannot add JSF facet to a Web project ------------------------------------- Key: JBIDE-10589 URL: https://issues.jboss.org/browse/JBIDE-10589 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, maven Affects Versions: 3.3.0.M5 Environment: Eclipse 3.7.1.20110916-0149, m2e 1.0.100.20110804-1717, m2e-wtp 0.14.0.20110928-2045, org.jboss.tools.jsf_3.3.0.v20111213-1958-H41-M5 Reporter: Rafal Krzewski Assignee: Alexey Kazakov Whenever I try to add a JSF project facet to my web project, operation fails. When I use Project facets configuration page, applying the JSF facet addition fails with the following message: Failed while installing JavaServer Faces 1.2: java.lang.NullPointerException. I can see the following pair of excpetions written to the log: No IModelProvider exists for project P/jsf_test of version: Dynamic Web Module 2.5 java.lang.NullPointerException: No IModelProvider exists for project P/jsf_test of version: Dynamic Web Module 2.5 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.internal.project.facet.JSFFacetInstallDelegate.execute(JSFFacetInstallDelegate.java:86) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) 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$5.run(FacetedProject.java:1099) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:232) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$5.run(FacetsPropertyPage.java:246) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Failed while installing JavaServer Faces 1.2. java.lang.NullPointerException at org.eclipse.jst.jsf.core.internal.project.facet.JSFUtils.getModelProvider(JSFUtils.java:148) at org.eclipse.jst.jsf.core.internal.project.facet.JSFFacetInstallDelegate.execute(JSFFacetInstallDelegate.java:97) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) 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$5.run(FacetedProject.java:1099) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:232) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$5.run(FacetsPropertyPage.java:246) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) When I attempt to update configuration of a Maven-enabled webapp project, I see the following exceptoions: Failed while installing JavaServer Faces 1.2. java.lang.NullPointerException at org.eclipse.jst.jsf.core.internal.project.facet.JSFUtils.getModelProvider(JSFUtils.java:148) at org.eclipse.jst.jsf.core.internal.project.facet.JSFFacetInstallDelegate.execute(JSFFacetInstallDelegate.java:97) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) 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:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255) at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.installJSFFacet(JSFProjectConfigurator.java:213) at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.installWarFacets(JSFProjectConfigurator.java:170) at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.configureInternal(JSFProjectConfigurator.java:122) at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.configure(JSFProjectConfigurator.java:98) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:277) at org.eclipse.m2e.core.ui.internal.UpdateConfigurationJob.runInWorkspace(UpdateConfigurationJob.java:87) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) followed by: Unable to update Maven configuration An exception stack trace is not available. I've tried also with JSF 2.0, with same results (JSF 2.0 facet is missing Maven provided library - I'm not sure if this expected or a separate problem) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

8
10
0 / 0

[JBoss JIRA] (JBIDE-10760) Delete deprecated code in jbpm/builders ?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10760: ---------------------------------- Summary: Delete deprecated code in jbpm/builders ? Key: JBIDE-10760 URL: https://issues.jboss.org/browse/JBIDE-10760 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Koen Aers Fix For: 3.3.0.Beta1 Was looking to remove deprecated code and discovered you have a reference to org.eclipse.pde.build in your code: {code} ** ./jbpm/builders/org.jboss.tools.flow.jpdl4.builder/build.xml ** 58- 59-  60: <BundleFileLocator eclipseInstallationRoot="${eclipseDir}" bundleId="org.eclipse.pde.build" filePath="scripts/build.xml" property="regularbuildfile" /> 61- <dirname file="${regularbuildfile}" property="scriptdir"/> 62- <property name="productbuildfile" value="${scriptdir}/productBuild/productBuild.xml"/> {code} I assume the whole ~/tunk/jbpm/builders/ folder is obsolete and can be removed. Is that correct? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (JBDS-1984) Required disk space amount is wrong in universal installer

by Radim Hopp (Created) (JIRA)

Required disk space amount is wrong in universal installer ---------------------------------------------------------- Key: JBDS-1984 URL: https://issues.jboss.org/browse/JBDS-1984 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.M5 Environment: Win7 32b, Linux (Fedora 15) 64b, Java 1.6, universal installer 5.0.0.M5-H63 Reporter: Radim Hopp Priority: Minor Fix For: 5.0.0.Beta1 On Summary Information page is said that only 14.03MB of disk space is required (which is clearly not enough). Tried it on win7 32b and linux 64b (Fedora 15). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
4
0 / 0

[JBoss JIRA] (JBIDE-10099) Exception thrown when creating mavenized seam2 project

by Rastislav Wagner (Created) (JIRA)

Exception thrown when creating mavenized seam2 project ------------------------------------------------------ Key: JBIDE-10099 URL: https://issues.jboss.org/browse/JBIDE-10099 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, Seam 2 Affects Versions: 3.3.0.M4 Reporter: Rastislav Wagner Assignee: Fred Bricon Exception: java.lang.NullPointerException at org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) at org.maven.ide.eclipse.wtp.WebFragmentProjectConfigurator.configure(WebFragmentProjectConfigurator.java:59) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:277) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:262) at org.jboss.tools.maven.core.MavenCoreActivator.updateMavenProjectConfiguration(MavenCoreActivator.java:331) at org.jboss.tools.maven.core.MavenCoreActivator.addMavenCapabilities(MavenCoreActivator.java:236) at org.jboss.tools.maven.core.MavenCoreActivator.createMavenProject(MavenCoreActivator.java:217) at org.jboss.tools.maven.core.MavenCoreActivator.createMavenProject(MavenCoreActivator.java:148) at org.jboss.tools.maven.seam.MavenSeamActivator.configureTestProject(MavenSeamActivator.java:325) at org.jboss.tools.maven.seam.MavenSeamActivator.configureSeamProject(MavenSeamActivator.java:164) at org.jboss.tools.maven.seam.internal.project.facet.MavenPostInstallListener.handleEvent(MavenPostInstallListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454) 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$5.run(FacetedProject.java:1099) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:400) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:282) at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:348) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

7
8
0 / 0

[JBoss JIRA] (JBDS-1946) Investigate use of jRebel in JBT/JBDS

by Nick Boldt (Created) (JIRA)

Investigate use of jRebel in JBT/JBDS ------------------------------------- Key: JBDS-1946 URL: https://issues.jboss.org/browse/JBDS-1946 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite Affects Versions: 5.0.0.M5 Reporter: Nick Boldt Assignee: Len DiMaggio Fix For: 5.0.0.Beta1 Download: http://zeroturnaround.com/jrebel/current/ License: http://zeroturnaround.com/jrebel/end-user-license-agreement/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
11
0 / 0

[JBoss JIRA] (JBIDE-10743) Knowledge Base and CDI Builder not compatible with Scala project

by Hendy Irawan (JIRA)

Hendy Irawan created JBIDE-10743: ------------------------------------ Summary: Knowledge Base and CDI Builder not compatible with Scala project Key: JBIDE-10743 URL: https://issues.jboss.org/browse/JBIDE-10743 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M5 Reporter: Hendy Irawan Assignee: Alexey Kazakov Create a Scala web project using Scala IDE. A Scala project removes the Java builder because it also compiles the Java sources. However, a project without Java builder is not supported by JBoss Tools: {code} ./.bak_1.log:!MESSAGE Can't enable org.jboss.tools.jst.web.kb.kbbuilder support on the project satukancinta-data without Java builder. ./.bak_1.log:!MESSAGE Can't enable org.jboss.tools.cdi.core.cdibuilder support on the project satukancinta-data without Java builder. {code} Alternative builders should be supported by JBoss Tools, as long as it is compatible with Java builder. Similar issue might also apply to Groovy projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
12
0 / 0

[JBoss JIRA] Created: (JBIDE-9581) Create vanilla Seam getting started project

by Nick Boldt (JIRA)

Create vanilla Seam getting started project ------------------------------------------- Key: JBIDE-9581 URL: https://issues.jboss.org/browse/JBIDE-9581 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Rob Stryker Fix For: 3.3.0.M4 (From JBDS-1814 - see https://issues.jboss.org/browse/JBDS-1814?focusedCommentId=12623742&page=...) Concerning the Getting Started Guide content: * for Tools 3.3/JBDS 5, we will want to have a vanilla EE6 getting started project as well as the Seam one. Those project templates are spelled out in the JBDS 5.0 planning docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
9
0 / 0

[JBoss JIRA] (JBIDE-10339) after installing JBT Abridged cateogy (including m2e connectors) lots of console errors logged

by Nick Boldt (Created) (JIRA)

after installing JBT Abridged cateogy (including m2e connectors) lots of console errors logged ---------------------------------------------------------------------------------------------- Key: JBIDE-10339 URL: https://issues.jboss.org/browse/JBIDE-10339 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: maven, updatesite, UpStream Affects Versions: 3.3.0.M5 Reporter: Nick Boldt Assignee: Fred Bricon Fix For: 3.3.0.Beta1 See parent jira JBIDE-10336 for steps to reproduce. Full log is here: https://issues.jboss.org/secure/attachment/12349551/eclipse.log.Sun_Dec4_... This could be an upstream issue, but I wanted to make sure you were aware of it in case it was because of something we're doing w/ m2e on first startup of JBT after install. Or perhaps because of a missing dependency? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
9
0 / 0

[JBoss JIRA] (JBIDE-9875) Ideas about publish ui for openshift servers

by Max Rydahl Andersen (Created) (JIRA)

Ideas about publish ui for openshift servers -------------------------------------------- Key: JBIDE-9875 URL: https://issues.jboss.org/browse/JBIDE-9875 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers, openshift Reporter: Max Rydahl Andersen Assignee: Rob Stryker Attachments: openshift_publishoptions.bmml Mock (see attached) for how to present the various commit/push options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2012