September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools

by Denis Golovin (JIRA)

Restore structure of http://download.jboss.org/jbosstools --------------------------------------------------------- Key: JBIDE-6956 URL: https://jira.jboss.org/browse/JBIDE-6956 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Assignee: Nick Boldt Priority: Critical Fix For: 3.2.0.Beta Before aggregation was introduced which is building final aggregated repo we used to have simple hierarchical stucture (see attached picture) jbosstools/builds/${type}/${branch/tag}/${timestamp} jbosstools/updates/${type}/${branch/tag} where ${type} is nightly, stable, development nightly for nightly builds stable for GA releases development for M's, betas and CR's releases ${branch/tag} was used to separate builds made from different branch tags ${timestamp} time stamp YYYYMMDDHHMMSS for example in jbosstools/builds/nightly jbosstools/builds/nightly/trunk would contains last three nightly builds from trunk jbosstools/builds/nightly/3.1.X would contains last three nightly builds from 3.1.X branch jbosstools/builds/nightly/3.1.1 would contains last several builds from 3.1.1 tag depends on what kind of problems was found in release candidate build for example jbosstools/updates/nightly would contains last update sites for tags/branches like jbosstools/updates/nightly/trunk - last update site built from trunk jbosstools/updates/nightly/3.1.X last update site built from 3.1.X branch jbosstools/updates/nightly/3.1.1 last update site built from 3.1.1 tag -- 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

15 years, 6 months

2
21
0 / 0

[JBoss JIRA] Created: (JBIDE-6938) Development Milestones Update Site Error

by Ben Clare (JIRA)

Development Milestones Update Site Error ---------------------------------------- Key: JBIDE-6938 URL: https://jira.jboss.org/browse/JBIDE-6938 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.M2 Reporter: Ben Clare Hi, When I apply the Development Milestones update site ( http://download.jboss.org/jbosstools/updates/development/ ) to Eclipse 3.6 I receive the following error: Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Maven Seam Integration 1.1.0.v20100720-0040-H162-M1 (org.jboss.tools.maven.seam.feature.feature.group 1.1.0.v20100720-0040-H162-M1) Missing requirement: Integration Seam projects with Maven 1.1.0.v20100720-0040-H162-M1 (org.jboss.tools.maven.seam 1.1.0.v20100720-0040-H162-M1) requires 'bundle org.maven.ide.eclipse.maven_model_edit 0.10.0' but it could not be found Cannot satisfy dependency: From: JBoss Maven Seam Integration 1.1.0.v20100720-0040-H162-M1 (org.jboss.tools.maven.seam.feature.feature.group 1.1.0.v20100720-0040-H162-M1) To: org.jboss.tools.maven.seam [1.1.0.v20100720-0040-H162-M1] Should the dependencies be available within the update bundle? Ben -- 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

15 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7145) Fix hibernate tools core build so works with Maven and tests passes and can get latest hibernate-tools.jar

by Max Andersen (JIRA)

Fix hibernate tools core build so works with Maven and tests passes and can get latest hibernate-tools.jar ---------------------------------------------------------------------------------------------------------- Key: JBIDE-7145 URL: https://jira.jboss.org/browse/JBIDE-7145 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.2.0.M2 Reporter: Max Andersen Assignee: Max Andersen Priority: Blocker Fix For: 3.2.0.Beta1 -- 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

15 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBDS-1287) Add Spring IDE 2.3.2 to build

by Snjezana Peco (JIRA)

Add Spring IDE 2.3.2 to build ----------------------------- Key: JBDS-1287 URL: https://jira.jboss.org/browse/JBDS-1287 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 4.0.0.M1 Reporter: Snjezana Peco Spring IDE update site: http://dist.springsource.com/release/TOOLS/update/e3.6 -- 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

15 years, 6 months

4
19
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-6988) Console Configuration should take into account scema and catalog specified for jpa project

by Dmitry Geraskov (JIRA)

Console Configuration should take into account scema and catalog specified for jpa project ------------------------------------------------------------------------------------------ Key: JBIDE-6988 URL: https://jira.jboss.org/browse/JBIDE-6988 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.2.0.M1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.2.0.CR1 Test case: 1. create 2 schemas in one database 2. create connection profile to the database 3. create jpa project with Hibernate platform and set schema, project to one of the schema 4. open created console configuration/Database Failure: there are 2 db scemas Should be only one schema, this means that hibernate is going to work with this schema. -- 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

15 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6734) Externalize string wizard - sort content of file

by Krasimir Goutcev (JIRA)

Externalize string wizard - sort content of file ------------------------------------------------ Key: JBIDE-6734 URL: https://jira.jboss.org/browse/JBIDE-6734 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Krasimir Goutcev Assignee: Alexey Kazakov Attachments: p_wizard2.png When we have big property file it will be difficult to find key. Will be nice to sort keys or values when click on header of table (see attached pic) P.S. why not to have a filter like in properties editor? -- 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

15 years, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7059) move selection bar from org.jboss.tools.vpe to org.jboss.tools.jst.jsp plugin

by Maxim Areshkau (JIRA)

move selection bar from org.jboss.tools.vpe to org.jboss.tools.jst.jsp plugin ----------------------------------------------------------------------------- Key: JBIDE-7059 URL: https://jira.jboss.org/browse/JBIDE-7059 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Affects Versions: 3.2.0.Beta Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.0.Beta Move not visual functionality from VPE plugin, because we loose it when XR will be an optional dependency. -- 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

15 years, 6 months

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2010