April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8775) Sync up JBT trunk with 3.2.x branch

by Robert (Bob) Brodt (JIRA)

Sync up JBT trunk with 3.2.x branch ----------------------------------- Key: JBIDE-8775 URL: https://issues.jboss.org/browse/JBIDE-8775 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Final Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.1.Final, 3.2.x Copy all bug fixes from JBT trunk and eclipse.org/bpel to the 3.2.x branch. This includes upversioning from x.y.z to x.y.z+1 of all plugins in MANIFEST.MF and pom.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDS-1131) Wrong link in JBDS Hibernate Doc (database_jboss_tools_331.zip)

by Jiri Peterka (JIRA)

Wrong link in JBDS Hibernate Doc (database_jboss_tools_331.zip) --------------------------------------------------------------- Key: JBDS-1131 URL: https://jira.jboss.org/jira/browse/JBDS-1131 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Doc - Hibernate Affects Versions: 3.0.0.CR3 Reporter: Jiri Peterka Assignee: Svetlana mukhina Fix For: 3.0.0.GA In Hibernate Doc, follow this: 4.1.1. Download base project You can download example projects which are used as base for this chapter. JPA base project is available here and base Java project is situated here. Also you need start database. WRONG LINK: database, http://anonsvn.jboss.org/repos/jbosstools/trunk//hibernatetools/docs/refe... -- 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, 8 months

5
13
0 / 0

[JBoss JIRA] Created: (JBDS-1636) fix copyrights in all features

by Nick Boldt (JIRA)

fix copyrights in all features ------------------------------ Key: JBDS-1636 URL: https://issues.jboss.org/browse/JBDS-1636 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build, documentation, Requirements Affects Versions: 4.1.0.M1, 5.0.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.0.M1, 5.0.0.M1 >From Richard Fontana: > If you are under general instructions to use "JBoss by Red Hat" for marketing or branding purposes that's fine. > The one place where it is not formally correct is in copyright statements themselves. Those should at least say "Copyright <year> Red Hat, Inc." (or, as I often recommend for JBoss source code files, "Copyright <year> Red Hat, Inc. and/or its affiliates". > The 'provider name' by contrast doesn't matter from a legal perspective. It doesn't matter to me if there's some inconsistency between provider name and copyright holder name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBDS-1527) Old usage report dialog after JBDS update from B2 to CR1

by Pavol Srna (JIRA)

Old usage report dialog after JBDS update from B2 to CR1 -------------------------------------------------------- Key: JBDS-1527 URL: https://issues.jboss.org/browse/JBDS-1527 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: updatesite Affects Versions: 4.0.0.CR1 Environment: JBDS 4.0.0.B2, updatesite: http://reports.qa.atl.jboss.com/binaries/RHDS/updates/development/4.0.0.C... Reporter: Pavol Srna After update from JBDS 4.0.0.B2 to JBDS 4.0.0.CR1 the usage report dialog is the same as in beta2. It should be the new one with just "yes","no" option. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
10
0 / 0

[JBoss JIRA] Created: (JBDS-1593) Detail what 3rd party projects should be included in JBDS 4.x

by Nick Boldt (JIRA)

Detail what 3rd party projects should be included in JBDS 4.x ------------------------------------------------------------- Key: JBDS-1593 URL: https://issues.jboss.org/browse/JBDS-1593 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Nick Boldt Assignee: Burr Sutter JBDS 4.0.0 contains: * SpringIDE 2.5.1.201011101000-RELEASE * TestNG 5.14.6.20110119_1050 (Hosted here: http://reports.qa.atl.jboss.com/binaries/RHDS/requirements/helios/) ---- What should the next two releases contain? JBDS 4.x should contain: * SpringIDE 2.5.1.201011101000-RELEASE * TestNG 5.14.6.20110119_1050 * ...? JBDS 5.x should contain: * SpringIDE 2.6? * TestNG 5.? * ...? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
38
0 / 0

[JBoss JIRA] Created: (JBDS-1612) JBDS41_020: Provide scriptable installer

by Brian Fitzpatrick (JIRA)

JBDS41_020: Provide scriptable installer ---------------------------------------- Key: JBDS-1612 URL: https://issues.jboss.org/browse/JBDS-1612 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 4.1.0.GA Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Priority: Optional Scriptable Izpack installer for headless install. Several customers as well as internal parties like GLS would like to have a scriptable - no human interaction - install for JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8809) Seam 2.2 DVD Store example not working with EAP 5.1.1

by Martin Malina (JIRA)

Seam 2.2 DVD Store example not working with EAP 5.1.1 ----------------------------------------------------- Key: JBIDE-8809 URL: https://issues.jboss.org/browse/JBIDE-8809 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2.0.Final Environment: Mac OS X 10.6.7 Snow Leopard Apple JDK 1.6 JBDS 4.0 JBoss EAP 5.1.1 ER1 Reporter: Martin Malina Assignee: Snjezana Peco The Seam 2.2 DVD Store example is not working with EAP 5.1.1 ER1. It fails to deploy. We had a similar problem in EAP 5.1 and it was resolved by updating the project-examples to use a newer version of the example. See JBIDE-6696. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
24
0 / 0

[JBoss JIRA] Created: (JBDS-1607) Wrong JBDS datasheet link on the devstudio product page

by Jiri Peterka (JIRA)

Wrong JBDS datasheet link on the devstudio product page ------------------------------------------------------- Key: JBDS-1607 URL: https://issues.jboss.org/browse/JBDS-1607 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 4.0.0.GA Reporter: Jiri Peterka There are two links on JBDS product page (http://www.jboss.com/products/devstudio/) One of them is incorrect (http://www.redhat.com/f/pdf/jbds_datasheet.pdf). It's pointing to old JBDS3 datatsheet It should be http://www.jboss.com/pdf/jboss_dev_studio_data_sheet.pdf -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8476) JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce)

by joe freeman (JIRA)

JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce) --------------------------------------------------------------------------------------------- Key: JBIDE-8476 URL: https://issues.jboss.org/browse/JBIDE-8476 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.CR1 Environment: 3.2.0 GA Rich Faces Editor Mac and Windows Eclipse 3.6 Perforce (or possibly other READ/ONLY based SCM) Reporter: joe freeman Assignee: Alexey Kazakov We have a large project that uses Perforce as SCM. Perforce leaves files read/only until they have been modified at which point they are checked out and made writable. Eclipse refactoring modifies files and automatically engages the SCM Eclipse plugins on changes to optionally check the files out. In the case of Perforce, this makes the files writable on modification which allows changes to be saved. This works fine under Eclipse 3.5 with Jboss Tools. This is broken under Eclipse 3.6, Jboss tools 3.2 when the RichFaces editor is installed and a developer attempts to rename a method using "refactor Method name". You get a set of error messages where it looks like the refactoring is trying to change read-only files. Many of the files listed are not changed by the refactoring. It's almost like the Rich Faces editor/refactor hooks is stat'ing or touching the files maybe without changing. Removing the RichFaces editor stops the problem for occurring. No work around exists. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
12
0 / 0

[JBoss JIRA] Created: (JBDS-1570) Document that BPEL is a Tech preview in the JBDS 4.0 release

by Shaun Appleton (JIRA)

Document that BPEL is a Tech preview in the JBDS 4.0 release ------------------------------------------------------------ Key: JBDS-1570 URL: https://issues.jboss.org/browse/JBDS-1570 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: documentation Affects Versions: 4.0.0.GA Reporter: Shaun Appleton JBDS-1360 states BPEL is a tech release for JBDS 4.0 The docs need to state this to and should say that, as such, it is not supported - but we welcome feedback. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

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