January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18724) HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>)

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18724?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-18724: ------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/433 (was: https://github.com/jbosstools/jbosstools-jst/pull/404) > HTML Validation: Ability to ignore custom htm tags (e.g. <ion-*>) > ----------------------------------------------------------------- > > Key: JBIDE-18724 > URL: https://issues.jboss.org/browse/JBIDE-18724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Labels: new_and_noteworthy > Fix For: 4.2.3.Final > > > WTP HTML validator marks any custom html tags as unknown. It's possible to disable this validation at all: Window->Preferences->Web->HTML Files->Validation ==> Set Elements -> Unknown tag name severity to "Ignore": > !00001262.png! > But it would be useful to have ability to make HTML validator ignore some particular tags only. > I suggest to contribute a patch to WTP to fix it. > We have already did it for attributes, so lets do it for tags too: > - New preferences with a list of ignored tags (a mask can be used) > - A new preference page to set these preferences > - QuickFix for validation problem which will add the tag name/mask to this list/preferences > - Extension in our angular/ionic plugin which will disable validation for <ion-*> tags. > I've filed it to bugzilla - https://bugs.eclipse.org/bugs/show_bug.cgi?id=444545 but we have to provide a patch for it if we want to have it done ;) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi... ] Rafael Benevides commented on JBIDE-19030: ------------------------------------------ That could be one cause. I'll update the stacks. Hang on > Creation of new RichFaces project results in outdated archetype > --------------------------------------------------------------- > > Key: JBIDE-19030 > URL: https://issues.jboss.org/browse/JBIDE-19030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: project-examples > Affects Versions: 4.2.1.Final > Reporter: Matej Novotny > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > In JBDS one can create RichFaces project via: > * File -> New -> Other -> RichFaces Project > This results in choosing kitchensink archetype for version 4.2.3 which is outdated. > There were some major changes to RichFaces beggining with version 4.5 so it would be nice if JBDS could make use of any 4.5.x.Final version artifact instead. > Note: Latest archetype version is 4.5.1.Final and 4.5.2.Final is being staged at the moment, so one of these two should be used I guess. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19032) CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19032?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19032: -------------------------------- Description: see the following [comment|https://issues.jboss.org/browse/JBIDE-18900?focusedCommentId=1303...] (was: see the following [comment|https://issues.jboss.org/browse/https://issues.jboss.org/browse/J...]) > CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-19032 > URL: https://issues.jboss.org/browse/JBIDE-19032 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > see the following [comment|https://issues.jboss.org/browse/JBIDE-18900?focusedCommentId=1303...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19032) CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19032?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19032: -------------------------------- Description: see the following [comment|https://issues.jboss.org/browse/https://issues.jboss.org/browse/J...] (was: see the following [comment|https://issues.jboss.org/browse/JBIDE-18900?focusedCommentId=1303...]) > CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-19032 > URL: https://issues.jboss.org/browse/JBIDE-19032 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > see the following [comment|https://issues.jboss.org/browse/https://issues.jboss.org/browse/J...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19032) CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19032?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19032: -------------------------------- Description: see the following [comment|https://issues.jboss.org/browse/JBIDE-18900?focusedCommentId=1303...] > CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-19032 > URL: https://issues.jboss.org/browse/JBIDE-19032 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cordovasim > Affects Versions: 4.2.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > see the following [comment|https://issues.jboss.org/browse/JBIDE-18900?focusedCommentId=1303...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19032) CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-19032: ----------------------------------- Summary: CordovaSim: Need to substitute 'Start Page' with the 'Start Page Parameters' in the launch config Key: JBIDE-19032 URL: https://issues.jboss.org/browse/JBIDE-19032 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cordovasim Affects Versions: 4.2.1.Final Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.3.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19030: ------------------------------------- And BTW, Wildfly doesn't reference any richfaces archetype so the first one (community) version found is used. > Creation of new RichFaces project results in outdated archetype > --------------------------------------------------------------- > > Key: JBIDE-19030 > URL: https://issues.jboss.org/browse/JBIDE-19030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: project-examples > Affects Versions: 4.2.1.Final > Reporter: Matej Novotny > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > In JBDS one can create RichFaces project via: > * File -> New -> Other -> RichFaces Project > This results in choosing kitchensink archetype for version 4.2.3 which is outdated. > There were some major changes to RichFaces beggining with version 4.5 so it would be nice if JBDS could make use of any 4.5.x.Final version artifact instead. > Note: Latest archetype version is 4.5.1.Final and 4.5.2.Final is being staged at the moment, so one of these two should be used I guess. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3309) Add Sapphire to JBDS target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3309?page=com.atlassian.jira.plugin.... ] Mickael Istria closed JBDS-3309. -------------------------------- Resolution: Done > Add Sapphire to JBDS target-platform > ------------------------------------ > > Key: JBDS-3309 > URL: https://issues.jboss.org/browse/JBDS-3309 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 9.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 9.0.0.Alpha1 > > > Batch component depends on Sapphire. So in order to get batch included by default in JBDS, we must have Sapphire available in JBDS TP. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19030: ------------------------------------- Rafael, IIRC, JBDS doesn't use the Runtime->Archetype association directly because stacks uses different archetype ids for the same type of archetype (jboss-javaee6-webapp-archetype, jboss-javaee6-webapp-archetype-eap...), but JBT/JBDS can only reference one thing (hence we rely on labels instead to filter archetypes per runtimes). But I reckon there's probably room for improvement on our side. > Creation of new RichFaces project results in outdated archetype > --------------------------------------------------------------- > > Key: JBIDE-19030 > URL: https://issues.jboss.org/browse/JBIDE-19030 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: project-examples > Affects Versions: 4.2.1.Final > Reporter: Matej Novotny > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > In JBDS one can create RichFaces project via: > * File -> New -> Other -> RichFaces Project > This results in choosing kitchensink archetype for version 4.2.3 which is outdated. > There were some major changes to RichFaces beggining with version 4.5 so it would be nice if JBDS could make use of any 4.5.x.Final version artifact instead. > Note: Latest archetype version is 4.5.1.Final and 4.5.2.Final is being staged at the moment, so one of these two should be used I guess. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19028) Prefix string too short prevents EL content assist with Seam taglib

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19028?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19028: -------------------------------------- Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) > Prefix string too short prevents EL content assist with Seam taglib > ------------------------------------------------------------------- > > Key: JBIDE-19028 > URL: https://issues.jboss.org/browse/JBIDE-19028 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, seam2 > Affects Versions: 4.2.1.Final > Environment: Plugin: Seam Tools 3.6.1.Final-v20141209-0505-B79 > OS: Windows 8.1 64bit > Eclipse: 4.4.1.M20140925-0400 (Luna SR1) > JVM: 1.8.0_25 (64bit, Oracle) > Reporter: Jiří Jansa > Assignee: Viacheslav Kabanovich > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > When Seam Tools is installed in Eclipse Luna SR1, Expression Language (EL) content assist in Visual Page Editor stopped working (no suggestion at all, JBoss related or not). This occurs only when xmlns:s="http://jboss.com/products/seam/taglib" tag library is used in a Facelet page. > Eclipse log shows following stacktrace on any such content assist attempt: > {quote} > org.jboss.tools.common.validation.JBTValidationException: Prefix string too short > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) > at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) > at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) > at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) > Caused by: java.lang.IllegalArgumentException: Prefix string too short > at java.io.File.createTempFile(File.java:2001) > at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.convertUriToFile(TagLibraryManager.java:182) > at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:100) > at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44) > at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135) > at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getLibraries(TagLibraryManager.java:57) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillXMLNamespacesForNode(PageContextFactory.java:996) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForNode(PageContextFactory.java:698) > at org.jboss.tools.jst.web.kb.PageContextFactory.fillContextForChildNodes(PageContextFactory.java:687) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:431) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:236) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:199) > at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:184) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validate(ELValidator.java:253) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > ... 10 more > {quote} > Digging more deeply into the cause, Eclipse loaded a plugin specified entry for this URI as: > {quote} > Entry element: URI > Location: taglibs\tld\s.tld in jar file C:\DevTools\IDE\eclipse\eclipse-ee-luna-sr1-64bit\plugins\org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar > URI: jar:file:/C:/DevTools/IDE/eclipse/eclipse-ee-luna-sr1-64bit/plugins/org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar!/taglibs/tld/s.tld > Key type: URI > Key: http://jboss.com/products/seam/taglib > {quote} > Line 182 of org.jboss.tools.jst.web.kb.taglib.TagLibraryManager shows the "too short" prefix is derived from the name of the file. Here, the culprit prefix is "s" (derived from "s.tld"). Temporary file prefix must be at least 3 characters long (javadoc: http://docs.oracle.com/javase/8/docs/api/java/io/File.html#createTempFile...). > I managed to work around this issue temporarily by renaming s.tld and s.taglib.xml in org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar to seam.tld and seam.taglib.tld respectively. Then I changed the entry in JAR's plugin.xml accordingly and started eclipse with "-clean" option for the changes to take effect. Now, content assist runs expectedly. > Either renaming the plugin's TLD file or ensuring the minimum prefix length in code should do the trick. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
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 2015