November 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13025) Target Platform jbosstools-JunoSR1a doesn't include Eclipse WST sources

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-13025: -------------------------------------- Summary: Target Platform jbosstools-JunoSR1a doesn't include Eclipse WST sources Key: JBIDE-13025 URL: https://issues.jboss.org/browse/JBIDE-13025 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 4.0.0.Beta2 Reporter: Alexey Kazakov Assignee: Nick Boldt Priority: Critical -- 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

13 years, 3 months

4
15
0 / 0

[JBoss JIRA] (JBDS-2345) Create a JBDS parent pom

by Mickael Istria (JIRA)

Mickael Istria created JBDS-2345: ------------------------------------ Summary: Create a JBDS parent pom Key: JBDS-2345 URL: https://issues.jboss.org/browse/JBDS-2345 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Build Reporter: Mickael Istria Assignee: Nick Boldt Fix For: 6.0.0.Beta1 Having a JBDS parent pom would be very comfortable. It would inherit from JBT parent pom, but would override some properties (such as local.site) and target-platform definitions. This is currently done in configuration in Jenkins, so it requires lots of parameters to build. Having a parent pom would allow to build JBDS with the same required parameters as JBT. It would also help to make the JBT parent pom cleaner: a lot of complexity in JBT parent pom comes from the fact that we want to be able to override everything since we use it for multiple purposes (JBT & JBDS). A parent pom would move this complexity to another file (JBDS parent), and won't pollute JBT. -- 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

13 years, 3 months

3
18
0 / 0

[JBoss JIRA] (JBIDE-12551) Reset button in Convert to maven dependencies wizard is behaving weird

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-12551: ---------------------------------------- Summary: Reset button in Convert to maven dependencies wizard is behaving weird Key: JBIDE-12551 URL: https://issues.jboss.org/browse/JBIDE-12551 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Alpha1 Reporter: Rastislav Wagner Assignee: Fred Bricon Fix For: 4.0.0.Alpha2 If I press Reset button in Convert to maven dependencies wizard during dependencies lookup then the status of already found dependencies is reset to "Unidentified dependency" and wizard continues in lookup but it wont bother with "reseted" dependencies anymore. Another case: When lookup ends and then I press Reset button, status of all dependencies is changet to "Unidentified dependency" and lookup is not restarted. Then no dependencies are added to pom.xml I would expect that pressing Reset button resets dependencies lookup. -- 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

13 years, 3 months

3
12
0 / 0

[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

13 years, 3 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

13 years, 3 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

13 years, 3 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

13 years, 3 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

13 years, 3 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

13 years, 3 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

13 years, 3 months

3
9
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 November 2012