February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-8119) parent pom maintenance for 3.3 trunk and 3.2 stable_branch

by Nick Boldt (JIRA)

parent pom maintenance for 3.3 trunk and 3.2 stable_branch ---------------------------------------------------------- Key: JBIDE-8119 URL: https://issues.jboss.org/browse/JBIDE-8119 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.x Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.x 1. Increment parent pom in trunk to 0.0.2-SNAPSHOT 2. publish updated trunk parent pom @ version 0.0.2-SNAPSHOT, and deploy to nexus 3. Increment all pom.xml refs to parent pom to 0.0.2-SNAPSHOT in all repos (jbosstools, devstudio, teiid, pi4soa, savara, scribble) (repeat process for 0.0.1-SNAPSHOT -> 0.0.1 in stable_branch just before release / GA respin) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8489) create TP for Indigo requirements

by Nick Boldt (JIRA)

create TP for Indigo requirements --------------------------------- Key: JBIDE-8489 URL: https://issues.jboss.org/browse/JBIDE-8489 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M1 Started with creation of mirrors here: http://download.jboss.org/jbosstools/updates/indigo/ (includes: Indigo (M5 stack from 201102040900) + latest Orbit (S20110124210048) + GWT 2.1.1 (not latest 2.2 yet) + link to BIRT 4.0-interim) Code is branched here: http://svn.jboss.org/repos/jbosstools/branches/3.3.indigo http://svn.jboss.org/repos/devstudio/branches/5.0.indigo -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-8486) 9 test errors in org.hibernate.eclipse.console.test

by Nick Boldt (JIRA)

9 test errors in org.hibernate.eclipse.console.test --------------------------------------------------- Key: JBIDE-8486 URL: https://issues.jboss.org/browse/JBIDE-8486 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Tests in error: testEachPackWithTestSet(org.hibernate.eclipse.console.test.mappingproject.MappingTestsCore) testEachPackWithTestSet(org.hibernate.eclipse.console.test.mappingproject.MappingTestsJpa) testEachPackWithTestSet(org.hibernate.eclipse.console.test.mappingproject.MappingTestsAnnotations) testJavaTypeHandler1(org.hibernate.eclipse.mapper.HBMInfoExtractorTest) testJavaTypeHandler2(org.hibernate.eclipse.mapper.HBMInfoExtractorTest) testJavaTypeHandler3(org.hibernate.eclipse.mapper.HBMInfoExtractorTest) testJavaTypeHandler4(org.hibernate.eclipse.mapper.HBMInfoExtractorTest) testPackageHandler1(org.hibernate.eclipse.mapper.HBMInfoExtractorTest) testPackageHandler2(org.hibernate.eclipse.mapper.HBMInfoExtractorTest) Tests run: 44, Failures: 0, Errors: 9, Skipped: 0 http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8377) Resources are sometimes out of sync after hibernate code generation

by Jiri Peterka (JIRA)

Resources are sometimes out of sync after hibernate code generation ------------------------------------------------------------------- Key: JBIDE-8377 URL: https://issues.jboss.org/browse/JBIDE-8377 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR2 (tentative) Environment: JBDS 4.0.0.CR3 H162, Linux 64 Reporter: Jiri Peterka After repeated hibernate code generation from JDBC (in my case from mysql, all exporters except generic a hql quiery selected ) sometimes ResourceException occurs. org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/dynwebonmysql51/src/entities/org/export/OrderlineId.html'. at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:699) at org.eclipse.core.internal.resources.File.getContents(File.java:293) at org.eclipse.core.internal.resources.File.getContents(File.java:282) at org.jboss.tools.jsf.web.validation.jsf2.JSF2ComponentsValidator.isValidate(JSF2ComponentsValidator.java:79) at org.jboss.tools.jsf.web.validation.jsf2.JSF2ComponentsValidator.validate(JSF2ComponentsValidator.java:56) at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704) at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:783) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669) at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:321) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79) at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48) at org.eclipse.wst.validation.internal.ValBuilderJob.deltaBuild(ValBuilderJob.java:211) at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:179) at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6396) Filter wizard/Database Collector should correctly identify catalog, schema, and tables even when tables contain dots (".") in the name

by Michael Walker (JIRA)

Filter wizard/Database Collector should correctly identify catalog, schema, and tables even when tables contain dots (".") in the name -------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6396 URL: https://jira.jboss.org/browse/JBIDE-6396 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Michael Walker Attachments: JBIDE-tablename-with-dots-patch-mpw.txt The DefaultDatabaseCollector uses StringHelper.qualifier(String) to determine the catalog and schema name for each table, given the fully-qualified name. StringHelper.qualifier() assumes that everything proceeding the final "." in the fully-qualified name represents the qualifier. This assumption breaks down if a table contains a dot in the name. This is found to be the case when working with MetaMatrix (and possibly Teiid). The result is that the Filter Wizard will generate invalid filters, based on the incorrect naming of catalog and schema for each table. As a fix, I modified DefaultDatabaseCollector to form the qualifier by using the known catalog and schema, rather than by using the StringHelper.qualifier method. I rebuilt tools and verified that this fixed the problem when working with MetaMatrix. This may be better addressed by changing the behavior of StringHelper.qualifier() itself. See forum discussion for details. Patch attached. -- 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, 9 months

7
28
0 / 0

[JBoss JIRA] Created: (JBIDE-8233) Gode Generation wizard: reveng stragegy should be validated

by Dmitry Geraskov (JIRA)

Gode Generation wizard: reveng stragegy should be validated ----------------------------------------------------------- Key: JBIDE-8233 URL: https://issues.jboss.org/browse/JBIDE-8233 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.2.x Test case: 1. Go to hibernate code generation configuration wizard 2. enter whatever in Reveng.strategy FAILURE: no message about invalid reveng.strategy -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-411) Need 64-bit windows support

by Samuel Mendenhall (JIRA)

Need 64-bit windows support --------------------------- Key: JBDS-411 URL: https://jira.jboss.org/jira/browse/JBDS-411 Project: Developer Studio Issue Type: Feature Request Affects Versions: 1.1.0.GA Reporter: Samuel Mendenhall Assignee: Max Rydahl Andersen JBDS is not usable on a 64-bit Windows machine. -- 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, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8344) Runtime detection creates invalid runtime for EAP 4.3.0.GA_CP03

by Magnus Mogren (JIRA)

Runtime detection creates invalid runtime for EAP 4.3.0.GA_CP03 --------------------------------------------------------------- Key: JBIDE-8344 URL: https://issues.jboss.org/browse/JBIDE-8344 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Magnus Mogren Assignee: Rob Stryker The automatic runtime detection cannot handle EAP 4.3.0.GA_CP03. In the "Searching for runtimes..." dialog it detects it as Version=4.3 and type=AS. The created runtime gets type "JBoss AS 4.2" and vendor "JBoss Community". Because of this i get the warning "This server type expects a version of 4.2 but the server directory is of version 4.3.0.GA_CP03." in the "Edit Server Runtime Environment" dialog The correct type and vendor should be "JBoss Enterprise Application Platform 4.3" and "JBoss Enterprise Middleware" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8272) Renaming seam runtime changes seam runtime path to seam runtime name

by Jiri Peterka (JIRA)

Renaming seam runtime changes seam runtime path to seam runtime name -------------------------------------------------------------------- Key: JBIDE-8272 URL: https://issues.jboss.org/browse/JBIDE-8272 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.CR1 Environment: JBDS 4.0.0.CR1 H100, Linux 64 Reporter: Jiri Peterka Steps: 1. Add new seam runtime (Preferences -> Jboss Tools -> Web -> Seam -> Add) 2. Add seam runtime 3. Edit and change seam runtime name, OK ERROR: Seam runtime path is changed to new seam runtime name -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8332) Image/Instance-Filter dialog: need field decorations

by Andre Dietisheim (JIRA)

Image/Instance-Filter dialog: need field decorations ---------------------------------------------------- Key: JBIDE-8332 URL: https://issues.jboss.org/browse/JBIDE-8332 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.1 Ihe filter expressions in the image- and instance-filter-dialogs may not be empty. An appropriate error is already shwon in the dialog title area. We also need error decorations for it to be consistent in all dialogs/wizard that we have. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
5
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 February 2011