December 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13061) Freemarker ui tests are failing on JDK 1.7

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13061: ------------------------------------ Summary: Freemarker ui tests are failing on JDK 1.7 Key: JBIDE-13061 URL: https://issues.jboss.org/browse/JBIDE-13061 Project: Tools (JBoss Tools) Issue Type: Bug Components: QA Affects Versions: 4.0.0.Beta2 Reporter: Jiri Peterka Assignee: Jiri Peterka Fix For: 4.0.0.Beta2 There is a profile wrongly set AWT toolkit in https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

1 week, 2 days

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6878) Seam does not work with JSF 2.0 faces-config.xml

by Alexey Kazakov (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBIDE-6878 URL: https://jira.jboss.org/browse/JBIDE-6878 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x This is an issue of Seam runtime. See https://jira.jboss.org/browse/JBSEAM-4637 But let's have a duplicate it in JBT JIRA to track JBSEAM-4637 -- 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

4 weeks, 1 day

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance

by Jim Tyrrell (JIRA)

Console not showing up when staritng a EAP/SOA-P Instance --------------------------------------------------------- Key: JBDS-983 URL: https://jira.jboss.org/jira/browse/JBDS-983 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 3.0.0.M4 Reporter: Jim Tyrrell For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance. -- 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

3 months, 1 week

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- 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

11 months, 1 week

3
7
0 / 0

[JBoss JIRA] (JBIDE-13339) Null Java EE Web Project Archetype

by Claudinei Jr (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13339?page=com.atlassian.jira.plugi... ] Claudinei Jr updated JBIDE-13339: --------------------------------- Priority: Minor (was: Major) > Null Java EE Web Project Archetype > ---------------------------------- > > Key: JBIDE-13339 > URL: https://issues.jboss.org/browse/JBIDE-13339 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.0.0.Final > Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final > Reporter: Claudinei Jr > Assignee: Fred Bricon > Priority: Minor > Labels: maven > > When trying to create a new Java EE Web Project, the following description is presented: > {quote} > This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. > This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. > Project based on the *null:null:null* Maven archetype > {quote} > If I go forward with the creation of the project, I get the following error message: > {quote} > Failed to create project. > Root cause: For artifact null:null:null:pom : The group id cannot be empty. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13339) Null Java EE Web Project Archetype

by Claudinei Jr (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13339?page=com.atlassian.jira.plugi... ] Claudinei Jr updated JBIDE-13339: --------------------------------- Steps to Reproduce: Try to create a Java EE Web Project. It was working fine until not long ago and out of the blue that issue came up - now I'm no longer able to create a project (was: Try to create a Java EE Web Project. It was working fine until sometime ago and out of the blue that issue came up. ) > Null Java EE Web Project Archetype > ---------------------------------- > > Key: JBIDE-13339 > URL: https://issues.jboss.org/browse/JBIDE-13339 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.0.0.Final > Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final > Reporter: Claudinei Jr > Assignee: Fred Bricon > Priority: Minor > Labels: maven > > When trying to create a new Java EE Web Project, the following description is presented: > {quote} > This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. > This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. > Project based on the *null:null:null* Maven archetype > {quote} > If I go forward with the creation of the project, I get the following error message: > {quote} > Failed to create project. > Root cause: For artifact null:null:null:pom : The group id cannot be empty. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13339) Null Java EE Web Project Archetype

by Claudinei Jr (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13339?page=com.atlassian.jira.plugi... ] Claudinei Jr updated JBIDE-13339: --------------------------------- Description: When trying to create a new Java EE Web Project, the following description is presented: {quote} This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. Project based on the *null:null:null* Maven archetype {quote} If I go forward with the creation of the project, I get the following error message: {quote} Failed to create project. Root cause: For artifact null:null:null:pom : The group id cannot be empty. {quote} was: When trying to create a new Java EE Web Project, the following description is presented: {quote} This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. Project based on the *null:null:null* Maven archetype {quote} If I go forward with the creation of the project, I get the following error message: {quote} Failed to create project. Root cause: For artifact {null:null:null:pom}: The group id cannot be empty. {quote} > Null Java EE Web Project Archetype > ---------------------------------- > > Key: JBIDE-13339 > URL: https://issues.jboss.org/browse/JBIDE-13339 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.0.0.Final > Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07 > Reporter: Claudinei Jr > Assignee: Fred Bricon > Labels: maven > > When trying to create a new Java EE Web Project, the following description is presented: > {quote} > This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. > This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. > Project based on the *null:null:null* Maven archetype > {quote} > If I go forward with the creation of the project, I get the following error message: > {quote} > Failed to create project. > Root cause: For artifact null:null:null:pom : The group id cannot be empty. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13339) Null Java EE Web Project Archetype

by Claudinei Jr (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13339?page=com.atlassian.jira.plugi... ] Claudinei Jr updated JBIDE-13339: --------------------------------- Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final (was: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07 ) > Null Java EE Web Project Archetype > ---------------------------------- > > Key: JBIDE-13339 > URL: https://issues.jboss.org/browse/JBIDE-13339 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.0.0.Final > Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07, JBoss Tools 4.0.0.Final > Reporter: Claudinei Jr > Assignee: Fred Bricon > Labels: maven > > When trying to create a new Java EE Web Project, the following description is presented: > {quote} > This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. > This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. > Project based on the *null:null:null* Maven archetype > {quote} > If I go forward with the creation of the project, I get the following error message: > {quote} > Failed to create project. > Root cause: For artifact null:null:null:pom : The group id cannot be empty. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13339) Null Java EE Web Project Archetype

by Claudinei Jr (JIRA)

Claudinei Jr created JBIDE-13339: ------------------------------------ Summary: Null Java EE Web Project Archetype Key: JBIDE-13339 URL: https://issues.jboss.org/browse/JBIDE-13339 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Final Environment: Windows 7 64b, Eclipse Juno Service Release 1 Build id: 20120920-0800, Java 1.7_07 Reporter: Claudinei Jr Assignee: Fred Bricon When trying to create a new Java EE Web Project, the following description is presented: {quote} This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss Enterprise Application Platform 6 or JBoss Application Server 7.1. This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. Project based on the *null:null:null* Maven archetype {quote} If I go forward with the creation of the project, I get the following error message: {quote} Failed to create project. Root cause: For artifact {null:null:null:pom}: The group id cannot be empty. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13186) make browsersim launchable via jnlp

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13186?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-13186: ---------------------------------------------- Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich) > make browsersim launchable via jnlp > ----------------------------------- > > Key: JBIDE-13186 > URL: https://issues.jboss.org/browse/JBIDE-13186 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.0.x > > > By making browsersim launchable via jnlp we could launch browsersim directly from jboss tools website. > Take a look at https://github.com/ifedorenko/p2-browser which contains a jnlp enabled eclipse rcp app (might be able to use this and remove need for custom swtjar or simply just adjust it to single jar) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
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 December 2012