November 2012 - jbosstools-issues

[JBoss JIRA] (JBDS-2403) remove references to techpreview, extras, and soa-tooling sites from JBDS 6.0 and 6.0-staging sites' index.html pages

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2403: -------------------------------- Summary: remove references to techpreview, extras, and soa-tooling sites from JBDS 6.0 and 6.0-staging sites' index.html pages Key: JBDS-2403 URL: https://issues.jboss.org/browse/JBDS-2403 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: updatesite Affects Versions: 6.0.0.CR1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 6.0.0.CR1 Remove references to techpreview, extras, and soa-tooling sites from JBDS 6.0 and 6.0-staging sites' index.html pages: https://devstudio.jboss.com/updates/6.0-staging/ https://devstudio.jboss.com/updates/6.0/ Max also requests: {quote} (2012-11-26 19:08:48) [~maxandersen]: Add a screenshot of Central pointing to the extensions page would be more relevant ;) {quote} -- 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, 4 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-13206) The following connectors are not available

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-13206: ----------------------------------- Summary: The following connectors are not available Key: JBIDE-13206 URL: https://issues.jboss.org/browse/JBIDE-13206 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Android Tools Reporter: Burr Sutter The Android Tools from JBoss Central -- 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, 4 months

3
18
0 / 0

[JBoss JIRA] (JBIDE-13166) Code Coverage report contains wrong data

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-13166: ----------------------------------- Summary: Code Coverage report contains wrong data Key: JBIDE-13166 URL: https://issues.jboss.org/browse/JBIDE-13166 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 4.0.0.CR1 Reporter: Vlado Pakan Assignee: Mickael Istria Generated code coverage reports on Jenkins contains no data. Code coverage = 0%. Looks like it's broken only for Jenkins jobs building more than one component. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk... -- 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, 4 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-13100) 2 test failures in org.jboss.tools.vpe.jsp.test.JSPComponentContentTest

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13100: ---------------------------------- Summary: 2 test failures in org.jboss.tools.vpe.jsp.test.JSPComponentContentTest Key: JBIDE-13100 URL: https://issues.jboss.org/browse/JBIDE-13100 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Alexey Kazakov Priority: Blocker Fix For: 4.0.0.CR2 {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--base/lastCompletedBuild/testReport/org.jboss.tools.common.el.core.test/ELParserTest/testMultiThreadAccess/} Regression org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess (from org.jboss.tools.common.el.core.test.CommonELAllTests) Failing for the past 1 build (Since Unstable#31 ) Error Message: expected:<9990> but was:<9989> Stacktrace junit.framework.AssertionFailedError: expected:<9990> but was:<9989> at junit.framework.Assert.fail(Assert.java:50) at junit.framework.Assert.failNotEquals(Assert.java:287) at junit.framework.Assert.assertEquals(Assert.java:67) at junit.framework.Assert.assertEquals(Assert.java:199) at junit.framework.Assert.assertEquals(Assert.java:205) at org.jboss.tools.common.el.core.test.ELParserTest.testMultiThreadAccess(ELParserTest.java:429) {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, 4 months

5
13
0 / 0

[JBoss JIRA] (JBIDE-13209) Need to add ESB 4.12 option with constraints

by Tom Cunningham (JIRA)

Tom Cunningham created JBIDE-13209: -------------------------------------- Summary: Need to add ESB 4.12 option with constraints Key: JBIDE-13209 URL: https://issues.jboss.org/browse/JBIDE-13209 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Tom Cunningham -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-13184) Seam Components 2.0 Editor: XModelException: Property <property> already contains value <value>.

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-13184: ------------------------------------- Summary: Seam Components 2.0 Editor: XModelException: Property <property> already contains value <value>. Key: JBIDE-13184 URL: https://issues.jboss.org/browse/JBIDE-13184 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 4.0.0.CR1 Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121118-2035-B111.jar Reporter: Daniel Azarov Assignee: Alexey Kazakov Test case: EXECUTE: 1. Create Seam Project (war or ear) 2. Open components.xml in Seam Components 2.0 Editor 3. Open tab "Tree" 4. Right click on node "components.xml" then select New->Component then type "component" in field "Name" then press button "Finish" 5. Right click on node "component" then select "Add List Property..." then type "list" in field "Name" then press button "Finish" 6. Right click on node "list" then select "Add Entry..." then type "value" in field "Value" then press button "Finish" 7. Repeat 6. FAIL: {code} org.jboss.tools.common.model.XModelException: Property list already contains value. at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:179) at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:169) at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.addCreatedObject(DefaultCreateHandler.java:143) at org.jboss.tools.common.meta.action.impl.handlers.DefaultCreateHandler.executeHandler(DefaultCreateHandler.java:49) at org.jboss.tools.common.meta.action.impl.XActionImpl.executeHandler(XActionImpl.java:65) at org.jboss.tools.common.model.ui.wizards.SpecialWizardSupportOneImpl.action(OneStepWizard.java:54) at org.jboss.tools.common.model.ui.wizards.standard.DefaultStandardWizard.performFinish(DefaultStandardWizard.java:39) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.tools.common.model.ui.wizards.special.DefaultSpecialWizard.execute(DefaultSpecialWizard.java:54) at org.jboss.tools.common.model.ui.wizards.OneStepWizard.execute(OneStepWizard.java:38) at org.jboss.tools.common.model.ui.action.XModelObjectAction.actionPerformed(XModelObjectAction.java:114) at org.jboss.tools.common.model.ui.action.XModelObjectAction$AL.widgetSelected(XModelObjectAction.java:131) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) 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} -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-13218) Error: Could not create the Java Virtual Machine

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-13218: ----------------------------------- Summary: Error: Could not create the Java Virtual Machine Key: JBIDE-13218 URL: https://issues.jboss.org/browse/JBIDE-13218 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Priority: Minor Attachments: 2012-11-30_1425.png, 2012-11-30_1425_001.png, Installer_JVM_Settings.png Running the installer with a JRE can create an improper installation. See screenshots -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-13210) Generate Hibernate/JPA Annotations is disabled in main menubar

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13210: ------------------------------------ Summary: Generate Hibernate/JPA Annotations is disabled in main menubar Key: JBIDE-13210 URL: https://issues.jboss.org/browse/JBIDE-13210 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.0.0.CR1 Environment: JBDS 6.0.0.CR1b, L64 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 4.1.x, 4.0.x Source -> Generate Hibernate/JPA is disabled (at least I didn't find any case when it's enabled). Operation works via context (on java file(s)) without problems. -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] (JBIDE-13168) Wrong URLs in central examples

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-13168: ---------------------------------------- Summary: Wrong URLs in central examples Key: JBIDE-13168 URL: https://issues.jboss.org/browse/JBIDE-13168 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, project-examples Affects Versions: 4.0.0.CR1 Reporter: Rastislav Wagner Assignee: Snjezana Peco Fix For: 4.0.0.CR1 According to readme.md in project examples: *GWT* {code}This will deploy `target/jboss-as-kitchensink-errai.war`. The application will be running at the following URL <http://localhost:8080/jboss-as-kitchensink-errai/>.{code} should be {code}target/jboss-gwt-webapp.war http://localhost:8080/jboss-gwt-webapp/{code} *HTML5* {code}The client application will be running at the following URL <http://localhost:8080/jboss-as-kitchensink-html5-mobile/>.{code} should be {code}jboss-html5-webapp{code} *RICHFACES* {code}http://localhost:8080/jboss-as-kitchensink-rf/{code} should be {code}jboss-richfaces-webapp{code} *JAVAEE6-MULTI* {code}jboss-javaee6-multi{code} should be {code}jboss-javaee6-multi-web{code} Also for springmvc, javaee6-webapp/javaee6-mult,html5 index.html contains wrong URL {http://red.ht/jbeap-6-docs} which points to 404. -- 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, 4 months

5
23
0 / 0

[JBoss JIRA] (JBIDE-13125) discovery plugin cleanup

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-13125: ------------------------------------------- Summary: discovery plugin cleanup Key: JBIDE-13125 URL: https://issues.jboss.org/browse/JBIDE-13125 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Because of JBDS-2361 and JBIDE-12556 I spent some time reviewing the discovery plugin.xml and found a few items. I'll put my raw list in the comments, but here are the highlights: - new connector ID's should not use the same name as the feature they refer to; this is so project examples can refer to them as "the maven plugins" instead of "org.eclipse.m2e" when it might be a different name. - The word "Free" is added to some entries but not to others. - egit and egit.mylyn are two seperate things (good), subversion/subclipse.mylyn is one big one (bad). - eclipsecs includes experiemental com.github.sevntucheckstyle feature - do we need/want that ? - common.mylyn.feature - can that be split into bugzilla and jira one ? - jrebel requires server_core feature but why aren't they just listed in there and remove the need for seperate core/server feature ? - Maven connectors seem to be too fine-grained, why do we have m2e,m2e-jdt and m2e-wtp as separate connectors ? -- 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, 4 months

2
16
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