November 2012 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-3526) Code assist for EL variables that come from <ui:param/>

by Alexey Kazakov (JIRA)

Code assist for EL variables that come from <ui:param/> ------------------------------------------------------- Key: JBIDE-3526 URL: https://jira.jboss.org/jira/browse/JBIDE-3526 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0 For example: mainPage.xhtml ... <ui:include src="/layout/incPage.xhtml"> <ui:param name="var1" value="#{someBean}"/> </ui:include> ... /loyout/incPage.xhtml ... <h:outputText value="#{var1.text}"/>  ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-6135) EL validation failes for valid JSF-EL

by nimo stephan (JIRA)

EL validation failes for valid JSF-EL ------------------------------------- Key: JBIDE-6135 URL: https://jira.jboss.org/jira/browse/JBIDE-6135 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Jboss Tools 3.1 GA, Facelets, JSF 1.2, Eclipse 3.5 Reporter: nimo stephan When using the following valid EL in XHTML: #{myBean.myMap['hobby'].size} the Jboss tools validator throws the following exception: 'size' cannot be resolved. Jboss tools should treat such expressions not as an error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

7
15
0 / 0

[JBoss JIRA] Created: (JBIDE-7908) Continue reading DB dialog should have "Never Show again" oprion

by Dmitry Geraskov (JIRA)

Continue reading DB dialog should have "Never Show again" oprion ---------------------------------------------------------------- Key: JBIDE-7908 URL: https://issues.jboss.org/browse/JBIDE-7908 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Priority: Optional Fix For: 3.2.0.CR1 Attachments: dialog.PNG Go to Reverce Engeneering Editor -> Type Mappings tab. Press Refresh button. Appeared dialog doesn't have "Never show again" option -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
11
0 / 0

[JBoss JIRA] (JBIDE-13076) Marker Resolution Generators should check if IMarker exists

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-13076: ------------------------------------- Summary: Marker Resolution Generators should check if IMarker exists Key: JBIDE-13076 URL: https://issues.jboss.org/browse/JBIDE-13076 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI, common/jst/core, Seam 2 Affects Versions: 4.0.0.Beta2 Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.Beta2-v20121107-1854-B62.jar Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 4.0.0.CR1 When Marker Resolution Generator tries to find quick fixes for Problem Marker marker may not be exist any more. In that case we can get follow Exception: {code} org.eclipse.core.internal.resources.ResourceException: Marker id 5 not found. at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:57) at org.eclipse.core.internal.resources.Marker.getType(Marker.java:195) at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.getProblemType(ConfigureProblemSeverityResolutionGenerator.java:140) at org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator.hasResolutions(ConfigureProblemSeverityResolutionGenerator.java:124) at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.hasResolution(MarkerHelpRegistry.java:191) at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.hasResolutions(MarkerHelpRegistry.java:160) at org.eclipse.ui.views.markers.MarkerField.annotateImage(MarkerField.java:76) at org.eclipse.ui.internal.views.markers.MarkerProblemSeverityAndMessageField.update(MarkerProblemSeverityAndMessageField.java:86) at org.eclipse.ui.internal.views.markers.MarkerColumnLabelProvider.update(MarkerColumnLabelProvider.java:62) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:953) at org.eclipse.ui.internal.views.markers.MarkersTreeViewer.doUpdateItem(MarkersTreeViewer.java:73) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:113) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1033) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167) at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2753) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1923) at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1930) at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1898) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1855) at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1535) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1533) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:548) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1490) at org.eclipse.ui.internal.views.markers.UIUpdateJob.runInUIThread(UIUpdateJob.java:108) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3529) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3182) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) 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:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) {code} So we need to add check IMarker.exists() to all our Marker Resolution Generator: 1. org.jboss.tools.jst.web.ui.action.JSPProblemMarkerResolutionGenerator 2. org.jboss.tools.jsf.web.validation.jsf2.action.JSF2ComponentResolutionGenerator 3. org.jboss.tools.cdi.ui.marker.CDIProblemMarkerResolutionGenerator 4. org.jboss.tools.common.ui.marker.ConfigureProblemSeverityResolutionGenerator 5. org.jboss.tools.seam.ui.marker.SeamProblemMarkerResolutionGenerator 6. org.jboss.tools.jst.web.kb.internal.validation.BuilderOrderResolutionGenerator 7. org.jboss.tools.jsf.ui.marker.DisableFaceletHTMLValidatorResolutionGenerator 8. org.jboss.tools.maven.ui.internal.markers.MavenDependencyMarkerResolutionGenerator 9. org.jboss.tools.maven.jdt.internal.markers.MissingEndorsedLibMarkerResolutionGenerator -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
15
0 / 0

[JBoss JIRA] (JBIDE-13181) JSF annotated managed beans do not present in Web Projects View / Beans

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-13181: -------------------------------------- Summary: JSF annotated managed beans do not present in Web Projects View / Beans Key: JBIDE-13181 URL: https://issues.jboss.org/browse/JBIDE-13181 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 4.0.0.CR1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Alpha1 1. Create a JSF 2.0 KickStart Project. 2. Open Web Projects View 3. See <project_name>/Beans 4. FAIL: There is no bean If you register any bean in faces-config then you will get this bean in the view. But annotated beans are ignored. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-13010) Wrong versioning on modules N&N pages

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-13010: ------------------------------------- Summary: Wrong versioning on modules N&N pages Key: JBIDE-13010 URL: https://issues.jboss.org/browse/JBIDE-13010 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.0.0.Beta2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.Beta2 Some modules N&N pages have old versions in their title (in the <title> section of the HTML code) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-13212) The server adapter deploys sar project with .java files instead of classes

by mikael sola (JIRA)

mikael sola created JBIDE-13212: ----------------------------------- Summary: The server adapter deploys sar project with .java files instead of classes Key: JBIDE-13212 URL: https://issues.jboss.org/browse/JBIDE-13212 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Beta2 Reporter: mikael sola Assignee: Fred Bricon As summarized, the server adapter deploys sar project, deployed into ear, with .java files instead of classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-13201) BYOE - Marketplace Installation on Mac - fails to start JBoss EAP

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-13201: ----------------------------------- Summary: BYOE - Marketplace Installation on Mac - fails to start JBoss EAP Key: JBIDE-13201 URL: https://issues.jboss.org/browse/JBIDE-13201 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
28
0 / 0

[JBoss JIRA] (JBIDE-12945) Migrate jbosstools-docs-nightly job to use git sources instead of svn

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12945: ---------------------------------- Summary: Migrate jbosstools-docs-nightly job to use git sources instead of svn Key: JBIDE-12945 URL: https://issues.jboss.org/browse/JBIDE-12945 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Nick Boldt Assignee: Isaac Rooskov This job needs to be tied to multiple git repos: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... For an example of how to do a job w/ multiple git repos as source, see this one: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... NOTE: You must set three advanced fields (each SCM entry has TWO *Advanced* buttons when configuring in the browser) for each repo to avoid collisions when fetching: !multiple-git-repos-jenkins.png! If you want to edit the config.xml file offline, the code looks like this: {code} <hudson.plugins.git.GitSCM> <configVersion>2</configVersion> <userRemoteConfigs> <hudson.plugins.git.UserRemoteConfig> <name/> <refspec/> <url>git://github.com/jbosstools/jbosstools-base.git</url> </hudson.plugins.git.UserRemoteConfig> </userRemoteConfigs> <branches> <hudson.plugins.git.BranchSpec> <name>origin/master</name> </hudson.plugins.git.BranchSpec> </branches> <disableSubmodules>false</disableSubmodules> <recursiveSubmodules>false</recursiveSubmodules> <doGenerateSubmoduleConfigurations>false</doGenerateSubmoduleConfigurations> <authorOrCommitter>false</authorOrCommitter> <clean>false</clean> <wipeOutWorkspace>false</wipeOutWorkspace> <pruneBranches>false</pruneBranches> <remotePoll>false</remotePoll> <ignoreNotifyCommit>false</ignoreNotifyCommit> <buildChooser class="hudson.plugins.git.util.DefaultBuildChooser"/> <gitTool>Default</gitTool> <submoduleCfg class="list"/> <relativeTargetDir>sources/base</relativeTargetDir> <reference/> <excludedRegions/> <excludedUsers/> <gitConfigName/> <gitConfigEmail/> <skipTag>false</skipTag> <includedRegions/> <scmName>base</scmName> </hudson.plugins.git.GitSCM> {code} You can also set filters to only watch the repo for specific paths instead of the whole repo: !git-repo-filtering-jenkins.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
18
0 / 0

[JBoss JIRA] (JBDS-2259) Scala jar missing in WAR when project using JDBS and Scala IDE

by Galder Zamarreño (JIRA)

Galder Zamarreño created JBDS-2259: -------------------------------------- Summary: Scala jar missing in WAR when project using JDBS and Scala IDE Key: JBDS-2259 URL: https://issues.jboss.org/browse/JBDS-2259 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.GA Reporter: Galder Zamarreño I've discovered a bug in JBDS/Eclipse. The application is: https://github.com/escalante/escalante-quickstart/tree/master/standard-he... If I build a war with Maven, it includes all the jars, see: https://dl.dropbox.com/u/6148072/standard-lift-app-Maven.png If I build the war, it seems to forget the scala-library jar (at least), see: https://dl.dropbox.com/u/6148072/standard-lift-app-JDBS.png Of course, without the scala-library jar, the application fails to deploy when deployed via JDBS. Note: This is a JDBS instance installed with Scala 2.9 IDE, and the IDE correctly identifies the project being a Scala project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2012