September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12400) JPA project building error with Eclipse Juno

by Esteve Aviles (JIRA)

Esteve Aviles created JBIDE-12400: ------------------------------------- Summary: JPA project building error with Eclipse Juno Key: JBIDE-12400 URL: https://issues.jboss.org/browse/JBIDE-12400 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 3.3.0.Final Environment: Fedora 17, with Eclipse 4.2 Juno Reporter: Esteve Aviles Assignee: Snjezana Peco JPA is unable to start: An internal error occurred during: "Building JPA Projects". org/eclipse/jpt/jpa/core/JpaAnnotationProvider -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
12
0 / 0

[JBoss JIRA] (TOOLSDOC-286) BYOE - Warn of upgrade scenario for Nring Your Own Eclipse in Release Notes (per GSS)

by mark yarborough (JIRA)

mark yarborough created TOOLSDOC-286: ---------------------------------------- Summary: BYOE - Warn of upgrade scenario for Nring Your Own Eclipse in Release Notes (per GSS) Key: TOOLSDOC-286 URL: https://issues.jboss.org/browse/TOOLSDOC-286 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Release Notes Affects Versions: Future Reporter: mark yarborough Assignee: Isaac Rooskov Fix For: Future -- 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, 6 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-11248) Invalid web.xml warning for welcome-file and error-page

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-11248: ---------------------------------- Summary: Invalid web.xml warning for welcome-file and error-page Key: JBIDE-11248 URL: https://issues.jboss.org/browse/JBIDE-11248 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.M5 Environment: Nightly Build as of 3/8/2012 Reporter: Cody Lerum web.xml shows warning "file name references to login.jsp that does not exist in web content" for {code} <welcome-file-list> <welcome-file>login.jsf</welcome-file> </welcome-file-list> {code} and "location references to /error/403.jsp that does not exist in web content" for {code} <error-page> <error-code>403</error-code> <location>/error/403.jsf</location> </error-page> {code} This just changed in a recent nightly and the actual pages are .xhtml not jsp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
15
0 / 0

[JBoss JIRA] (JBIDE-12437) Identical classes in Seam test module make Jacoco fail to generate a report

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12437: -------------------------------------- Summary: Identical classes in Seam test module make Jacoco fail to generate a report Key: JBIDE-12437 URL: https://issues.jboss.org/browse/JBIDE-12437 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Reporter: Mickael Istria Assignee: Alexey Kazakov Some classes such as org.jboss.tools.seam.ui.test.wizard.Seam12XOperationsTestSuite121EAP exist in 2 distinct modules of Seam tests (org.jboss.tools.seam.ui.test and org.jboss.tools.seam121EAP.core.test). This duplicated class prevent Jacoco from generating a report, since it does not allow several definition for the same class. We need to have those class available only once and add dependency from one of this module to the other so it can consume it during test execution; or rename packages so we now have 2 different classes. Affected class follow the pattern Seam*OperationsTestSuite* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-10251) JBossTools/Server Runtime fails to pick up new JDK/JRE runtime

by Gregor Rosenauer (Created) (JIRA)

JBossTools/Server Runtime fails to pick up new JDK/JRE runtime -------------------------------------------------------------- Key: JBIDE-10251 URL: https://issues.jboss.org/browse/JBIDE-10251 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Environment: JBoss AS 6.1.0.Final, JDK 1.6.0_27, Eclipse 3.7.1 "Indigo", WindowsXP 32bit Reporter: Gregor Rosenauer Assignee: Rob Stryker After installing a new Java version and changing JAVA_HOME and Eclipse JDK and JBoss Runtime settings accordingly, exisiting Server runtime configurations fail to pick up the changed VM and refuse to start. The only solution is to delete the server runtime configuration and create a fresh one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

7
10
0 / 0

[JBoss JIRA] (JBDS-2198) Projects created via JBoss Central page are not added to working sets

by Tomas Repel (JIRA)

Tomas Repel created JBDS-2198: --------------------------------- Summary: Projects created via JBoss Central page are not added to working sets Key: JBDS-2198 URL: https://issues.jboss.org/browse/JBDS-2198 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Beta3 Environment: RHEL 6, lenovo with CORE i7 vPro Reporter: Tomas Repel I had set the Working Sets to be the top level elements in Project Explorer. I have three working sets created, two of them are empty, one contains few projects. When I used a wizard to create a project using JBoss Central page (I tried the HTML5 Project and Spring MVC Project from Create Projects section) and clicked on the checkbox 'Add project(s) to working set' where I selected that non-empty working set, the newly created project was not added to that working set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
14
0 / 0

[JBoss JIRA] (JBIDE-11858) Empty tooltips in Server View

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-11858: ------------------------------------- Summary: Empty tooltips in Server View Key: JBIDE-11858 URL: https://issues.jboss.org/browse/JBIDE-11858 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Reporter: Daniel Azarov Assignee: Rob Stryker Attachments: ServerViewTooltip1.png, ServerViewTooltip2.png For some nodes (XML Configuration, Ports, Filesets) in Server View, Tooltips are empty -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

6
8
0 / 0

[JBoss JIRA] (JBIDE-12100) AS7 poller is set to as7 management by default while EAP6 is set to web port

by Martin Malina (JIRA)

Martin Malina created JBIDE-12100: ------------------------------------- Summary: AS7 poller is set to as7 management by default while EAP6 is set to web port Key: JBIDE-12100 URL: https://issues.jboss.org/browse/JBIDE-12100 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Environment: JBDS 5.0.0.CR1a Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.0.CR1 Feel free to push this to a future version. But I just found out about this and it seems odd. When I add a local AS7 server, it is, by default, set to AS7 management startup poller. But when I create a local EAP6 server, it is set to web poller. Why is that? This applies to both adding manually or using jboss runtime detection plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-12271) Automatic creation of xpath model fails during some tests; metadata folder DNE

by Rob Stryker (JIRA)

13 years, 6 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12398) Bug in PollThread, mixing up expected nad actual when alerting listeners

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12398: ----------------------------------- Summary: Bug in PollThread, mixing up expected nad actual when alerting listeners Key: JBIDE-12398 URL: https://issues.jboss.org/browse/JBIDE-12398 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.4.0.M1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.4.0.M1 There is currently only one implementer of the interface which is being misued, and that specific instance is not affected by the bug. This is a bug only discoverable via unit test. There is no behaviour change at all for it. The interface IPollResultListener has two methods: public void stateAsserted(boolean expectedState, boolean currentState); public void stateNotAsserted(boolean expectedState, boolean currentState); The PollThread class is misusing these methods, and instead calling with the parameters reversed. In the case of stateAsserted(bool, bool), this is not able to be noticed. In this case, it is saying the transition worked, so both values will be the same no matter what. Either expected is up or down, and, necessarily, the actual value will be the same as expected. In the case of stateNotAsserted, however, the ordering definitely matters. Either the server is up when it should be down, or it is down when it should be up. This difference matters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

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