February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10212) JBoss Perspective: File-New Options

by Burr Sutter (Created) (JIRA)

JBoss Perspective: File-New Options ----------------------------------- Key: JBIDE-10212 URL: https://issues.jboss.org/browse/JBIDE-10212 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Attachments: Screen Shot 2011-11-22 at 10.47.56 AM.png File-New options should match the Create Projects section of JBoss Central. Java EE 6 WAR Java EE 6 EAR HTML5 Project RichFaces Project SpringMVC Dynamic Web Project The ordering should match JBoss Central as well. Note: let's discuss these final labels in the comments section. -- 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

12
32
0 / 0

[JBoss JIRA] (JBIDE-10987) Installing the JBoss Maven Facet fails on EAR projects

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-10987: ----------------------------------- Summary: Installing the JBoss Maven Facet fails on EAR projects Key: JBIDE-10987 URL: https://issues.jboss.org/browse/JBIDE-10987 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.Beta1 Reporter: Fred Bricon Assignee: Fred Bricon Priority: Blocker Fix For: 3.3.0.Beta1 A regression crept in when fixing JBIDE-10762, since the Java nature is no longer installed on EAR projects : {noformat} org.eclipse.wst.common.project.facet.core.FacetedProjectFrameworkException: Failed while installing JBoss Maven Integration 1.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: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.seam.configurators.SeamProjectConfigurator.installM2Facet(SeamProjectConfigurator.java:271) at org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator.configureInternal(SeamProjectConfigurator.java:176) at org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator.configure(SeamProjectConfigurator.java:129) 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.configureNewMavenProject(ProjectConfigurationManager.java:234) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:150) at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase$4.run(AbstractMavenProjectTestCase.java:315) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:313) at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:289) at org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest.testJBIDE10790_earConfiguration(SeamConfiguratorTest.java:62) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:72) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44) at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(WorkbenchTestable.java:71) at java.lang.Thread.run(Thread.java:662) Caused by: Java Model Exception: Java Model Status [multi-ear does not exist] at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:495) at org.eclipse.jdt.internal.core.JavaModelManager.getPerProjectInfoCheckExistence(JavaModelManager.java:2283) at org.eclipse.jdt.internal.core.JavaProject.getPerProjectInfo(JavaProject.java:1905) at org.eclipse.jdt.internal.core.JavaProject.getRawClasspath(JavaProject.java:1927) at org.jboss.tools.maven.core.ProjectUtil.removeWTPContainers(ProjectUtil.java:149) at org.jboss.tools.maven.core.internal.project.facet.MavenFacetInstallDelegate.execute(MavenFacetInstallDelegate.java:150) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) {noformat} -- 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
4
0 / 0

[JBoss JIRA] (JBIDE-10785) Failed while installing JavaServer Faces 1.2.

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-10785: -------------------------------------- Summary: Failed while installing JavaServer Faces 1.2. Key: JBIDE-10785 URL: https://issues.jboss.org/browse/JBIDE-10785 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Fred Bricon 1. Check out http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/examples to a local folder. 2. Import it as an existing maven project. 3. It's imported OK. 4. Remove this project from the workspace. 5. Check out http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/examples to the same local folder. 6. Import it as an existing maven project (the same folder, the same project name). 7. There is an exception: {code} java.lang.RuntimeException: org.osgi.service.prefs.BackingStoreException: Resource '/booking/booking-web/.settings' does not exist. at org.eclipse.jst.common.project.facet.core.libprov.internal.LibraryProviderFrameworkImpl.setCurrentProvider(LibraryProviderFrameworkImpl.java:224) at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate.execute(LibraryInstallDelegate.java:597) at org.eclipse.jst.jsf.core.internal.project.facet.JSFFacetInstallDelegate.execute(JSFFacetInstallDelegate.java:116) 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:203) at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.installWarFacets(JSFProjectConfigurator.java:160) at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.configureInternal(JSFProjectConfigurator.java:112) at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.configure(JSFProjectConfigurator.java:88) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:303) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:242) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:152) at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:164) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:249) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.osgi.service.prefs.BackingStoreException: Resource '/booking/booking-web/.settings' does not exist. at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferencesGroup.save(ProjectFacetPreferencesGroup.java:174) at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferences.flush(ProjectFacetPreferences.java:412) at org.eclipse.jst.common.project.facet.core.libprov.internal.LibraryProviderFrameworkImpl.setCurrentProvider(LibraryProviderFrameworkImpl.java:220) ... 23 more Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/booking/booking-web/.settings' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:320) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:194) at org.eclipse.core.internal.resources.File.create(File.java:114) at org.eclipse.core.internal.resources.File.create(File.java:187) at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:358) at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:321) at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:307) at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferencesGroup.save(ProjectFacetPreferencesGroup.java:165) ... 25 more {code} 8. Remove the project again. 9. Restart Eclipse. 10. Now I can import the project without problems. -- 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

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9636) Wrong Load Strategy in web.xml in JBoss Seam/Portlet Project

by Joao Viragine (JIRA)

Wrong Load Strategy in web.xml in JBoss Seam/Portlet Project ------------------------------------------------------------ Key: JBIDE-9636 URL: https://issues.jboss.org/browse/JBIDE-9636 Project: Tools (JBoss Tools) Issue Type: Bug Environment: JBDS 4.1 Reporter: Joao Viragine When we create a Seam Web Project with JBoss Seam Portlet Facet, JBDS generates a wrong JBoss Seam/Portlet Project as follow: JBDS generates a Load Strategy as NONE and it should be DEFAULT. <context-param> <param-name>org.richfaces.LoadStyleStrategy</param-name> <param-value>NONE</param-value> </context-param> <context-param> <param-name>org.richfaces.LoadScriptStrategy</param-name> <param-value>NONE</param-value> </context-param> When we use a Load Strategy as NONE, the Portlet doesn't properly load the css and js. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9767) Change LoadStyleStrategy and LoadScriptStrategy in RichFaces portlet project

by Miroslav Cupak (JIRA)

Change LoadStyleStrategy and LoadScriptStrategy in RichFaces portlet project ---------------------------------------------------------------------------- Key: JBIDE-9767 URL: https://issues.jboss.org/browse/JBIDE-9767 Project: Tools (JBoss Tools) Issue Type: Enhancement Affects Versions: 3.2.1.Final Environment: JBDS 4.1.0.GA, EPP 5.2.0.ER01, Sun JDK 1.6.0_27 Reporter: Miroslav Cupak When I generate a JSF portlet project (_Dynamic Web Module_, _Java_, _JavaServer Faces_, _JBoss Core Portlet_ and _JBoss JSF Portlet_ facets) with RichFaces libraries in JBDS to deploy on EPP, its _web.xml_ contains the following lines: {code:xml} <context-param> <param-name>org.richfaces.LoadStyleStrategy</param-name> <param-value>NONE</param-value> </context-param> <context-param> <param-name>org.richfaces.LoadScriptStrategy</param-name> <param-value>NONE</param-value> </context-param> {code} This was OK with Portlet Bridge 1.0 (see _JBoss Portlet Bridge 1.0 Reference Guide_, section _RichFaces Setup and Configuration Options_), but doesn't make much sense with Portlet Bridge 2.x (again, see _JBoss Portlet Bridge 2.x Reference Guide_, section _RichFaces Setup and Configuration Options_). I think it would be better and more convenient to set the generated value for both _LoadStyleStrategy_ and _LoadScriptStrategy_ to _DEFAULT_ (or _ALL_) so that RichFaces components can be used in portlets without needing to include the relevant scripts manually. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
6
0 / 0

[JBoss JIRA] (JBIDE-9899) downloads should be clear where it is from (url) and if community show disclaimer

by Max Rydahl Andersen (Created) (JIRA)

downloads should be clear where it is from (url) and if community show disclaimer --------------------------------------------------------------------------------- Key: JBIDE-9899 URL: https://issues.jboss.org/browse/JBIDE-9899 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Environment: Reporter: Max Rydahl Andersen -- 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
6
0 / 0

[JBoss JIRA] (JBIDE-10877) wrong credentials are not exposed in console view

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10877: ------------------------------------------- Summary: wrong credentials are not exposed in console view Key: JBIDE-10877 URL: https://issues.jboss.org/browse/JBIDE-10877 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.Beta1 adding a user with incorrect credentials just shows empty tree. should have some kind of indication the credentials are ok. I would expect the "add connection" not to actually allow me to add. -- 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
3
0 / 0

[JBoss JIRA] (JBIDE-10993) Error when connecting into the OpenShift Express Console for the first time

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-10993: ------------------------------------- Summary: Error when connecting into the OpenShift Express Console for the first time Key: JBIDE-10993 URL: https://issues.jboss.org/browse/JBIDE-10993 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Xavier Coulon Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.Beta1 Attachments: Screen Shot 2012-02-22 at 11.46.59 AM.png -- 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
5
0 / 0

[JBoss JIRA] (JBIDE-11034) "Delete" action disappeared from User's contextual menu in OpenSHift Express Console view

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-11034: ------------------------------------- Summary: "Delete" action disappeared from User's contextual menu in OpenSHift Express Console view Key: JBIDE-11034 URL: https://issues.jboss.org/browse/JBIDE-11034 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Critical Fix For: 3.3.0.Beta1 Attachments: JBIDE-11034.patch Menu "Delete" is not visible anymore -- 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
6
0 / 0

[JBoss JIRA] (JBIDE-10285) Run As > On Server support for jax-rs GET end points

by Max Rydahl Andersen (Created) (JIRA)

Run As > On Server support for jax-rs GET end points ---------------------------------------------------- Key: JBIDE-10285 URL: https://issues.jboss.org/browse/JBIDE-10285 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Environment: Reporter: Max Rydahl Andersen Assignee: Xavier Coulon Priority: Optional Fix For: 3.3.0.Beta1 Here is a patch to start implement supprot for Run On Server for "GET /members" and similar under JAX-RS node point. note: I believe this feature request is already in here but coulnd't find it ;( -- 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

4
4
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 February 2012