April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8644) Remember to bump versions of usage tracking to distinguish releases

by Max Rydahl Andersen (JIRA)

Remember to bump versions of usage tracking to distinguish releases ------------------------------------------------------------------- Key: JBIDE-8644 URL: https://issues.jboss.org/browse/JBIDE-8644 Project: Tools (JBoss Tools) Issue Type: Bug Components: usage Affects Versions: 3.2.0.Final Reporter: Max Rydahl Andersen Fix For: 3.2.1, 3.2.0.M1 afaik the usage plugin version is still the one that is used to report which version of JBT/JBDS users are using. Opening this jira to ensure that we either find another solution for this OR at least remember to bump the minor/major versions just as much as for jboss tools it self (i.e. 3.2.1 in branch and 3.3.0 in trunk) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8795) pom.xml and manifest.mf versions must align

by Nick Boldt (JIRA)

pom.xml and manifest.mf versions must align ------------------------------------------- Key: JBIDE-8795 URL: https://issues.jboss.org/browse/JBIDE-8795 Project: Tools (JBoss Tools) Issue Type: Bug Components: usage Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Andre Dietisheim Fix For: 3.3.0.M1 http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.3... [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-packaging-plugin:0.10.0:validate-version (default-validate-version) on project org.jboss.tools.usage.test: Unqualified OSGi version 1.1.0.qualifier must match unqualified Maven version 1.0.0-SNAPSHOT for SNAPSHOT builds -> [Help 1] When incrementing your manifest.mf files, be sure to also increment your pom.xml files! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7111) Internal error during building Project Archive

by Jiri Peterka (JIRA)

Internal error during building Project Archive ---------------------------------------------- Key: JBIDE-7111 URL: https://jira.jboss.org/browse/JBIDE-7111 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.2.0.M2 Environment: JBDS 4.0.0.m2 480, Linux 64 Reporter: Jiri Peterka Internal error and temporary IDE freeze during building SeamWAR in Project Archive View: 1. New workspace 2. Create seam war project (default EAP) 3. Switch to Project Archive 4. Create war archive 5. Build archive -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8304) Project Archives Preferences for project should have link to edit global Rchives preferences

by Denis Golovin (JIRA)

Project Archives Preferences for project should have link to edit global Rchives preferences -------------------------------------------------------------------------------------------- Key: JBIDE-8304 URL: https://issues.jboss.org/browse/JBIDE-8304 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Affects Versions: 3.2.0.CR2 (tentative) Reporter: Denis Golovin Assignee: Rob Stryker Fix For: 3.3.0.M1 Attachments: screenshot65.png, screenshot66.png Compiler preferences dialog for project lets enable/disable project specific preferences as well as open and edit global preferences through the link. !screenshot65.png! Would be good have the same feature for Project Archives Preferences page for project like !screenshot65.png! -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8763) Create XULRunner 1.9.2 bundles for MacOS

by Yahor Radtsevich (JIRA)

Create XULRunner 1.9.2 bundles for MacOS ---------------------------------------- Key: JBIDE-8763 URL: https://issues.jboss.org/browse/JBIDE-8763 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.0.M1 We need XULRunner 1.9.2 bundles for MacOS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8467) Remove debug message from RichFacesInplaceSelectTemplate.java

by Vlado Pakan (JIRA)

Remove debug message from RichFacesInplaceSelectTemplate.java ------------------------------------------------------------- Key: JBIDE-8467 URL: https://issues.jboss.org/browse/JBIDE-8467 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.2.x Reporter: Vlado Pakan Assignee: Denis Maliarevich Priority: Minor /trunk/jsf/plugins/org.jboss.tools.jsf.vpe.richfaces/src/org/jboss/tools/jsf/vpe/richfaces/template/RichFacesInplaceSelectTemplate.java contains forgotten debug message in createSelectedList(...) method: System.out.println(" dropDownListSizesStyle = " //$NON-NLS-1$ + dropDownListSizesStyle); Please remove it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBDS-905) Forum revision for 3.1.0 release

by Svetlana mukhina (JIRA)

Forum revision for 3.1.0 release -------------------------------- Key: JBDS-905 URL: https://jira.jboss.org/jira/browse/JBDS-905 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.1.0-doc Review forum posts, update the guides according to users remarks, wishes, answer on forum posts related to docs or posts that you know answers for -- 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

14 years, 11 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-8497) Seam test failures.

by Alexey Kazakov (JIRA)

Seam test failures. ------------------- Key: JBIDE-8497 URL: https://issues.jboss.org/browse/JBIDE-8497 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.1 >>> org.jboss.tools.seam.ui.test.SeamUiAllTests.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam12XFacetTestSuite121EAP.testCreateWar 0.012 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam12XFacetTestSuite121EAP.testCreateEar 0.0050 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam12XFacetTestSuite121EAP.testCreateCustomProject 0.0040 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam12XFacetTestSuite121EAP.testJiraJbide1544 0.0030 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam12XOperationsTestSuite121EAP.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite201GA.org.jboss.tools.seam.core.test.project.facet.Seam2FacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite201GA.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite202SP1.org.jboss.tools.seam.core.test.project.facet.Seam2FacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite202SP1.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite203CR1.org.jboss.tools.seam.core.test.project.facet.Seam2FacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite203CR1.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite211GA.org.jboss.tools.seam.core.test.project.facet.Seam211GAFacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite211GA.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite212GA.org.jboss.tools.seam.core.test.project.facet.Seam211GAFacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite212GA.initializationError 0.0070 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite220CR1.org.jboss.tools.seam.core.test.project.facet.Seam220CR1FacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite220CR1.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite220GA.org.jboss.tools.seam.core.test.project.facet.Seam220CR1FacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite220GA.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite221CR1.org.jboss.tools.seam.core.test.project.facet.Seam220CR1FacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite221CR1.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite221CR2.org.jboss.tools.seam.core.test.project.facet.Seam221CR2FacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite221CR2.initializationError 0.0060 4 >>> org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuiteFP.org.jboss.tools.seam.core.test.project.facet.Seam2FacetInstallDelegateTest 0.0 4 >>> org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuiteFP.initializationError -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8811) TestProjectProvider.importProject() fails when project already exists in Workspace

by Victor Rubezhny (JIRA)

TestProjectProvider.importProject() fails when project already exists in Workspace ---------------------------------------------------------------------------------- Key: JBIDE-8811 URL: https://issues.jboss.org/browse/JBIDE-8811 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: testing Affects Versions: 3.3.0.M1 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.3.0.M1 When a project exists in workspace (for example, after some test case in finished on this project) the repeat import of the same project fails because of exception risen in project.create() method. In this case the project doesn't not become properly opened. ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.tools.seam.ui.test.SeamUiAllTests org.eclipse.core.internal.resources.ResourceException: Resource '/TestSeamELContentAssist' already exists. at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:306) at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:293) at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:52) at org.eclipse.core.internal.resources.Project.create(Project.java:287) at org.eclipse.core.internal.resources.Project.create(Project.java:269) at org.eclipse.core.internal.resources.Project.create(Project.java:262) at org.jboss.tools.test.util.ResourcesUtils.importProjectIntoWorkspace(ResourcesUtils.java:246) at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:74) at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:60) at org.jboss.tools.test.util.ResourcesUtils.importProject(ResourcesUtils.java:193) at org.jboss.tools.test.util.TestProjectProvider.<init>(TestProjectProvider.java:56) at org.jboss.tools.seam.ui.test.ca.SeamELContentAssistJbide1645Test.setUp(SeamELContentAssistJbide1645Test.java:35) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-8591) New File Wizard gives no indication that new resource can't be created because project lacks BPEL facet

by Robert (Bob) Brodt (JIRA)

New File Wizard gives no indication that new resource can't be created because project lacks BPEL facet ------------------------------------------------------------------------------------------------------- Key: JBIDE-8591 URL: https://issues.jboss.org/browse/JBIDE-8591 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Robert (Bob) Brodt Fix For: 3.2.1 The New File Wizard can not be advanced beyond the first page ("Select a wizard - New BPEL Process File") if the selected project does not have a BPEL facet. No error message is displayed but there is a stack trace in the log. The correct behavior should be to allow creation of the BPEL process file, but display a warning if the project does not have a BPEL facet. java.lang.IllegalArgumentException: Path must include project and resource name: /project_without_BPEL_facet at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1795) at org.eclipse.core.internal.resources.Container.getFolder(Container.java:221) at org.eclipse.bpel.ui.wizards.NewFileWizard.getBPELContainer(NewFileWizard.java:228) at org.eclipse.bpel.ui.wizards.NewFileWizard.init(NewFileWizard.java:93) at org.eclipse.ui.internal.dialogs.WorkbenchWizardNode.getWizard(WorkbenchWizardNode.java:185) at org.eclipse.jface.wizard.WizardSelectionPage.getNextPage(WizardSelectionPage.java:104) at org.eclipse.ui.internal.dialogs.WorkbenchWizardSelectionPage.getNextPage(WorkbenchWizardSelectionPage.java:100) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:887) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:426) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:254) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
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 April 2011