April 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-754) Externalize English strings in devstudio code

by Sean Flanigan (JIRA)

Externalize English strings in devstudio code --------------------------------------------- Key: JBDS-754 URL: https://jira.jboss.org/jira/browse/JBDS-754 Project: Developer Studio Issue Type: Feature Request Components: ui/branding Affects Versions: 2.0.0.GA Reporter: Sean Flanigan Assignee: Sean Flanigan As in JBIDE-3557, there are some unexternalized strings which need to be pulled out into .properties files, so that they can be translated. -- 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

15 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBDS-587) Need to translate Help/About text including copyright statement

by Sean Flanigan (JIRA)

Need to translate Help/About text including copyright statement --------------------------------------------------------------- Key: JBDS-587 URL: https://jira.jboss.org/jira/browse/JBDS-587 Project: Developer Studio Issue Type: Feature Request Components: Build Affects Versions: 2.0.0.cr1 Reporter: Sean Flanigan Help/About JBoss Developer Studio shows the version/copyright information for JBDS. This text looks similar to /com.jboss.jbds.product/plugin.properties but is actually overwritten/expanded from releng/org.jboss.ide.eclipse.releng/builders/product/product.properties during the build. The problem is, if we create a translation fragment plugin for com.jboss.jbds.product, the translators will translate the obsolete information in /com.jboss.jbds.product/plugin.properties, and when a langpack is installed, the up-to-date information will be replaced by obsolete information. We need to work out how to handle this better, preferably keeping the translatable text somewhere in com.jboss.jbds.product, not in releng. Perhaps we could do something with /com.jboss.jbds.product/about.mappings / about.ini? Ref: http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.... -- 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

15 years, 6 months

6
28
0 / 0

[JBoss JIRA] Created: (JBIDE-6089) JDT thows exception when seam dynamic web project form ear deleted first

by Denis Golovin (JIRA)

JDT thows exception when seam dynamic web project form ear deleted first ------------------------------------------------------------------------ Key: JBIDE-6089 URL: https://jira.jboss.org/jira/browse/JBIDE-6089 Project: Tools (JBoss Tools) Issue Type: Task Components: QA, Seam Affects Versions: 3.2.next Reporter: Denis Golovin Assignee: Denis Golovin Priority: Minor Fix For: 3.1.0.GA Seam test project has a reference to WebContent in seam dynamic web project and that leads to exception if seam dynamic web project deleted first Java Model Exception: Java Model Status [/seam_war/WebContent [in seam_war-test] does not exist] [java] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502) [java] at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) [java] at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515) [java] at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252) [java] at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238) [java] at org.eclipse.jdt.internal.core.PackageFragmentRoot.getKind(PackageFragmentRoot.java:477) [java] at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:645) [java] at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:791) [java] at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:734) [java] at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:791) [java] at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:734) [java] at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.elementChanged(PackageExplorerContentProvider.java:124) [java] at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1557) [java] at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) [java] at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1547) [java] at org.eclipse.jdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1381) [java] at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1357) [java] at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1958) [java] at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:470) [java] at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291) [java] at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) [java] at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) [java] at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) [java] at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313) [java] at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1022) [java] at org.eclipse.core.internal.resources.Resource.delete(Resource.java:749) [java] at org.eclipse.core.internal.resources.Project.delete(Project.java:317) [java] at org.jboss.tools.seam.core.test.project.facet.AbstractSeamFacetTest.tearDown(AbstractSeamFacetTest.java:135) [java] at org.jboss.tools.seam.ui.test.wizard.AbstractSeamNewOperationTest.tearDown(AbstractSeamNewOperationTest.java:98) [java] at org.jboss.tools.seam.ui.test.wizard.Seam12WARNewOperationTest.tearDown(Seam12WARNewOperationTest.java:83) [java] at org.jboss.tools.seam.ui.test.wizard.Seam20XOperationsTestSuite201GA$Seam20WARNewOperationTestSetup.tearDown(Seam20XOperationsTestSuite201GA.java:72) [java] at junit.extensions.TestSetup$1.protect(TestSetup.java:22) [java] at junit.framework.TestResult.runProtected(TestResult.java:124) [java] at junit.extensions.TestSetup.run(TestSetup.java:25) [java] at junit.framework.TestSuite.runTest(TestSuite.java:230) [java] at junit.framework.TestSuite.run(TestSuite.java:225) [java] at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) [java] at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) [java] at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) [java] at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) [java] at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) [java] at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) [java] at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) [java] at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) [java] at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) [java] at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) [java] at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) [java] at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) [java] at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) [java] at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) [java] at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) [java] at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) [java] at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) [java] at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) [java] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) [java] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) [java] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1311) [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1287) [java] at org.eclipse.core.launcher.Main.main(Main.java:34) [java] !SUBENTRY 1 org.eclipse.jdt.core 4 969 2010-03-20 16:11:45.571 [java] !MESSAGE /seam_war/WebContent [in seam_war-test] does not exist -- 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

15 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4177) Seam Booking project example errors.

by Aliaksey Nis (JIRA)

Seam Booking project example errors. ------------------------------------ Key: JBIDE-4177 URL: https://jira.jboss.org/jira/browse/JBIDE-4177 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.1.0 Environment: WindowsXP SP2 JBoss Tools Version: 3.1.0 Build id: JBossTools-ALL-win32-3.1.0.Alpha1-N200904090001-H90 JRE 1.5_08 Reporter: Aliaksey Nis Priority: Minor EXECUTE: Import Seam Booking example project. EXECUTE: Open Problems view. FAILURE: 3 errors shown here. 1. The element type "INPUT" must be terminated by the matching end-tag "</INPUT>". File: introExp.html Folder: booking/WebContent/exp Line: line 22 2. The element type "INPUT" must be terminated by the matching end-tag "</INPUT>". File: workspaceExp.html Folder: booking/WebContent/exp Line: line 22 3. The entity name must immediately follow the '&' in the entity reference. File: mainExp.html Folder: booking/WebContent/exp Line: line 94 Example project must be correctly imported. -- 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

15 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-564) Internationalise Dev Studio installer

by Sean Flanigan (JIRA)

Internationalise Dev Studio installer ------------------------------------- Key: JBDS-564 URL: https://jira.jboss.org/jira/browse/JBDS-564 Project: Developer Studio Issue Type: Feature Request Components: installer Reporter: Sean Flanigan Assignee: Sean Flanigan Link from Denis Golovin: http://izpack.org/documentation/installation-files.html#internationalizat... We should probably try to reuse some of the tooling developed for the JEMS installer by Caius Chance. See http://www.jboss.org/community/docs/DOC-10872 and http://anonsvn.jboss.org/repos/installer/jems-installer/branches/Branch_M... -- 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

15 years, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5909) Other console configuration empty tree labels after close first console config.

by Vitali Yemialyanchyk (JIRA)

Other console configuration empty tree labels after close first console config. ------------------------------------------------------------------------------- Key: JBIDE-5909 URL: https://jira.jboss.org/jira/browse/JBIDE-5909 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.CR2 Reporter: Vitali Yemialyanchyk Priority: Minor Attachments: screenshot-1.jpg should be at least 2 opened/expanded console configurations; select first console config - drop down menu - close it; other console config will be colapsed - expand tree item for this console config - see empty labels; rebuild will help to restore it to normal state -- 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

15 years, 7 months

2
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6185) NPE o.j.t.common.model.filesystems.impl.FolderImpl.update()

by Darryl Miles (JIRA)

NPE o.j.t.common.model.filesystems.impl.FolderImpl.update() ----------------------------------------------------------- Key: JBIDE-6185 URL: https://jira.jboss.org/jira/browse/JBIDE-6185 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.1.0.GA Environment: Linux Reporter: Darryl Miles Assignee: Alexey Kazakov More IResource.getLocation()==null (see my bug https://jira.jboss.org/jira/browse/JBIDE-4912 ) Check out the following background reading on IResource.getLocation()==null http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.... https://bugs.eclipse.org/bugs/show_bug.cgi?id=130398 I am a Linux user, therefore I have multiple file systems for different purposes, not all my data is on the same filesystem. Please please audit all plugins for the same presumption. Looking at the context this is a "linked resource" and usually it is linked because it is somewhere else on my filesystem. I don't understand the comment from bugs.eclipse.org link above about getResource()==null when its on a different file system, it seems users need a reliable way to resolve a java.io.File for a given resource, if that resource is backed by a file, even if its on a different file system. !MESSAGE An internal error occurred during: "JBoss Tools Model Update". !STACK 0 java.lang.NullPointerException at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:306) at org.jboss.tools.common.model.filesystems.impl.FileSystemFolderLoader.update(FileSystemFolderLoader.java:28) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.update(FileSystemsLoader.java:67) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.doUpdate(FileSystemsImpl.java:286) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.access$4(FileSystemsImpl.java:280) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl$UpdateRunnable.run(FileSystemsImpl.java:273) at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:158) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

15 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBDS-1034) ESB Node Properties for Input/Output variables grows larger than panel when panel is resized.

by Aaron Pestel (JIRA)

ESB Node Properties for Input/Output variables grows larger than panel when panel is resized. --------------------------------------------------------------------------------------------- Key: JBDS-1034 URL: https://jira.jboss.org/jira/browse/JBDS-1034 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: JBDS 3.0 M4 Reporter: Aaron Pestel Priority: Minor To reproduce: 1.) Drag an ESB Service node on jBPM Diagram Pallette 2.) Click on (select) the new ESB Service node 3.) Select the Properties view tab 4.) Click the ESB subtab of the ESB Properties panel 5.) Click the "Input" subsubtab of the ESB subtab of the ESB Properties panel 6.) Grab the left edge of the "Properties" panel and move it to the left (increasing the width of the Properties panel) 7.) Note that the ESB Input sub panel grows wide faster than its Properties panel container such that you can no longer see the "Add" button in the ESB Input sub panel without scrolling. -- 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

15 years, 7 months

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-5910) jBPM processdefinition.xml renaming causes complete physical removal of process definition and related files

by Jiri Peterka (JIRA)

jBPM processdefinition.xml renaming causes complete physical removal of process definition and related files ------------------------------------------------------------------------------------------------------------ Key: JBIDE-5910 URL: https://jira.jboss.org/jira/browse/JBIDE-5910 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.CR2 Environment: JBDS 3.0.0 CR2 #173, Linux 64, Linxu 64, Sun JDK 1.6 Reporter: Jiri Peterka Fix For: 3.1.0.CR3 Steps to reproduce: 1. Create jBPM3 project 2. Create jbpm Process 3. Click on processdefinition.xml -> Refactor -> Rename and change to processdefinition2.xml ERROR: Entire process package with all files is physically removed from filesystem -- 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

15 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4717) JBoss Portlet facet is available only when there is no runtime selected

by Denis Golovin (JIRA)

JBoss Portlet facet is available only when there is no runtime selected ----------------------------------------------------------------------- Key: JBIDE-4717 URL: https://jira.jboss.org/jira/browse/JBIDE-4717 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.1.GA Reporter: Denis Golovin Assignee: Snjezana Peco Fix For: 3.0.2.GA -- 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

15 years, 7 months

3
7
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 2010