[JBoss JIRA] Created: (JBIDE-9249) Error in Error log when creating JSF2 Kick Start project
by Vlado Pakan (JIRA)
Error in Error log when creating JSF2 Kick Start project
--------------------------------------------------------
Key: JBIDE-9249
URL: https://issues.jboss.org/browse/JBIDE-9249
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Environment: Linux 32bit, JDK Sun 1.6.0_25, JBoss AS 6 final, jbdevstudio-product-linux-gtk-5.0.0.v201106231745R-H7-M2
Reporter: Vlado Pakan
Assignee: Alexey Kazakov
Fix For: 3.3.0.M3
Create JSF2 Kick Start Project.
There is this error in Error Log:
!MESSAGE Error initializing facelet registry entry (/opt/jboss-6.0.0.Final/server/default/deployers/jsf.deployer/Mojarra-2.0/jsf-libs/jsf-impl-2.0.3-b05.jar!com/sun/faces/metadata/taglib/facelets_jsf_core.taglib.xml is invalid at line 453, column 52)
!STACK 0
org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'span' not found. (file:///opt/jbdevstudio5.0.0.M2/studio/com/sun/faces/metadata/taglib/facelets_jsf_core.taglib.xml, 453, 52)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLLoadImpl.java:83)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:191)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:242)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1511)
at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.TagModelLoader.loadFromInputStream(TagModelLoader.java:100)
at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.processJar(JarFileFaceletTaglibLocator.java:239)
at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.start(JarFileFaceletTaglibLocator.java:128)
at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.start(JarFileFaceletTaglibLocator.java:1)
at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor$1.run(ProjectTaglibDescriptor.java:82)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor.initialize(ProjectTaglibDescriptor.java:71)
at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor.getTagLibraries(ProjectTaglibDescriptor.java:117)
at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.initialize(FaceletTagRegistry.java:183)
at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.getAllTagLibraries(FaceletTagRegistry.java:129)
at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.getTagLibrary(FaceletTagRegistry.java:230)
at org.eclipse.jst.jsf.facelet.core.internal.metadata.FaceletNamespaceMetaDataLocator.locateMetaDataModelProviders(FaceletNamespaceMetaDataLocator.java:53)
at org.eclipse.jst.jsf.common.metadata.internal.DomainLoadingStrategy.locateMetaDataSourceInstances(DomainLoadingStrategy.java:143)
at org.eclipse.jst.jsf.common.metadata.internal.DomainLoadingStrategy.load(DomainLoadingStrategy.java:55)
at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModel.load(MetaDataModel.java:93)
at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModelManager.loadMetadata(MetaDataModelManager.java:147)
at org.eclipse.jst.jsf.common.metadata.internal.MetaDataModelManager.getModel(MetaDataModelManager.java:90)
at org.eclipse.jst.jsf.common.metadata.query.internal.MetaDataQueryHelper.getMDModel(MetaDataQueryHelper.java:124)
at org.eclipse.jst.jsf.common.metadata.query.internal.MetaDataQueryHelper.getModel(MetaDataQueryHelper.java:59)
at org.eclipse.jst.jsf.common.metadata.query.internal.MetaDataQueryHelper.getEntities(MetaDataQueryHelper.java:69)
at org.eclipse.jst.jsf.common.metadata.query.internal.MetaDataQueryHelper.getEntity(MetaDataQueryHelper.java:64)
at org.eclipse.jst.jsf.metadataprocessors.MetaDataEnabledProcessingFactory.getAttributeValueRuntimeTypeFeatureProcessors(MetaDataEnabledProcessingFactory.java:100)
at org.eclipse.jst.jsf.metadataprocessors.MetaDataEnabledProcessingFactory.getAttributeValueRuntimeTypeFeatureProcessors(MetaDataEnabledProcessingFactory.java:146)
at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validateNonELAttributeValue(AttributeValidatingStrategy.java:660)
at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.access$1(AttributeValidatingStrategy.java:637)
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:166)
at org.eclipse.jst.jsf.validation.internal.strategy.AttributeValidatingStrategy.validate(AttributeValidatingStrategy.java:142)
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.HTMLValidator.validateFile(HTMLValidator.java:158)
at org.eclipse.jst.jsf.facelet.ui.internal.validation.HTMLValidator.validate(HTMLValidator.java:108)
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:106)
at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:65)
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.iterate(ElementTreeIterator.java:127)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:75)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:104)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:88)
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)
Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'span' not found. (file:///opt/jbdevstudio5.0.0.M2/studio/com/sun/faces/metadata/taglib/facelets_jsf_core.taglib.xml, 453, 52)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLHandler.java:1777)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:1023)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:1001)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:712)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1363)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2755)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:181)
... 57 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-1919) Uninstaller leaves behind empty jbdevstudio folder
by Nick Boldt (Created) (JIRA)
Uninstaller leaves behind empty jbdevstudio folder
--------------------------------------------------
Key: JBDS-1919
URL: https://issues.jboss.org/browse/JBDS-1919
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 4.1.1.GA, 5.0.0.M4
Environment: Seen on Win7_64 w/ JDK 6u25 32-bit. May occur on other platforms too.
Reporter: Nick Boldt
Fix For: 5.0.0.Beta1
See JBDS-1918 for steps to repro. This might be an izpack bug or an installer/uninstaller config bug, but either way the install folder - though empty - persists after installation.
If you double-click the uninstaller.jar, you'll end up with ~/jbdevstudio/ and ~/jbdevstudio/Uninstaller (both empty folders).
If you run the uninstaller from the icon (having tweaked it as follows first), you'll get just the ~/jbdevstudio folder.
{code}
Target: "C:\Users\nboldt\jbdevstudio/Uninstaller\uninstaller.jar"
Start in: (leave blank)
{code}
--
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
12 years, 5 months
[JBoss JIRA] Created: (JBDS-1627) 3rd party certification for JBDS 5.x
by Nick Boldt (JIRA)
3rd party certification for JBDS 5.x
------------------------------------
Key: JBDS-1627
URL: https://issues.jboss.org/browse/JBDS-1627
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
Reporter: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.x
We should define what kind of certifications we want and then certify 3rd party plugins with JBDS
Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees.
For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-10945) BrowserSim: create more skins
by Yahor Radtsevich (JIRA)
Yahor Radtsevich created JBIDE-10945:
----------------------------------------
Summary: BrowserSim: create more skins
Key: JBIDE-10945
URL: https://issues.jboss.org/browse/JBIDE-10945
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Yahor Radtsevich
New skins or a universal skin should be created.
Now there is only one iPhone 3 skin which is used to render all devices, including iPad, Android and BlackBerry. But there are differences between these devices, which should be reflected skins. For example, iPad has back/forward buttons on the address bar and the address bar is never hidden. Android, in its turn, has back/forward buttons either as hardware buttons (not on screen), or they are hidden automatically. For developers this means, that available browser size differs from iPhone 3.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-11081) Small changes for warning message when enabling openshift application for existing project
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-11081:
---------------------------------------
Summary: Small changes for warning message when enabling openshift application for existing project
Key: JBIDE-11081
URL: https://issues.jboss.org/browse/JBIDE-11081
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Lucia Jelinkova
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 3.3.0.CR1
Existing message that appears during enabling OpenShift application for the existing project is informative, however, could you consider these suggestions?
- distinguish more explicitly what will be done on the "remote" and "local" side
- put "This cannot be undone" warning just before "Do you wish to continue?" question
- write more explicitly that Git will not only be enabled, but also connected to OpenShift server's Git
- the lines are not aligned
The message could then look something like this:
OpenShift application XXX will be enabled on project YYY by copying OpenShift configuration from server to local project and connecting local project to OpenShift Git repository.
The local project will be automatically committed to local Git repository and further publishing will eventually override existing remote content.
This cannot be undone. Do you wish to continue?
--
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
12 years, 5 months